Mcp-abap-adt MCP Server

Mcp-abap-adt is an MCP integration. MCP server for SAP ABAP ADT over HTTP, RFC or SNC: repository analysis and RAP/classic ABAP CRUD.

Packages and local setup

The published npm package is @mcp-abap-adt/core, version 17.1.0. Its declared MCP transport is stdio.

The package declares MCP_ENV_PATH: Path to the .env file that states the destination (the same as the --env-path argument). The file states SAP_URL and SAP_AUTH_TYPE (basic, snc or jwt); a jwt file also states SAP_GRANT_TYPE (authorization_code or none). Without this or --mcp, the server starts in tool-inspection-only mode: nothing is read from the working directory, and SAP_ variables in the process environment alone form no destination.; AUTH_BROKER_PATH: Base directory of service-keys/ and sessions/ for a named destination chosen with the --mcp argument (one directory; a list is not split). Default: ~/.config/mcp-abap-adt (Documents\mcp-abap-adt on Windows).; MCP_BROWSER: Browser for a JWT login: chrome, edge, firefox, system, headless or none.; MCP_BROWSER_AUTH_PORT: Callback port of the JWT browser login, 1-65535.; MCP_UNSAFE: Write a named destination's session to disk (sessions/ .env) instead of keeping it in memory.; SAP_CONNECTION_TYPE: Connection type: http or rfc. SNC needs rfc (and the SAP NW RFC SDK).; SAP_SYSTEM_TYPE: System type, controls which tools are available (e.g. Programs are onprem-only).; SAP_LANGUAGE: Logon language (ISO code, e.g. 'en', 'de').; SAP_MASTER_SYSTEM: System context for on-prem create/update operations (system id).; SAP_RESPONSIBLE: Responsible user for on-prem create/update operations..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 17.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.