Resources · Claude connector

Claude SAP Fiori connectorWhat Claude can generate and adapt in your Fiori elements apps.

The Claude SAP Fiori connector exposes 9 tools. 5 look things up, 4 produce or transform files in your project. Here is what Claude can scaffold, how it adapts an existing app in three steps, and which settings on your side can block it.

Open the SAP Fiori MCP Server connector sheetSee the 9 tools

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes for a Fiori developer

SAP documents nine tools for this server: one searches the Fiori and UI5 documentation, three take stock of what exists on your side (Fiori apps in a folder, SAP systems in your environment, an OData service's metadata), two generate a new Fiori app, and three walk an existing app through a supported modification.

Start from an OData service. list_sap_systems shows the SAP systems stored in your environment, download_odata_service_metadata saves a service's EDMX description as metadata.xml, and generate_fiori_app_odata generates a new Fiori UI for a non-CAP OData project, such as one built on the ABAP RESTful Application Programming Model.

Add a UI to a CAP project. generate_fiori_app_cap generates a new Fiori app inside an existing CAP project.

Modify an app in three steps. list_functionality lists the supported modifications, get_functionality_details returns the required parameters, execute_functionality runs the change: adding or deleting pages, controller extensions, manifest.json properties.

What it will not do: nothing runs unless you ask in the conversation, since Claude calls these tools while it answers you. Jobs that run end to end with nobody watching are another trade, collected on the Integrations hub.

Vocabulary

Quick glossary

Five notions that make the rest of the page easier to follow.

Connector
A bridge you install once so Claude can lean on software you already run while you chat with it, without copy and paste.
Tool
A specific function the connector makes available. Claude calls it by itself whenever your request needs it.
Local server
This connector runs on your own computer through Claude Desktop, so whatever it generates lands in your folders.
Approval
The go-ahead Claude requests in the chat before an operation that touches your data or your files on your behalf.
MCP
The protocol every connector shares; it is what allows Claude to exchange with a third-party program.
Connect

Adding SAP Fiori to Claude Desktop

  1. 01

    Locate the connector

    In Claude Desktop, head to settings, then Customize and Connectors. SAP Fiori only shows up for the desktop app, since the server runs locally on your machine.

  2. 02

    Switch it on from its row

    Click Connect to add it. In a Team or Enterprise workspace, an Owner or Primary Owner switches it on for the organization first; until then, members will not see it.

  3. 03

    Check what access you grant

    If an authorization screen appears, read it before you accept, because it sets the scope. When the link stops responding, Disconnect and add it again.

Tools

The 9 tools of the Claude SAP Fiori connector

SAP Fiori MCP Server gives Claude 9 tools: 5 that read your account, 4 that change something in it.

Two groups: what Claude looks up, and what writes files into your project. Names match what Claude displays.

  • 5 read
  • 4 write

What Claude looks up (5)

5 tools

Search, inventory and preparation, with nothing produced in the project.

search_docs

Queries the documentation for Fiori elements, annotations, UI5, OPA5 guides and SAP Fiori tools against your question, using a local text-embedding model.

When it helps
you need the documentation passage on a Fiori elements or annotation topic.
Watch out
on first use, a model of about 86 MB is downloaded from HuggingFace and then cached.

Sourcegithub.com · October 1, 2026 ↗

list_fiori_apps

Scans a folder you point it at and reports the existing Fiori applications that the three adaptation tools can then work on.

When it helps
a workspace holds several projects and you need to know which Fiori apps it contains, and where, before picking one.

Sourcegithub.com · October 1, 2026 ↗

list_sap_systems

Shows the SAP systems saved in your environment, such as the SAP Fiori tools system store, as SAP describes it.

When it helps
you need to check which SAP systems are already stored on your side before fetching metadata from one of them.

Sourcegithub.com · October 1, 2026 ↗

list_functionality

Step one of three: for an existing Fiori app, given its absolute path, returns the functionalities the server supports for it, which SAP groups as page management, controller extensions and manifest.json properties.

When it helps
you want to know whether an adjustment is supported before going further.

Sourcegithub.com · October 1, 2026 ↗

get_functionality_details

Step two: for the adjustment you picked, returns the required parameters and the details you need before applying it.

When it helps
you want to know exactly which values a controller extension expects, without trial and error or guessing the format.

Sourcegithub.com · October 1, 2026 ↗

What produces files (4)

4 tools

Four tools that generate or transform files on your machine. No source documents a confirmation for them.

download_odata_service_metadata

Approval: see the rule

Pulls the EDMX description of an OData service from an SAP system and saves it on your machine as metadata.xml.

What Claude asks for
no source documents a dedicated confirmation, so the general rule for approvals applies.
When it helps
you need a local copy of a service's metadata.

Sourcegithub.com · October 1, 2026 ↗

generate_fiori_app_odata

Approval: see the rule

Produces a new Fiori UI for a non-CAP OData project, for instance a service built on the ABAP RESTful Application Programming Model.

What Claude asks for
nothing tool-specific is documented; see the general rule below.
When it helps
an OData service exists outside CAP and has no Fiori UI yet.

Sourcegithub.com · October 1, 2026 ↗

generate_fiori_app_cap

Approval: see the rule

Adds a new Fiori UI inside an existing CAP project.

What Claude asks for
no source specifies its own confirmation; the general rule for approvals covers it.
When it helps
a CAP project is in place and needs a Fiori application of its own, without starting a separate project.

Sourcegithub.com · October 1, 2026 ↗

execute_functionality

Approval: see the rule

Step three: runs the chosen modification on the existing app with the parameters supplied.

What Claude asks for
no dedicated confirmation is described; the default rule covers this tool.
When it helps
the parameters from step two are known and the modification can be applied.

Sourcegithub.com · October 1, 2026 ↗

Approvals

Before it generates, what Claude asks

The baseline: before any action taken in your name, Claude pauses and asks for your go-ahead in the conversation.

No source describes a confirmation specific to SAP Fiori's generation tools, so that baseline is what covers them. In a Team or Enterprise organization, owners choose whether a member may let some actions through without a repeat prompt, and they can restrict the connector for everyone, for instance keeping lookups and closing anything that writes. Claude also acts with your rights: an SAP system you cannot reach stays out of its reach too.

Plans

Plan availability

The official directory holds 819 sheets, and none says which plans its connector works on. That information does not exist anywhere on a per-connector basis.

What is published is the shared rule: a desktop extension such as SAP Fiori installs on Claude Desktop, and remote connectors are open to all users of Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables it before members can use it. The SAP Fiori sheet in the directory stays the up-to-date reference.

Limits

SAP Fiori's limits

Nothing runs in the background: Claude calls these tools when it answers a request, never on its own initiative.

The 9 tools on the sheet are what can be observed, not a closed list; an administrator can open others. The partner badge is not a security audit, and Anthropic reminds readers on every sheet that it does not choose a publisher's tools or vouch for their behaviour. All documentation for this connector comes from SAP, in the open-ux-tools repository; Claude has no page of its own on it. For other ways to link your tools, see Integrations.

Need help

Need help connecting SAP Fiori MCP Server to Claude?

A person reads every message.

FAQ

Claude SAP Fiori connector FAQ

01What can Claude do with the Claude SAP Fiori connector?
Claude can generate Fiori elements apps and adapt existing ones straight from the conversation. It searches the Fiori, UI5 and SAP Fiori tools docs, spots the apps in a folder, finds the SAP systems saved in your environment and fetches an OData service's metadata. It then builds an app for an OData service or inside a CAP project, and applies adjustments in three steps: list what is supported, detail the inputs, execute.
02Can Claude create or change files with SAP Fiori?
Yes, four tools produce or transform files on your machine. One saves an OData service description as metadata.xml, two generate a new application, one for an OData project and one inside a CAP project, and the last applies an adjustment to an existing app. Those adjustments cover adding or dropping pages, controller extensions and some manifest.json properties. The five other tools only look things up and leave your project as it is.
03Does Claude ask before generating a Fiori app?
No source documents a confirmation specific to SAP Fiori's tools, so Claude's default rule applies. That rule has Claude stop and ask for your go-ahead before every action it takes in your name. In a Team or Enterprise workspace, owners decide whether a member may let some actions through without a repeat prompt, and they can also shut off generation for the whole organization while leaving search open, and members cannot undo that choice from their own account.
04Which plans is SAP Fiori available on?
No official source says which plans a given connector works on, and no directory sheet shows it. The published general rule is that desktop extensions install on Claude Desktop, while remote connectors are open to all users of Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner is the one who opens the connector first. For the current status, the directory sheet is the reference to trust.
05Does Claude reach all of my SAP systems?
No, Claude only sees what your environment and your rights open up. The listing tool shows the systems saved on your side, for example in the SAP Fiori tools system store, and metadata downloads go through those same systems. A system your credentials cannot reach stays closed. At the organization level, a Team or Enterprise owner can also restrict the connector for every member, with no exception possible, whatever their own role.
06Why can SAP Fiori not reach my OData server?
One case SAP documents is an OData server using a self-signed SSL certificate. For it, SAP lists several methods, one of which is to set the NODE_EXTRA_CA_CERTS environment variable to the path of your CA certificate file. The metadata download also goes through the SAP systems stored in your environment, the ones the listing tool shows, so check that the target system is there. Beyond that, SAP's repository is the reference for connection settings.
07Claude or an automation tool for SAP Fiori?
They are not rivals; they answer different needs. With this connector, Claude assists you during development: you describe the app or the adjustment, it calls SAP's tools and shows you the outcome in the conversation. An automation tool runs steps without you, starting from a trigger. None of SAP Fiori's tools fires on its own, so there is always a request from you behind every call it makes, even a short one.
Same platform

Other docs you might need on this stack.

Browse all integrations