CapabilityAI & AgentsWeb Components

Agent access to your Fiori app

An assistant that can only describe the steps leaves the developer to perform them. fiori-mcp lets it create and edit the application directly, driving the generators and editors Fiori tools already ship rather than reimplementing them — which also means it reaches what those reach and stops where they stop.

Showing artifacts, examples and content with confirmed Web Components applicability. View All UI5

Overview

SAP SHIPS

No core answer is documented.

Not covered: SAP does publish an MCP server for this flavor, @ui5/webcomponents-mcp-server, but its tools fetch a named component's API, a framework's integration guide or the documentation set itself; none reads the project the agent is actually working in.

Unmapped rather than not-applicable: a Web Components project has files of its own — component definitions, a package.json, a build — for an agent to read and act on, the same as a freestyle UI5 or Fiori elements one, so the concern is not structurally absent the way routing or the flexibility layer are.

NOBODY YET

No artifact is documented here yet.

Artifacts

Nothing is mapped here yet.

Details

Coverage
stateunmapped, UI5, Web Components
assessed
also inCAP, ABAP, BTP/BAIP
For your agent
Ref
capability:agent-code-access
JSON
/capabilities/agent-code-access.json
MCP
Connecting an agent