Agentic Engineering for SAP BTP Extensions: Using the CAP, Fiori and UI5 MCP Servers to Build Faster and Cleaner
How a modern SAP BTP "extension factory" uses MCP-aware AI coding assistants — and the guardrails that keep quality high.
AI coding assistants are only as good as the context they have. Generic models often hallucinate deprecated UI5 APIs, invent CDS syntax or generate Fiori manifests that fail validation. SAP has addressed this by publishing official MCP servers for developers that ground coding agents in real SAP tooling. Used well, they turn a BTP team into an extension factory.
1. The developer MCP servers you should know
CAP MCP server (@cap-js/mcp-server, command cds-mcp) — lets the assistant search your compiled CDS model (entities, services, endpoints) and the CAP documentation, so generated code follows real CAP APIs.
SAP Fiori MCP server (@sap-ux/fiori-mcp-server) — generates and modifies Fiori elements applications (e.g., "add a list report to my CAP project") using Fiori tools under the hood.
UI5 MCP server (@ui5/mcp-server) — UI5 API reference, coding guidelines (get_guidelines), the UI5 linter, manifest validation, project scaffolding and UI Integration Card creation.
Others worth knowing: the UI5 Web Components MCP server, the SAP Mobile Development Kit MCP server, and the ADT MCP server for ABAP Development Tools for VS Code.
Note the difference from runtime MCP: these servers help developers build apps; the @cap-js/mcp adapter and the Integration Suite MCP gateway help agents use apps.
2. A typical configuration
Most MCP clients (VS Code agents, Cline, Claude Code, Cursor, OpenCode) accept a JSON configuration like this:
{
"mcpServers": {
"cap": { "command": "cds-mcp" },
"ui5": { "command": "npx", "args": ["@ui5/mcp-server"] },
"fiori":{ "command": "npx", "args": ["@sap-ux/fiori-mcp-server"] }
}
}Install the CAP server globally first with npm i -g @cap-js/mcp-server. Check each package's README for the current invocation, as these tools evolve quickly.
3. Add an AGENTS.md to every repository
MCP servers only help if the assistant actually calls them. We add project rules such as:
- Before writing CDS or CAP code, search the model and docs with the CAP MCP server.
- Before using any UI5 control or API, call get_guidelines and check the API reference.
- After changing UI5 code, run the UI5 linter and fix all findings.
- Use the Fiori MCP server to add or change Fiori elements pages; do not hand-edit annotations blindly.
- Never call unreleased S/4HANA APIs; use released APIs from SAP Business Accelerator Hub.SAP-samples also publishes reusable AGENTS.md and skill sets for CAP and Fiori elements agentic development — a solid starting point.
4. Our extension-factory workflow
Specify — business analyst writes the user story and acceptance criteria; architect fixes the clean-core boundaries (which released APIs, which events).
Model — CDS domain model and service definitions, reviewed by a senior developer.
Generate — assistant scaffolds handlers and Fiori elements UIs using the MCP servers.
Verify — UI5 linter, manifest validation, cds lint, unit tests with cds.test, and human code review. AI output is never merged unreviewed.
Deploy — MTA build and CI/CD to Cloud Foundry, with XSUAA/IAS, Destination and HTML5 repository configured.
Agent-enable — annotate the agent-facing service with @mcp or publish via the Integration Suite MCP gateway.
5. Guardrails that protect quality
Human in the loop for architecture. AI accelerates implementation; senior consultants own data model, security and integration design.
No production credentials in the IDE. Restrict the OData domains the UI5 MCP server may reach (it supports an allow-list via environment variable) and use sandbox systems.
Version pinning. Pin MCP server versions in team setup scripts to keep results reproducible.
Measure. Track lead time, defect rate and linter findings per sprint to prove the gain to clients.
6. What this means for customers and partners
For customers it means faster, cheaper, cleaner extensions — without compromising the clean core. For SI partners it is a capacity multiplier: a small, well-trained team grounded in SAP's own tooling can deliver what used to need a much larger team, with consistent quality.
FAQ
Do these MCP servers send my code to SAP? They run locally (stdio) in your environment; your AI assistant's own data policy still applies — choose an enterprise-approved assistant.
Do they replace SAP Build Code? No — they complement it. Teams can use them in SAP Build Code, Business Application Studio or local VS Code.
Scale your BTP delivery with us
Raven Infotech runs an agentic-engineering extension factory for SAP BTP — CAP, Fiori elements, UI5 and integrations — and trains partner teams in the same methodology. Ask about our delivery pods and team enablement programmes.
Comments