mdk

The MDK MCP server provides AI-assisted MDK development capabilities by exposing a set of MDK-specific tools via an MCP server interface. Once running, an AI agent can connect to this server to generate new MDK projects, create or update entity metadata using templates, validate project schemas, migrate older MDK projects to the latest schema, deploy MDK projects, and generate onboarding QR codes for quick provisioning. The server integrates with the MDK CLI tooling and templates to help agents produce production-ready MDK artifacts, guided by best practices and project context. Tools are designed to be used by AI models rather than as a stable public API, so expect occasional changes as the project evolves.

To use the server, configure your MCP client (such as OpenCode, Cursor, or a Cline-based setup in VS Code) to connect to the server endpoint with the appropriate command and schema version. The primary entry point is the mdk-mcp tool (e.g., mdk-mcp --schema-version 25.9). Through this interface, you can request generation of new MDK projects, validate schemas, migrate existing work, and access helper commands like mdk-create for project and metadata templating. Refer to the MDK tooling docs and the MCP client configuration examples in the repository readme to tailor the connection to your agent environment.

Prerequisites:

• Node.js (recommended: 22.14.0)
• npm (comes with Node.js)
• Yeoman (optional for local tooling or scaffolding)

Installation options:

1. Install from npm registry (global):

npm install -g @sap/mdk-mcp-server

2. Clone the repository and install locally, then install the server package globally:

git clone https://github.com/SAP/mdk-mcp-server.git
cd mdk-mcp-server
npm i --include=optional
npm run build
npm i -g @sap/mdk-mcp-server@.

3. Validate installation by running the server tool (example):

mdk-mcp --version

Configure your MCP client to connect to the server as described in the project's README and examples for different MCP clients (VS Code Cline, OpenCode, Cursor, etc.).

Tips and common issues:

• Ensure you’re using the supported Node.js version and have npm permissions set correctly for global installs.
• If the MCP server tool isn’t appearing in your MCP client, try restarting the client or reloading the configuration file (e.g., cline_mcp_settings.json).
• The server exposes tools like mdk-create for project/template generation; refer to the latest tool descriptions for available templates (CRUD, List Detail, Base) and their parameters.
• When deploying or validating MDK projects, ensure your environment has access to the SAP Mobile Services endpoints and Cloud Foundry prerequisites if you plan to generate or deploy .service.metadata files.
• Always verify the schema version compatibility in your MCP client configuration (the readme shows 25.9 as a default).