MCP Abap Adt Http

Name: MCP Abap Adt Http
Author: fr0ster

by fr0sterversion 20.0.0i★ –iRuns on your computer

Registry nameio.github.fr0ster/mcp-abap-adt-http

Install

Overview

Description from the maker (original English)

MCP server for SAP ABAP ADT over Streamable HTTP: credentials from x-sap-* headers per request

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 1.2K/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: Streamable HTTP
Category: Other
You need to fill in: SAP_SYSTEM_TYPE

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: SAP_SYSTEM_TYPE, MCP_HTTP_HOST, MCP_HTTP_PORT, SAP_MASTER_SYSTEM, SAP_RESPONSIBLE

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "abap-adt-http": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/http"
      ],
      "env": {
        "SAP_SYSTEM_TYPE": "your-value",
        "MCP_HTTP_HOST": "your-value",
        "MCP_HTTP_PORT": "your-value",
        "SAP_MASTER_SYSTEM": "your-value",
        "SAP_RESPONSIBLE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add abap-adt-http --env SAP_SYSTEM_TYPE=your-value --env MCP_HTTP_HOST=your-value --env MCP_HTTP_PORT=your-value --env SAP_MASTER_SYSTEM=your-value --env SAP_RESPONSIBLE=your-value -- npx -y @mcp-abap-adt/http

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "abap-adt-http": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/http"
      ],
      "env": {
        "SAP_SYSTEM_TYPE": "your-value",
        "MCP_HTTP_HOST": "your-value",
        "MCP_HTTP_PORT": "your-value",
        "SAP_MASTER_SYSTEM": "your-value",
        "SAP_RESPONSIBLE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "abap-adt-http": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/http"
      ],
      "env": {
        "SAP_SYSTEM_TYPE": "your-value",
        "MCP_HTTP_HOST": "your-value",
        "MCP_HTTP_PORT": "your-value",
        "SAP_MASTER_SYSTEM": "your-value",
        "SAP_RESPONSIBLE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SAP_SYSTEM_TYPE required env
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 serve…
MCP_HTTP_HOST env
Host to listen on: 127.0.0.1 (this machine only) or 0.0.0.0 (every interface).
MCP_HTTP_PORT env
Port to listen on, 1-65535.
SAP_MASTER_SYSTEM env
System context for on-prem create/update operations (system id), when no x-sap-master-system header states it.
SAP_RESPONSIBLE env
Responsible user for on-prem create/update operations, when no x-sap-responsible header (or x-sap-login) states it.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account fr0ster, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18444 servers in this category
Published to the registry more recently than 72% of the other 18444 servers in this category
Basic checks equal to or better than 100% of the other 18444 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Abap Adt Http safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SAP_SYSTEM_TYPE

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (20.0.0) reached the registry 16 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Egovframe Scaffold MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

Install

Egovframe Scaffold MCP

eGovFrame (전자정부 표준프레임워크) projects: templates, components, CRUD, build, 5.x migration, dependencies

by EricSeokgonEarly↓ 1.4K/wkUpdated today

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mcp-abap-adt: Your Gateway to ABAP Development Tools (ADT)

mcp-abap-adt is an MCP server for ABAP ADT in SAP ECC/S/4HANA (on-premise) and SAP BTP ABAP Cloud systems. It gives agents controlled access to real ABAP repositories through ADT, so analysis and changes are grounded in system data instead of assumptions. It is built for AI-assisted pair programming (AIPNV: AI Pairing, Not Vibing), not autopilot vibe coding.

Primary workflows:

Deep ABAP analysis: where-used, object metadata, repository navigation, object structure, semantic analysis, dependency and impact exploration.
High-level ABAP development: rapid CRUD and iterative updates for RAP and classic ABAP artifacts (classes, interfaces, function groups/modules, programs, DDIC, CDS/view/service artifacts), validated through ADT flows.

Why teams use it:

Full CRUD (not read-only): create, read, update, and delete ABAP artifacts
Works with On-Premise (ECC/S/4HANA) and ABAP Cloud (BTP) systems
Legacy systems (BASIS < 7.50) are not supported at present: that support is parked on the parked/legacy-support branch until it can be tried against a live legacy system
Three authentications over stdio: basic (HTTP or RFC), SNC (passwordless, RFC), JWT with browser login (service key, ABAP or XSUAA); a JWT you already hold goes in the x-sap-jwt-token header of mcp-abap-adt-http / mcp-abap-adt-sse
Multiple transports: stdio, HTTP, SSE
Several installation variants: the full server (@mcp-abap-adt/core) or the compact one (@mcp-abap-adt/compact), each connecting to the system over HTTP, RFC or SNC — see Installation variants
Rich tool surface for ABAP objects, metadata, transports, and search

Authorization & Destinations (Important): A *destination* is the filename of a service key stored locally. You place service keys in the service-keys directory, and use --mcp= to select which one to use. This is the primary auth model for on‑prem and BTP systems. See Authentication & Destinations.

You can configure MCP clients either manually (JSON/TOML) or via the configurator CLI (@mcp-abap-adt/configurator, repo: mcp-abap-adt-conf).

Getting Started
Architecture
Quick Start
Use Cases
Target Users
Capabilities (High-Level Focus)
Terminology
Authorization & Destinations
Registries
Features
Documentation
Dependencies
Running the Server

Getting Started

Pick a variant first — full or compact server, and HTTP, RFC or SNC to the system. HTTP needs nothing but Node.js 22 or 24; RFC and SNC need the SAP NW RFC library when the server runs — SAP GUI's 64-bit sapnwrfc.dll on Windows, else the SAP NW RFC SDK; the RFC module comes prebuilt for Linux x64 (glibc), Windows x64 and macOS ARM64, and npm install compiles nothing. Installation variants has the table and the commands; RFC Setup the steps. To run without Node.js on a machine, build your own portable executable — Node.js and your SAP NW RFC SDK inside.

Install the server and configure your client using the configurator:

npm install -g @mcp-abap-adt/core

npm install -g @mcp-abap-adt/configurator

stdio (destination)

mcp-conf --client cline --name abap --mcp TRIAL

HTTP (streamable HTTP)

mcp-conf --client copilot --name abap --transport http --url http://localhost:3000/mcp/stream/http

Full configurator usage (separate repo): CLIENT_INSTALLERS.md.

Terminology

Destination: a local service key filename. You store service keys in the standard service-keys directory, and pass the filename (without extension) via --mcp= to select which system to use.

See docs/user-guide/TERMINOLOGY.md for the full list.

Authorization & Destinations

Destination-based auth is the default. Drop service keys into the standard platform folder and use the filename as your destination:

mcp-abap-adt --mcp=TRIAL --system-type=cloud

Standard service key paths:

Unix (Linux/macOS): ~/.config/mcp-abap-adt/service-keys/ .json
Windows: %USERPROFILE%\\Documents\\mcp-abap-adt\\service-keys\\ .json

mcp-abap-adt (stdio) supports exactly three authentications, each a destination stated in a service key, a .env, or both; a JWT you hold is sent in headers to the HTTP or SSE server:

Authentication	`.env` keys
Basic (HTTP or RFC)	`SAP_AUTH_TYPE=basic`, `SAP_USERNAME`, `SAP_PASSWORD`
SNC (RFC only, passwordless)	`SAP_AUTH_TYPE=snc`, `SAP_SNC_PARTNERNAME`, optional `SAP_SNC_QOP`, `SAP_SNC_LIB`, `SAP_SNC_MYNAME` — no user, no password
JWT, browser login	`SAP_AUTH_TYPE=jwt`, `SAP_GRANT_TYPE=authorization_code`, a service key (ABAP or XSUAA) or `SAP_UAA_*`
JWT you hold	the `x-sap-jwt-token` header of `mcp-abap-adt-http` / `mcp-abap-adt-sse` (stdio serves none)

A jwt .env must state SAP_GRANT_TYPE. The mcp-auth command that writes such a .env comes from @mcp-abap-adt/auth-broker-cli. The browser login listens on port 61001 unless --browser-auth-port says otherwise.

A created object always carries its responsible person and, where known, its master system. The servers name them once per destination — its credentials and its ABAP system — when its connection is created, by the rules of @mcp-abap-adt/responsible-rules: the system's systeminformation answer (its user, its system id) wins, on-premise and on ABAP Cloud alike; a tool argument that names the value (a transport's owner, say) still states it for that call. When the system gives no information, ABAP Cloud is an error (cloud_without_systeminformation for a 404, else system_lookup_failed); on-premise the responsible is SAP_RESPONSIBLE / x-sap-responsible if stated, else the login (SAP_USERNAME, x-sap-login), and the master system SAP_MASTER_SYSTEM / x-sap-master-system when stated; with no user at all the call is refused system_user_unknown, and a stdio start ends with exit 1. A 401 is answered as it came. The library applies no rules unless an embedder passes them. See Authentication & Destinations. Coming from 22.x? See the 23.0 migration note — CreateProgram no longer offers include (create an include with CreateInclude); an embedder registering the ./handlers groups on its own McpServer states systemType (SAP_SYSTEM_TYPE is not read there), and HandlerExporter serves no background run and no debugger. Coming from 21.x? See the 22.0 migration note — the tools, their enums and the object types each argument accepts are the declared system type's (onprem or cloud), inspection needs --system-type too, function / func are the function module, main types stand for their one code, RunATC on cloud offers no program, and ValidateServiceBinding requires package_name. Coming from 19.x? See the 20.0 migration note — RFC on connection 19 and sap-rfc-lite 0.3.2: nothing compiled on install, a prebuilt binding for Linux x64, Windows x64 and macOS ARM64 only; over Streamable HTTP state_handle is an argument of every tool, and a long session keeps one SAP session across calls. Coming from 18.x? See the 19.0 migration note — the server split into a package per transport and tool set, the system type required, the low set gone, the auth chain on 6.0. Coming from 17.x? See the 18.0 migration note — the debugger's embedder surface moved to adt-clients 29, and a debugger start needs at least one breakpoint. From 16.x, the 17.0 note first.

For full details (paths, .env, direct headers), see Authentication & Destinations.

Architecture

The project ships a library and the servers — and a compact variant of each server — because the two usage patterns want different licences. Embedding the tools in a network service should not drag in the obligations of a server that service never runs.

Package	Licence	What it is
`@mcp-abap-adt/lib`	Apache-2.0	The ADT tool handlers and the embeddable MCP server. No transport: the host supplies one.
`@mcp-abap-adt/core`	AGPL-3.0-only	The standalone stdio server, `mcp-abap-adt`: one destination through the auth broker. Depends on the library.
`@mcp-abap-adt/http`	AGPL-3.0-only	The Streamable HTTP server, `mcp-abap-adt-http`: credentials from each request's `x-sap-*` headers.
`@mcp-abap-adt/sse`	AGPL-3.0-only	The HTTP+SSE server, `mcp-abap-adt-sse`: credentials from the `x-sap-*` headers of each SSE connection's `GET`.
`@mcp-abap-adt/compact`	AGPL-3.0-only	The compact server over stdio, `mcp-abap-adt-compact`: one tool per operation, the object type in the arguments. `core`'s launcher and configuration (from `server-runtime`) with the compact tool set.
`@mcp-abap-adt/compact-http`	AGPL-3.0-only	The compact server over Streamable HTTP, `mcp-abap-adt-compact-http`: `http`'s launcher and configuration (from `server-runtime`) with the compact tool set.
`@mcp-abap-adt/compact-sse`	AGPL-3.0-only	The compact server over HTTP+SSE, `mcp-abap-adt-compact-sse`: `sse`'s launcher and configuration (from `server-runtime`) with the compact tool set.
`@mcp-abap-adt/server-runtime`	AGPL-3.0-only	The launch code of every server: the stdio, Streamable HTTP and SSE launchers and servers, and the destination layer. No command of its own: every server package depends on it, so it is installed with each server; you never install it yourself.
`@mcp-abap-adt/background-runs-memory`	Apache-2.0	The in-memory store of background runs (`IBackgroundRuns` of the library): the servers' store, for an embedder that keeps runs in its process. Every server package depends on it.
`@mcp-abap-adt/responsible-rules`	Apache-2.0	The rules that name a call's responsible, user and system from `systeminformation` (`SystemContextRules` of the library), and the system type the binaries require. Every server package passes them; the library applies none, so an embedder opts in.

| @mcp-abap-adt/core-ro, http-ro, sse-ro | AGPL-3.0-only | The read-only se

Only the beginning is shown; read the rest in the repo

MCP Abap Adt Http

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Egovframe Scaffold MCP

README from the maker

mcp-abap-adt: Your Gateway to ABAP Development Tools (ADT)

Table of Contents

Getting Started

stdio (destination)

HTTP (streamable HTTP)

Terminology

Authorization & Destinations

Architecture