Claude SAP MDK connectorWhat Claude builds in your MDK mobile projects.
The Claude SAP MDK connector exposes 4 tools. Only 1 is limited to reading documentation, 3 produce or transform your project. Below: what Claude can generate, what gets pushed to Mobile Services, and what no source spells out.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug in SAP MDK for SAP mobile work
SAP presents this server as AI help for developing Mobile Development Kit applications, the cross-platform mobile apps it lets you create, validate, migrate and deploy. Its repository describes four tools: one opens the MDK documentation, three act on the project itself, from creation to deployment on SAP Mobile Services.
Create a project or add entity metadata. mdk-create starts from a CRUD, List Detail or Base template, either to initialize a new project or to add entity metadata to an existing one. Offline mode is only generated when it is explicitly requested.
Generate artifacts. mdk-gen covers pages, actions, translation files and rule references; per SAP, it returns prompts for the model to process (pages, actions, translations) or searches for rule examples.
Handle the lifecycle. mdk-manage groups build, validation, migration, the project QR code, Mobile App Editor operations and deployment to SAP Mobile Services, which takes the work beyond your own machine.
What it does not do: nothing starts without your request, since Claude calls these tools while it answers you, and no source describes a confirmation before a deployment. Chains of steps that run with no conversation are a separate trade, introduced on the Integrations hub.
Four words and an acronym
What you need to know to follow the rest.
- Connector
- What ties Claude to a tool you already use, once and for all, so it can draw on it as the conversation goes.
- Tool
- Each named operation the connector entrusts to Claude, which decides on its own which ones to run.
- Desktop extension
- A connector that executes on your machine by way of Claude Desktop, rather than on a remote server somewhere.
- Approval
- The consent Claude asks you for in the conversation before it finishes an operation that changes something.
- MCP
- The open standard that acts as a common language for connectors, so Claude can talk to outside software.
Setting up SAP MDK in Claude
- 01
Go to connectors
Open Claude Desktop settings, then Customize and Connectors, and look for SAP MDK. The directory lists it for the desktop app only; there is no web version of it.
- 02
Add the connector
On its row, choose Connect. In a Team or Enterprise workspace, a member can only add it once an Owner or Primary Owner has switched the connector on.
- 03
Confirm with your eyes open
If an authorization screen opens, go through it before accepting, since it defines the access. When the link breaks, use Disconnect and then connect it again.
The 4 tools in the Claude SAP MDK connector
SAP MDK MCP Server gives Claude 4 tools: 1 that read your account, 3 that change something in it.
One lookup tool and three that produce. Names stay as Claude displays them.
- 1 read
- 3 write
What Claude reads (1)
1 toolMDK documentation, from several angles.
mdk-docs
Opens MDK documentation from one entry point: search, component schemas, property details and examples.
What produces or transforms (3)
3 toolsThree tools that touch your project, one of them all the way to deployment. No specific confirmation appears in the sources.
mdk-create
Approval: see the ruleSets up a new MDK project, or adds entity metadata to an existing one, starting from a CRUD, List Detail or Base template.
mdk-gen
Approval: see the ruleGenerates MDK artifacts: pages, actions, translation files and rule references. For pages, actions and translations, SAP says it returns prompts for the model to process; for rules, it searches for examples.
mdk-manage
Approval: see the ruleBundles lifecycle operations: build, deploy, validate, migrate, show the project QR code, and Mobile App Editor operations. Deployment sends the project to SAP Mobile Services.
What Claude asks before touching the project
The principle: Claude stops and waits for your go-ahead before an operation it runs on your behalf.
For SAP MDK, no source spells out a per-tool confirmation, not even before a deployment to Mobile Services, so that principle is what applies. In Team or Enterprise organizations, owners set whether a member may let some actions through without a repeat prompt, and they can narrow what the connector does for everyone. Claude has no more rights than you do, on your machine or on Mobile Services, and anything closed to you stays closed to it.
Plans and SAP MDK
Across 819 sheets in the official directory, none states which plans apply. That detail is published nowhere for any single connector.
What is known is the general rule: desktop extensions install 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 turns the connector on before members can. For SAP MDK's current status, read its sheet in the directory.
What SAP MDK leaves out
No background jobs: the tools only run while Claude is answering something you asked in the conversation.
The 4 listed tools are an observed minimum; an administrator can open more. The partner badge is no security audit, and Anthropic notes on every sheet that it does not choose a publisher's tools or guarantee how they work. The only documentation is SAP's, in the server repository: neither Claude's help center nor Anthropic's developer docs have a page on it. Other ways to connect your tools are listed under Integrations.
Need help connecting SAP MDK MCP Server to Claude?
A person reads every message.
