SAP Fiori MCP Server (official)
Score = points from 5 automated checks. Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested version: @sap-ux/fiori-mcp-server 1.15.20. The package says it needs Node 22 or newer; first tested on Node 20.19.2, where it installed and listed its 9 tools anyway. Retested on Node 22 (v22.23.4) on 2026-10-31: installed, initialized and listed the same 9 tools. Real tool call on Node 22: list_fiori_apps with searchPath [an empty local directory] returned {"applications":[]} (no apps found; local read only, no credentials).
Tool-call test (2026-10-31, direct MCP stdio client, no LLM): pass. 1 of 1 calls passed: list_fiori_apps scanned an empty local directory and returned {"applications":[]} (no apps found). Local read only, no network, no credentials. Evidence: local test run, Oct 31, 2026.
Transport (tested 2026-10-31): stdio
Score 100/100 · Tools 9 · Token cost ~5,544 · Compare · Last tested 2026-10-31 · Version tested 1.15.20 · Package @sap-ux/fiori-mcp-server · Repo SAP/open-ux-tools
Summary: SAP Fiori MCP Server (official) completed an MCP handshake without credentials and exposed 9 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 9
- Context cost
- 5,544 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 1,402 tokens; raw tools/list total 6,946. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key needed for the tools we called
- Tested
- 2026-10-31
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @sap-ux/fiori-mcp-server (Node 20, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 9 tools listed in 3.1s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 161 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Schema context cost: ~5,544 tokens for 9 tools (25,230 bytes) · about 68% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-10-31
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 9 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-10-31 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
69a93a16a6ab: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@sap-ux/fiori-mcp-server",
"version": "1.15.20",
"registry": "npm",
"status": "working",
"tested": "2026-10-31",
"tools_count": 9,
"tools_schema_tokens_est": 5544,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @sap-ux/fiori-mcp-server` (Node 20, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 9 tools listed in 3.1s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 161 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
}
}Install
npx -y @sap-ux/fiori-mcp-server
Tools listed
search_docs, list_fiori_apps, list_sap_systems, download_odata_service_metadata, generate_fiori_app_odata, generate_fiori_app_cap, list_functionality, get_functionality_details, execute_functionality
Quick config
{
"mcpServers": {
"sap-fiori-mcp-server-official": {
"command": "npx",
"args": [
"-y",
"@sap-ux/fiori-mcp-server"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @sap-ux/fiori-mcp-server(Node 20). This is the exact command we ran on 2026-10-31. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (9 in our test).
{
"mcpServers": {
"sap-fiori-mcp-server-official": {
"command": "npx",
"args": [
"-y",
"@sap-ux/fiori-mcp-server"
]
}
}
}Test history
No dated events yet.
FAQ
Is SAP Fiori MCP Server (official) deprecated?
No. @sap-ux/fiori-mcp-server was not deprecated or archived when we last tested it on 2026-10-31.
What replaces SAP Fiori MCP Server (official)?
Nothing; SAP Fiori MCP Server (official) is not deprecated as of 2026-10-31.
Does SAP Fiori MCP Server (official) need an API key?
No. It completed an MCP handshake with no credentials and listed 9 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.