@sap/mdk-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCHEMA_VERSION | No | The MDK schema version to use (supported: 26.3, 25.9, 25.6, 24.11, 24.7) | 26.3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mdk-createA | Creates MDK projects or entity metadata using templates (CRUD, List Detail, Base). Use this for initializing new projects or adding entity metadata to existing projects. |
| mdk-genA | Generates MDK artifacts including pages, actions, i18n files, and rule references. Returns prompts for LLM processing (pages, actions, i18n) or searches for rule examples. |
| mdk-manageB | Comprehensive MDK project management tool that handles build, deploy, validate, migrate, show QR code, and mobile app editor operations. |
| mdk-docsB | Unified tool for accessing MDK documentation including search, component schemas, property details, and examples. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: creation, documentation, artifact generation, and project management. No overlap or ambiguity.
All tools follow a consistent 'mdk-<verb>' pattern (create, gen, manage, docs), with clear and predictable naming.
Four tools cover the core workflows of an MDK server without being excessive or insufficient, well-scoped for the domain.
Covers creation, documentation, generation, and management (build, deploy, validate, migrate). Minor gaps like editing or debugging tools, but core lifecycle is addressed.