Open UX Tools is a collection of open-source modules for building SAP Fiori applications more efficiently. SAP Fiori developers and related projects use the reusable modules to create development tools and to contribute fixes, findings, and improvements through community collaboration.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/SAP/open-ux-toolsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/sap/open-ux-tools/fiori-mcp-server-fiori-mcp)<a href="https://agentmods.dev/mcp/sap/open-ux-tools/fiori-mcp-server-fiori-mcp"><img src="https://agentmods.dev/badge/mcp/sap/open-ux-tools/fiori-mcp-server-fiori-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/sap/open-ux-tools/fiori-mcp-server-fiori-mcp"><img src="https://agentmods.dev/badge/mcp/sap/open-ux-tools/fiori-mcp-server-fiori-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fiori-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"fiori-mcp": {
"type": "stdio",
"timeout": 600,
"command": "npx",
"args": [
"--yes",
"@sap-ux/fiori-mcp-server@latest",
"fiori-mcp"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 12 lines scan A e4367ccb80e2
fiori-mcp is an MCP server published in the GitHub repository SAP/open-ux-tools (158 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
mcp-server
MCP server for SAPUI5/OpenUI5 development. Runs locally from the @ui5/mcp-server npm package. Needs 5 environment variables to run.
webcomponents-mcp-server
MCP server for UI5 Web Components development assistance. Runs locally from the @ui5/webcomponents-mcp-server npm package.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
capforge
MCP server that makes AI agents get SAP CAP/CDS right: modern scaffolding + real validation loop against cds compile. Runs locally from the capforge npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.