All servers / Developer / SAP MDK MCP server
SAP MDK MCP server
Model Context Protocol (MCP) server for AI-assisted development of MDK applications.
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-18 on package version 0.4.3. Package: @sap/mdk-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 12 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (134.2 seconds including download)
- Tools offered: 5
- Last published: 2026-11-15
- Weekly downloads (npm): 11,967
- License: Apache-2.0 · Direct dependencies: 17
Notes
- The package runs install scripts, which execute code when you install it.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
mdk-create7 of 7 parameters describedCreates MDK projects or entity metadata using templates (CRUD, List Detail, Base). Use this for initializing new projects or adding entity metadata to existing projects. Supports CAP projects - automatically creates MDK apps in the app/ folder with proper naming and configuration.
mdk-gen8 of 8 parameters describedGenerates MDK artifacts including pages, actions, i18n files, and rule references. Returns prompts for LLM processing (pages, actions, i18n) or searches for rule examples.
mdk-manage3 of 3 parameters describedComprehensive MDK project management tool that handles build, deploy, validate, migrate, show QR code, and mobile app editor operations.
mdk-docs6 of 6 parameters describedUnified tool for accessing MDK documentation including search, component schemas, property details, and examples.
mdk-fetch-mobile-metadata5 of 5 parameters describedFetches OData metadata from a Mobile Services destination and automatically saves it to .service.metadata file in the project. This retrieves the $metadata document from a configured destination in a Mobile Services application and creates the service metadata configuration file. Requires CF CLI authentication (cf login).
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.