Abap Adt MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 333 installs a week from npm. Last commit 16 Sep 2026.
ABAP development from Claude and other MCP hosts: source, transports, tests, ATC, debugger
We read the source, 23 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const file = path.join(pkgDir, fileName);
execFile(config.command, config.args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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 abap-adt-mcp -- npx -y abap-adt-mcp
{
"mcpServers": {
"abap-adt-mcp": {
"args": [
"-y",
"abap-adt-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.abap-adt-mcp]
command = "npx"
args = ["-y", "abap-adt-mcp"]
{
"mcpServers": {
"abap-adt-mcp": {
"args": [
"-y",
"abap-adt-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"abap-adt-mcp": {
"args": [
"-y",
"abap-adt-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
SAP_SYSTEMS_FILE (Path to a JSON file mapping destination names to system configs (url, client, authType basic/sso/oauth, credentials). Recommended; keep the file mode 0600. See systems.example.json), SAP_SYSTEMS (Inline JSON map of destinations (same shape as SAP_SYSTEMS_FILE). Contains credentials — prefer SAP_SYSTEMS_FILE), SAP_DEFAULT_DESTINATION (Destination name used when a tool call omits `destination` (alternatively mark an entry with "default": true)), SAP_AUTH_TYPE (Default auth type for entries that don't specify one: sso (default), basic, or oauth), MCP_HTTP_PORT (When set (1024-65535), serve Streamable HTTP on http://127.0.0.1:<port>/mcp with bearer-token auth instead of stdio), MCP_HTTP_HOST (Bind address for the HTTP transport (default 127.0.0.1). Set 0.0.0.0 only inside containers that publish the port), MCP_HTTP_TOKEN (Bearer token for the HTTP transport; auto-generated and written to ~/.abap-adt-mcp/http-token when unset), MCP_HTTP_MAX_SESSIONS (Maximum concurrent MCP sessions on the HTTP transport (default 16); further initialize requests get 503), MCP_HTTP_MAX_BODY_BYTES (Largest request body the HTTP transport accepts, in bytes (default 4194304); larger bodies are refused with HTTP 413), MCP_HTTP_SESSION_TTL_MINUTES (Idle minutes after which an HTTP session (and its SAP sessions/locks) is closed (default 30)), MCP_HTTP_ALLOWED_ORIGINS (Comma-separated Origin values allowed on the HTTP transport (loopback origins always allowed when bound to loopback; * allows any)), MCP_HTTP_ALLOWED_HOSTS (Comma-separated Host header values allowed (DNS-rebinding protection; loopback hosts always allowed when bound to loopback)), MCP_EXPORT_ROOT (When set, exportPackageSources may only write inside this directory), MCP_AUDIT_FILE (Path of a JSONL audit trail: one record per tool call (tool, destination, duration, outcome ok/error/denied/unavailable, policy gate, redacted argument summary)), MCP_READ_ONLY (Set to 1 to make every destination read-only (server-side; only read-only annotated tools plus login/logout run). Per-destination policies live in systems.json), MCP_TOOLSETS (Toolsets to publish: comma list (core,source,objects,transports,analysis,tests,atc,data,discovery,runtime,refactoring,rap,services,git,debugger,traces) or a preset: all (default) or focused), MCP_DISABLED_TOOLSETS (Toolsets to hide, comma list (core cannot be disabled)), MCP_MAX_RESPONSE_CHARS (Character budget for a single tool response before results are paged/truncated (default 40000, minimum 5000). Raise it if your MCP host accepts larger tool outputs), SAP_ALLOW_REENTRANCE_TICKET (Set to 1 to enable the reentranceTicket tool (disabled by default: it returns a live SAP logon credential into the conversation)), SAP_URL (Legacy single-system mode: base URL of the SAP system, e.g. https://host:44300), SAP_USER (Legacy single-system mode: SAP username), SAP_PASSWORD (Legacy single-system mode: SAP password), SAP_CLIENT (Legacy single-system mode: SAP client number, e.g. 100), SAP_LANGUAGE (Legacy single-system mode: logon language, e.g. EN), SAP_BROWSER_PATH (SSO destinations: path to a Chromium/Chrome/Edge binary for the browser login (auto-detected when unset)), SAP_BROWSER_PROFILE_DIR (SSO destinations: directory of the persistent browser profile that keeps the identity-provider session (default ~/.abap-adt-mcp/sso/<host>)), SAP_TLS_INSECURE (Legacy single-system mode: set to 1 to skip TLS certificate verification for that system only (sandboxes with self-signed certificates)), SAP_OAUTH_TOKEN_URL (Legacy single-system mode with SAP_AUTH_TYPE=oauth: OAuth2 token endpoint (client_credentials)), SAP_OAUTH_CLIENT_ID (Legacy single-system mode with SAP_AUTH_TYPE=oauth: OAuth2 client id), SAP_OAUTH_CLIENT_SECRET (Legacy single-system mode with SAP_AUTH_TYPE=oauth: OAuth2 client secret), SAP_OAUTH_SCOPE (Legacy single-system mode with SAP_AUTH_TYPE=oauth: optional OAuth2 scope), MCP_PROFILE_GATE (Platform gate for toolsets the destination does not expose (debugger, traces, abapGit, ...): enforce (default, refuse before calling SAP), warn (log only) or off), MCP_SOURCE_CACHE_TTL_SECONDS (Lifetime of the per-session source cache used by grepPackage, cdsViewInfo and syntaxCheckCode (default 300; 0 keeps entries until logout)), MCP_CACHE_DIR (Directory for the cached SAP cloudification repository used by apiReleaseState (default ~/.abap-adt-mcp/cache)).
The author declared them in the registry entry; get the values from the project itself.
Develop, test, analyze, and operate SAP ABAP systems through ADT from AI coding agents.
MCP server for iOS and Android Mobile Development, Automation and Testing
MCP server for R package development using usethis, devtools, renv, and testthat
MCP server for agent-driven React Native and Expo development and mobile testing
Flaky test detection, root cause analysis, and fix suggestions for development teams.
MCP server for AI-assisted coding with development history: git, tests, Copilot.
Local Sapiom developer MCP for authoring, testing, deploying, and inspecting agents.
MCP server for Appium mobile automation on iOS and Android devices with test creation tools.
Answers built from our own checks of this server.