Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.
SAP Fiori MCP Server
by SAP
Released
v1.12.7
Apache-2.0
Summary
SAP's official MCP server for SAP Fiori tools — generates Fiori elements apps from OData services or CAP projects and applies guided modifications to existing ones.
Features
- Generates SAP Fiori elements apps for CAP projects and for OData/RAP services
- Three-step guided modification: list, detail, then execute a functionality
- Reads the SAP Fiori tools system store so users can name a system, not a URL
- Downloads OData EDMX metadata to metadata.xml before generation
- Local semantic docs search over Fiori elements, annotations, UI5 and OPA5
- stdio transport launched via npx — no global install
- Documented setup for Claude Code, Cline, Cursor and Windsurf
- Self-signed SSL handling for on-premise systems, and telemetry opt-out
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
The SAP Fiori MCP Server is SAP's official Model Context Protocol server for SAP Fiori development, published from the SAP/open-ux-tools monorepo as @sap-ux/fiori-mcp-server. It lets a coding assistant scaffold and modify SAP Fiori applications from natural-language prompts — "add a SAP Fiori elements list report app to my CAP project", or generate one against a specific OData V4 service URL.
Generation comes in two flavours. generate_fiori_app_cap creates a Fiori UI application inside an existing SAP Cloud Application Programming Model project, while generate_fiori_app_odata targets non-CAP OData projects such as ABAP RESTful Application Programming Model services. Supporting tools round out the workflow: list_sap_systems reads the SAP Fiori tools system store so the user can name a system rather than paste a URL, and download_odata_service_metadata pulls that service's EDMX metadata to metadata.xml before generation runs.
Modifying an existing app is deliberately a three-step handshake rather than one open-ended call. list_functionality reports what the app at a given path actually supports — adding and deleting pages, adding and modifying controller extensions, and similar — then get_functionality_details returns the parameters for the chosen change, and execute_functionality applies it. list_fiori_apps scans a directory to find the candidates in the first place.
Documentation search is handled locally: search_docs covers SAP Fiori elements, annotations, UI5, OPA5 guides and SAP Fiori tools docs using an all-MiniLM-L6-v2 text-embedding model, roughly 86 MB, downloaded from the Hugging Face Hub on first use and cached under HF_HOME/TRANSFORMERS_CACHE so later starts need no network.
It runs over stdio and launches through npx, so there is nothing to install globally; setup snippets are documented for Claude Code, Cline, Cursor and Windsurf. SAP recommends pairing it with @cap-js/mcp-server and @ui5/mcp-server. The README also covers self-signed SSL certificate handling for on-premise SAP systems and how to opt out of telemetry. Apache-2.0.
Related MCP Servers
Hugging Face's official MCP server — search the Hub's models, datasets and Spaces, read repository files, and call thousands of Gradio applications as tools from one remote endpoint.
4 views
Qase test management over MCP: 36 task-oriented tools for cases, runs, results, defects and QQL search, hosted at mcp.qase.io or self-run with your own API token.
6 views
Arm's official MCP server for porting and tuning software on Arm — semantic docs search, codebase migration scanning, container architecture checks and LLVM-MCA assembly analysis.
8 views