MCP Abap Adt Ro runs on your own machine — the client starts it, so there is no endpoint to ping. 242 installs a week from npm. Last commit 24 Oct 2026.
Read-only MCP server for SAP ABAP ADT over HTTP, RFC or SNC: the readonly, system and search tools
Today is the operative word: we check MCP Abap Adt Ro every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-abap-adt-ro -e 'SAP_SYSTEM_TYPE=<SAP_SYSTEM_TYPE>' -- npx -y @mcp-abap-adt/core-ro
{
"mcpServers": {
"mcp-abap-adt-ro": {
"command": "npx",
"args": [
"-y",
"@mcp-abap-adt/core-ro"
],
"env": {
"SAP_SYSTEM_TYPE": "<SAP_SYSTEM_TYPE>"
}
}
}
}
[mcp_servers.mcp-abap-adt-ro]
command = "npx"
args = ["-y", "@mcp-abap-adt/core-ro"]
env = { SAP_SYSTEM_TYPE = "<SAP_SYSTEM_TYPE>" }
{
"mcpServers": {
"mcp-abap-adt-ro": {
"command": "npx",
"args": [
"-y",
"@mcp-abap-adt/core-ro"
],
"env": {
"SAP_SYSTEM_TYPE": "<SAP_SYSTEM_TYPE>"
}
}
}
}
{
"servers": {
"mcp-abap-adt-ro": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mcp-abap-adt/core-ro"
],
"env": {
"SAP_SYSTEM_TYPE": "<SAP_SYSTEM_TYPE>"
}
}
}
}
Put your own value in place of
<SAP_SYSTEM_TYPE> (System type, required (here or as --system-type; no default, never guessed): the tools offered (e.g. Programs are onprem-only), the connector, and how the system's answers are read. Without it a destination does not start).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
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/<name>.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_LANGUAGE (Logon language (ISO code, e.g. 'en', 'de')).
Read-only MCP server for SAP ABAP ADT over HTTP+SSE: x-sap-* header credentials
Read-only compact MCP server for SAP ABAP ADT: the compact tools that change nothing
MCP server for SAP ABAP ADT over HTTP, RFC or SNC: repository analysis and RAP/classic ABAP CRUD
Read-only MCP server for SAP ABAP ADT over Streamable HTTP: x-sap-* header credentials
Compact MCP server for SAP ABAP ADT over HTTP, RFC or SNC: one tool per operation, object in args
Read-only compact MCP server for SAP ABAP ADT over HTTP+SSE: x-sap-* header credentials
Read-only compact MCP server for SAP ABAP ADT over Streamable HTTP: x-sap-* headers
MCP server for Yandex.Webmaster search queries (read-only).
Answers built from our own checks of this server.