MCP Abap Adt Compact Sse runs on your own machine — the client starts it, so there is no endpoint to ping. 230 installs a week from npm. Last commit 24 Oct 2026.
Compact MCP server for SAP ABAP ADT over HTTP+SSE: x-sap-* header credentials
What the code does
We read the source, 3 h ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
const dist = path.join(REPO, pkg, 'dist', file);
const result = spawnSync(npmCmd, jestArgs, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check MCP Abap Adt Compact Sse every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
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-compact-sse -e 'SAP_SYSTEM_TYPE=<SAP_SYSTEM_TYPE>' -- npx -y @mcp-abap-adt/compact-sse{
"mcpServers": {
"mcp-abap-adt-compact-sse": {
"command": "npx",
"args": [
"-y",
"@mcp-abap-adt/compact-sse"
],
"env": {
"SAP_SYSTEM_TYPE": "<SAP_SYSTEM_TYPE>"
}
}
}
}[mcp_servers.mcp-abap-adt-compact-sse]
command = "npx"
args = ["-y", "@mcp-abap-adt/compact-sse"]
env = { SAP_SYSTEM_TYPE = "<SAP_SYSTEM_TYPE>" }{
"mcpServers": {
"mcp-abap-adt-compact-sse": {
"command": "npx",
"args": [
"-y",
"@mcp-abap-adt/compact-sse"
],
"env": {
"SAP_SYSTEM_TYPE": "<SAP_SYSTEM_TYPE>"
}
}
}
}{
"servers": {
"mcp-abap-adt-compact-sse": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mcp-abap-adt/compact-sse"
],
"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, no request header states it): the tools offered, the connector, and how the system's answers are read. Without it the server 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_SSE_HOST (Host to listen on: 127.0.0.1 (this machine only) or 0.0.0.0 (every interface)), MCP_SSE_PORT (Port to listen on, 1-65535), SAP_MASTER_SYSTEM (System context for on-prem create/update operations (system id), when no x-sap-master-system header states it), SAP_RESPONSIBLE (Responsible user for on-prem create/update operations, when no x-sap-responsible header (or x-sap-login) states it).
Alternatives to MCP Abap Adt Compact Sse
same job, measured the same wayRead-only compact MCP server for SAP ABAP ADT over HTTP+SSE: x-sap-* header credentials
Compact MCP server for SAP ABAP ADT over Streamable HTTP: x-sap-* header credentials
Read-only MCP server for SAP ABAP ADT over HTTP+SSE: x-sap-* header credentials
Read-only MCP server for SAP ABAP ADT over Streamable HTTP: x-sap-* header credentials
MCP server for SAP ABAP ADT over HTTP+SSE: credentials from the x-sap-* headers of each connection
Read-only compact MCP server for SAP ABAP ADT over Streamable HTTP: x-sap-* headers
MCP server for SAP ABAP ADT over Streamable HTTP: credentials from x-sap-* headers per request
Compact MCP server for SAP ABAP ADT over HTTP, RFC or SNC: one tool per operation, object in args
MCP Abap Adt Compact Sse — questions
Answers built from our own checks of this server.