SAP Build MCP Server

SAP Build ships a family of official Model Context Protocol servers that give AI coding assistants context-aware access to SAP's core application development stacks. The suite covers four runtimes and toolchains: SAP Fiori elements (@sap-ux/fiori-mcp-server), the SAP Cloud Application Programming Model (@cap-js/mcp-server), SAPUI5/OpenUI5 (@ui5/mcp-server), and the SAP Mobile Development Kit (@sap/mdk-mcp-server). Each server runs locally over stdio and exposes a focused tool surface so that agents like Claude Code, Cursor, Cline, Windsurf, and GitHub Copilot Agent Mode can scaffold, inspect, validate, and modify SAP projects without guessing.

The Fiori server can list existing Fiori apps in a workspace, enumerate supported functionalities (such as adding a list report or object page), fetch their required parameters, and execute generators. The CAP server provides search_model for fuzzy queries over compiled CDS models and search_docs for local semantic search of CAP documentation. The UI5 server includes ten tools spanning project creation, integration card generation, manifest validation, UI5 linting, API reference, guidelines, and TypeScript conversion. The MDK server bundles mdk-create, mdk-gen, mdk-manage, and mdk-docs for project generation, page and action scaffolding, build/deploy/validate operations, and documentation lookups.

All four servers are open source under Apache-2.0 and maintained directly by SAP product teams (SAP/open-ux-tools, cap-js, UI5, SAP). They are designed to be used together: the Fiori server's README explicitly recommends running @cap-js/mcp-server and @ui5/mcp-server alongside it for the best agentic experience.

Tools

Each SAP Build MCP server is a separate npm package. Install only the ones relevant to your stack, or run all four together for full coverage. All servers run locally over stdio and need no API keys.

Prerequisites

• Node.js (v20.17.0 or v22.9.0+ recommended; MDK requires Node 22.14+)
• An MCP-compatible client: Claude Code, Cursor, Cline, Windsurf, or VS Code with GitHub Copilot Agent Mode

Quick install via Claude Code CLI

claude mcp add fiori-mcp -- npx --yes @sap-ux/fiori-mcp-server@latest fiori-mcp
claude mcp add cds-mcp   -- npx -y @cap-js/mcp-server
claude mcp add ui5-mcp-server -- npx @ui5/mcp-server
claude mcp add mdk-mcp   -- mdk-mcp --schema-version 26.3

For MDK, first install the package globally:

npm install -g @sap/mdk-mcp-server

Combined mcp.json configuration

{
  "mcpServers": {
    "fiori-mcp": {
      "type": "stdio",
      "timeout": 600,
      "command": "npx",
      "args": ["--yes", "@sap-ux/fiori-mcp-server@latest", "fiori-mcp"]
    },
    "cds-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cap-js/mcp-server"]
    },
    "ui5-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@ui5/mcp-server"]
    },
    "mdk-mcp": {
      "type": "stdio",
      "command": "mdk-mcp",
      "args": ["--schema-version", "26.3"]
    }
  }
}

Optional environment variables

• Fiori: LOG_LEVEL, NODE_EXTRA_CA_CERTS for custom corporate CA bundles
• UI5: UI5_MCP_SERVER_ALLOWED_DOMAINS, UI5_MCP_SERVER_CDN_URL, UI5_LOG_LVL, UI5_DATA_DIR

Source repositories

• Fiori: https://github.com/SAP/open-ux-tools (package: packages/fiori-mcp-server)
• CAP: https://github.com/cap-js/mcp-server
• UI5: https://github.com/UI5/mcp-server
• MDK: https://github.com/SAP/mdk-mcp-server

• Scaffold a new SAP Fiori elements list report or object page on top of a CAP service, with the agent gathering required parameters via list_functionalities and get_functionality_details before running execute_functionality.
• Ask an AI assistant questions like "what entities expose a releaseDate field?" and have the CAP server's search_model answer against the compiled CDS model instead of hallucinating.
• Generate, lint, and validate a SAPUI5 freestyle or TypeScript app end to end using create_ui5_app, run_ui5_linter, and run_manifest_validation.
• Build, validate, and deploy an SAP Mobile Development Kit project via mdk-create, mdk-gen, and mdk-manage without leaving the IDE.
• Look up UI5 control APIs, CAP documentation, or MDK component schemas inline while coding, replacing manual searches across SAP Help Portal.

• "Add a SAP Fiori elements list report page for the Books entity in my CAP project."
• "Search the CDS model for any entity that has a discount field and show me where it is used."
• "Create a new TypeScript SAPUI5 app called sales-overview, then run the UI5 linter and report errors."
• "Validate the manifest.json in my UI5 project and fix any issues you find."
• "Generate an MDK CRUD project for the Customer entity, build it, and produce an onboarding QR code."

• Officially built and maintained by SAP product teams (open-ux-tools, cap-js, UI5, SAP).
• Open source under Apache-2.0 with active development and aligned releases across the four servers.
• Tools are project aware: they read the local workspace, CDS models, and manifests instead of relying purely on LLM knowledge.
• Designed to compose: Fiori, CAP, and UI5 servers can run together for a complete agentic SAP development setup.

• Four separate packages to install and keep updated; there is no single binary for the whole SAP Build suite.
• Focused on SAP Build/BTP technologies, so they offer nothing for ABAP, S/4HANA backend, or non-SAP work.
• Some tools depend on optional companions (for example the Connection Manager for SAP Systems extension) to reach OData endpoints.

• ABAP Accelerator for Amazon Q Developer for ABAP-side AI assistance.
• Community SAP MCP servers indexed at https://github.com/marianfoo/sap-ai-mcp-servers for niches not covered by SAP's official set.
• Generic dev tooling MCP servers (filesystem, Git, shell) combined with SAP CLIs as a lower-level alternative.