sap-ux-fiori-tools — GitHub Copilot plugin: build SAP Fiori apps
Wires the SAP Fiori MCP server into your agent, so it can scaffold Fiori Elements apps on CAP or ABAP OData, add charts, and write OPA5 tests.
copilot plugin install sap-ux-fiori-tools@awesome-copilotWhat sap-ux-fiori-tools does
The plugin ships the @sap-ux/fiori-mcp-server MCP server plus seven skills the agent picks up as it works. One skill covers creating Fiori Elements and standalone apps, another handles analytical charts and visual filters, others deal with tree tables, OPA5 integration tests, ESLint rules and Fiori tools CLI commands.
Under the hood it is a manifest, a launch config for the MCP server with a pinned version, and a skills/ folder. Plugin versioning runs separately from the server, so a server release does not move the manifest on its own. Edit a SKILL.md and you bump the version in the manifest by hand.
The plugin used to be called sap-fiori-mcp-server. Marketplace installs get the old slug rewritten on the next sync for you. A direct git URL to the old path does not: that one needs a manual reinstall. Skills do nothing until the MCP server is actually running, so check that first.
What it helps with
- scaffold a Fiori Elements app against a CAP service
- add an analytical chart with visual filters to a list page
- write an OPA5 test for a navigation flow
- drop a tree table into an existing app
- run Fiori tools CLI commands from the agent chat
Example prompts for the agent
- Generate a Fiori Elements app from the OData service in
service.cds - Add visual filters to the analytical list page
- Write an OPA5 test that opens a detail page
How to install sap-ux-fiori-tools
Command from the source
copilot plugin install sap-ux-fiori-tools@awesome-copilotStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about sap-ux-fiori-tools
How do I install sap-ux-fiori-tools in GitHub Copilot?
Run copilot plugin install sap-ux-fiori-tools@awesome-copilot.
What does sap-ux-fiori-tools do?
It starts the SAP Fiori MCP server and gives the agent seven skills: app generation, charts, visual filters, OPA5 tests, ESLint, tree tables and the CLI.
I had the old sap-fiori-mcp-server plugin. Do I need to do anything?
A marketplace install migrates on the next sync. If you added it through a git URL to the old path, uninstall it and install the new one manually.
Source text
fiori · Apache-2.0
# SAP Fiori Tools Plugin for Coding Agents Plugin distribution assets for the SAP Fiori MCP server, enabling AI coding assistants (Claude Code and GitHub Copilot) to develop SAP Fiori applications. ## What is in this directory | Asset | Purpose | |---|---| | `.claude-plugin/plugin.json` | Claude Code plugin manifest | | `.github/plugin/plugin.json` | GitHub Awesome Copilot plugin manifest | | `.mcp.json` | MCP server launch config (pinned version) | | `skills/` | Seven skills loaded by Claude Code and Awesome Copilot | ## Skills | Skill | Description | |---|---| | `sap-fiori-app-development` | Fiori Elements and standalone app creation | | `sap-fiori-analytical-chart` | Analytical chart and visual filter configuration | | `sap-fiori-add-visual-filter` | Adding visual filters to Analytical List Pages | | `sap-fiori-create-cli` | SAP Fiori tools CLI commands | | `sap-fiori-eslint-plugin` | ESLint plugin for Fiori development | | `sap-fiori-opa5-test-development` | OPA5 integration test development | | `sap-fiori-tree-table` | Tree table implementation | ## MCP Server The MCP server binary is published as [@sap-ux/fiori-mcp-server](https://www.npmjs.com/package/@sap-ux/fiori-mcp-server) on npm. Source code lives in [packages/fiori-mcp-server](../../packages/fiori-mcp-server/). ## Installing in Claude Code Install via the Claude Code CLI: ```bash claude plugin install https://github.com/SAP/open-ux-tools.git#plugins-coding-agents/fiori ``` Or add via the Claude Code marketplace: search for `sap-ux-fiori-tools`. ## Migrating from the old plugin name The plugin was previously distributed as `sap-fiori-mcp-server` from `packages/fiori-mcp-server/`. It has been renamed to `sap-ux-fiori-tools` and relocated to this directory. If you installed via the Claude Code marketplace, the rename is handled automatically — Claude Code rewrites the old slug to the new one on next sync via the `renames` map in `claude-plugins-official`. If you installed via a direct git URL pointing at the old path, reinstall manually: ```bash claude plugin uninstall sap-fiori-mcp-server claude plugin install https://github.com/SAP/open-ux-tools.git#plugins-coding-agents/fiori ``` ## Version Alignment Plugin versions in `.claude-plugin/plugin.json` and `.github/plugin/plugin.json` are independent of the MCP server version. **Automated** — on each `@sap-ux/fiori-mcp-server` npm release, two scripts run in CI: - `packages/fiori-mcp-server/scripts/sync-mcp-manifests.cjs` — updates `server.json` and the pinned server version in `.mcp.json` - `plugins-coding-agents/fiori/scripts/sync-plugin-manifests.cjs` — patch-bumps the plugin `version` in both `.claude-plugin/plugin.json` and `.github/plugin/plugin.json` **Manual** — when skills change (editing a `SKILL.md`, adding or removing a skill), bump the `version` field in **both** `.claude-plugin/plugin.json` and `.github/plugin/plugin.json` by hand as part of the same commit.
© SAP SE · Apache-2.0 · SAP/open-ux-tools