Claude SAPUI5 connectorWhat Claude checks and scaffolds in your UI5 projects.
The Claude SAPUI5 connector exposes 10 tools. 8 consult or analyze without producing anything, 2 create files. You will find what Claude reads from your UI5 project, what it checks, what it can scaffold, and what stays out of its reach.
Verified Trustpilot reviews · AI, automation & growth agency
What it brings to a UI5 project
Published by the UI5 team, this server gives Claude access to UI5 material while it answers you: the API reference, development best practices, version information about the framework, and checks on your project. Two of its tools scaffold something new, a UI5 application from templates or a UI Integration Card.
Work from the framework's own references. get_guidelines gives access to UI5 development best practices, and the UI5 team recommends it to retrieve the latest coding standards; get_api_reference fetches and formats the API documentation.
Check a project. run_ui5_linter relies on @ui5/linter to analyze the code and report issues, and run_manifest_validation checks the manifest against the UI5 Manifest schema.
Start something new. create_ui5_app scaffolds an application from a set of templates and create_integration_card a UI Integration Card; get_integration_cards_guidelines covers the best practices for cards.
What it does not do: nothing runs without your request, since Claude calls these tools while it answers you, and no source describes a deployment or automatic fixes after linting. For chained tasks with nobody at the keyboard, the Integrations hub gathers those other ways of working.
Page lexicon
Five markers before getting into the details.
- Connector
- The lasting hook-up between Claude and software you use every day, which Claude then draws on while it answers you.
- Tool
- A capability labelled by name, which Claude calls on its own initiative when your question warrants it.
- Local execution
- This server runs on your machine, launched by Claude Desktop: it reads and produces files at your place, not in a cloud.
- Approval
- The sign-off Claude asks you for during the exchange before it completes an action that changes your project.
- MCP
- The shared standard that lets Claude talk to external programs, and that every connector is built on.
Connecting SAPUI5 to Claude
- 01
Find SAPUI5
In Claude Desktop, open settings, then Customize and Connectors. The directory offers SAPUI5 for the desktop app only, since the server runs on your own computer.
- 02
Start the setup
Click Connect next to its name. For a Team or Enterprise workspace, an Owner or Primary Owner has to approve the connector for the organization before anyone can add it.
- 03
Read before accepting
If an authorization screen comes up, take the time to read it: it sets how far the access reaches. To fix a broken link, use Disconnect and then reconnect.
The 10 tools in the Claude SAPUI5 connector
SAPUI5 MCP Server gives Claude 10 tools: 8 that read your account, 2 that change something in it.
Two groups: what consults or analyzes, and what creates files. Names are shown exactly as Claude lists them.
- 8 read
- 2 write
What Claude consults or analyzes (8)
8 toolsDocs, project information and checks, producing nothing.
get_guidelines
Gives access to UI5 development best practices. The UI5 team points to this tool as the way to retrieve the latest coding standards for UI5 development.
run_ui5_linter
Puts your code through @ui5/linter, which it integrates, and reports the issues it finds.
get_api_reference
Fetches UI5 API documentation and formats it, so the answer rests on the official reference rather than on recollection.
get_project_info
Extracts metadata and configuration from a UI5 project, giving Claude a description of the project it is asked about.
get_version_info
Retrieves version information for the UI5 framework, the framework itself rather than any one project, as the UI5 team describes it.
get_integration_cards_guidelines
Card-specific advice: opens the best practices for developing UI Integration Cards, kept apart from the general UI5 guidelines.
run_manifest_validation
Validates your app's manifest against the UI5 Manifest schema and reports what does not match.
get_typescript_conversion_guidelines
Hands over the UI5 team's guidance for the conversion of UI5 applications, and of controls too, from JavaScript to TypeScript.
What Claude creates (2)
2 toolsTwo scaffolding tools that lay down new files. No dedicated confirmation is documented.
create_ui5_app
Approval: see the ruleCreates the starting structure of a UI5 application, picked from a set of templates provided by the UI5 team.
create_integration_card
Approval: see the ruleLays down a new UI Integration Card, the card format UI5 documents separately from full applications.
The go-ahead Claude needs before creating
Starting rule: before an action it takes for you, Claude pauses and waits for your sign-off in the conversation.
No source specifies a confirmation for SAPUI5's two creation tools, so that starting rule is what governs them. Owners of a Team or Enterprise workspace decide whether a member may let some actions through without a new prompt, and they can restrict the connector for everyone, for example keeping the checks and cutting creation. Claude never holds more rights than you do over your machine and your projects.
Plans and availability
The official directory lists 819 sheets and none publishes plan availability. For SAPUI5, that information therefore exists nowhere.
The general rule is documented, though. A desktop extension like this one is installed on Claude Desktop; remote connectors, for their part, reach every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector before members can. SAPUI5's current status is shown on its directory sheet.
Where SAPUI5 stops
No automation: these tools only run while Claude answers something you asked it to do.
The 10 tools on the sheet are what you can see, not a guaranteed boundary; an administrator can open others. The partner badge is not a security audit, and Anthropic says so on every sheet: it does not choose a publisher's tools and does not guarantee their behaviour. The only documentation comes from the UI5 team, in the server repository; neither Claude's help center nor Anthropic's docs cover it. Other ways to link your tools are on Integrations.
Need help connecting SAPUI5 MCP Server to Claude?
A person reads every message.
