UI5 MCP Server
OFFICIAL SERVERSAP's MCP server for building, checking and documenting SAPUI5 and OpenUI5 apps
Generate and modify SAP Fiori elements apps for CAP and OData projects from a coding assistant
Official · SAP TypeScript Local · stdio Developer tools
79 popularity score ★ 162 ↓ 118k/wk
Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.
claude mcp add sap-fiori -- npx --yes '@sap-ux/fiori-mcp-server@<VERSION>' fiori-mcp{
"mcpServers": {
"sap-fiori": {
"command": "npx",
"args": [
"--yes",
"@sap-ux/fiori-mcp-server@<VERSION>",
"fiori-mcp"
]
}
}
}{
"mcpServers": {
"sap-fiori": {
"command": "npx",
"args": [
"--yes",
"@sap-ux/fiori-mcp-server@<VERSION>",
"fiori-mcp"
]
}
}
}{
"servers": {
"sap-fiori": {
"type": "stdio",
"command": "npx",
"args": [
"--yes",
"@sap-ux/fiori-mcp-server@<VERSION>",
"fiori-mcp"
]
}
}
}[mcp_servers.sap-fiori]
command = "npx"
args = ["--yes", "@sap-ux/fiori-mcp-server@<VERSION>", "fiori-mcp"]gemini mcp add --scope user sap-fiori npx -- --yes '@sap-ux/fiori-mcp-server@<VERSION>' fiori-mcpLOG_LEVEL |
Optional: Log level: off, error (default), warn, info, debug or verbose; logs go to ~/.fioritools/fiori-mcp-server.log. |
|---|---|
SAP_FIORI_MCP_ADP_TOOLS |
Optional: Set to true to expose the six adaptation-project tools. |
NODE_EXTRA_CA_CERTS |
Optional: Path to a CA certificate for SAP systems with self-signed TLS certificates. |
SAP_UX_FIORI_TOOLS_DISABLE_TELEMETRY |
Optional: Set to true to turn off usage telemetry, which is on by default. |
HF_HOME |
Optional: Where the search embedding model is cached (default ~/.cache/huggingface/hub). |
SAP's own MCP server for building SAP Fiori user interfaces. It runs locally over stdio as the `fiori-mcp` program in the @sap-ux/fiori-mcp-server package, which is part of SAP's open-ux-tools monorepo. A coding assistant can use it to create a Fiori elements app inside an existing SAP Cloud Application Programming Model (CAP) project, or to create one against an OData service (for example an ABAP RAP service) on an SAP system.
To change an existing app, the assistant follows three steps. It lists the changes the server supports for that app path, fetches the parameters one change needs, then runs it. Supported changes include adding or deleting pages, adding controller extensions and editing manifest.json settings such as the layout. Other tools find Fiori apps under a folder, list the SAP systems saved on the machine, download an OData service's EDMX metadata into metadata.xml, and do semantic search over the Fiori elements, annotations, UI5, OPA5 and SAP Fiori tools docs.
The default build exposes 9 tools. The tool registry in the source (src/tools/index.ts, version 1.15.11) adds 6 more for SAPUI5 adaptation projects when SAP_FIORI_MCP_ADP_TOOLS is set to true. The README does not mention these: they generate an adaptation project, start the adaptation editor, write controller extensions, drive Runtime Authoring in the editor page, read the project's OData metadata and look up UI5 control API docs. The changelog dates them to 1.15.0.
The README suggests pinning a version in the npx arguments rather than using @latest, and it ships a set of rules to paste into the assistant's own rules file.
| Runtime | Node.js 22+ |
|---|
Node.js 22 or later (the package's engines field says >=22.x). npx is used to fetch and start it. You need a CAP project or an SAP system with an OData service to work on. Prompts that target an SAP system need a connection saved first, for example with the Connection Manager for SAP Systems extension or the SAP Fiori tools system store. The first doc search downloads an embedding model of about 86 MB from HuggingFace Hub.
It changes Fiori elements apps only through the change types that list_functionality reports for each app. search_docs searches the most recent indexed UI5 documentation, not the UI5 version your app uses. It cannot find an OData service by name or technical id: download_odata_service_metadata needs a service path, and the tool text points to a separate Service Center MCP server for lookups by name. The adaptation-project tools stay hidden unless SAP_FIORI_MCP_ADP_TOOLS=true is set. For self-signed SAP certificates the docs advise NODE_EXTRA_CA_CERTS, and warn that NODE_TLS_REJECT_UNAUTHORIZED=0 turns off all TLS checks and suit non-production use only.
Developers who build SAP Fiori elements front ends on CAP or ABAP RAP services and want an assistant to scaffold and adjust apps with SAP's own generators rather than hand-written code. It runs on your machine and writes into your project folders, so it fits local IDE workflows in Claude Code, Cline, Cursor or Windsurf. It is little use outside the SAP UI5/Fiori stack. If you only need UI5 docs search, a lighter docs server is enough; this one brings the full generator set and a local embedding model.
search_docslist_fiori_appslist_sap_systemsdownload_odata_service_metadatagenerate_fiori_app_odatagenerate_fiori_app_caplist_functionalityget_functionality_detailsexecute_functionalitygenerate_adaptation_projectopen_adaptation_editoradp_controller_extensionrun_rta_workflow_stepread_odata_metadata_adplookup_ui5_documentation