@ui5/mcp-server

What it does

MCP server for UI5 application development with SAPUI5/OpenUI5. Designed to improve developer experience when agentic AI tools work with UI5 codebases. Exposes ten tools: scaffolding new applications and Integration Cards, validating manifests against the UI5 schema, running UI5-specific linting via @ui5/linter integration, fetching framework API documentation, extracting project metadata and configuration, accessing development guidelines, providing UI Integration Card best practices, and supporting JavaScript-to-TypeScript migration guidance.

Who it's for

Frontend developers building SAPUI5 or OpenUI5 applications, particularly teams using agentic AI tools like Claude, GitHub Copilot, or Cline to accelerate development, validate code quality, and ensure adherence to UI5 best practices and conventions.

Common use cases

• Scaffold new UI5 applications or Integration Cards from built-in templates
• Validate UI5 manifest files against the official schema
• Analyze UI5 code with integrated @ui5/linter to detect framework-specific issues
• Retrieve API documentation for UI5 controls, classes, and framework features
• Extract project metadata for analysis or plan JavaScript-to-TypeScript migrations

Setup pitfalls

• Node.js v20.17.0, v22.9.0, or higher is required; earlier versions are unsupported
• On native Windows (not WSL), the MCP configuration must prefix npx with cmd /c as a workaround
• Filesystem read access is required to analyze project structure and generate scaffolds; ensure this is configured in restricted or sandboxed environments
• Configure UI5_MCP_SERVER_ALLOWED_DOMAINS to control external API access (defaults to localhost and services.odata.org)