@ui5/mcp-server

What it does

This MCP server provides ten tools specifically designed for UI5 and OpenUI5 development. It scaffolds new UI5 applications and UI Integration Cards, validates application manifests, runs UI5-specific linting through integration with @ui5/linter, and retrieves API documentation and development guidelines. The server enables AI tools to understand UI5 patterns and constraints, helping with code analysis, error detection, and project setup.

Who it's for

SAP UI5 and OpenUI5 developers building enterprise web applications. Particularly valuable for teams using AI-assisted development with clients like Claude Code, VS Code Copilot, or Cline who want framework-specific guidance and scaffolding during development.

Common use cases

• Generate new UI5 applications or UI Integration Cards with correct project structure and dependencies
• Run UI5-specific linting to detect framework violations and anti-patterns in code
• Fetch and query UI5 API reference and development best practices during coding sessions
• Validate manifest.json files against the official UI5 schema
• Retrieve TypeScript conversion guidelines when migrating existing JavaScript UI5 projects

Setup pitfalls

• High-risk classification: the server reads the filesystem and makes network calls to fetch documentation. Review MCP client permissions before enabling.
• Node.js version: strictly requires v20.17.0, v22.9.0 or higher. Earlier versions fail silently.
• Windows native: use cmd /c prefix in the npx command; WSL and other systems use the standard configuration.
• Domain whitelist: by default UI5_MCP_SERVER_ALLOWED_DOMAINS restricts API calls to localhost and services.odata.org. If your project uses custom OData services, update this environment variable.