sri-adt-mcp
Gives AI agents a full SAP ABAP Development Tools (ADT) seat against an ABAP system (S/4HANA or ABAP Platform ≥7.5x) reached through an SAP BTP destination. Provides 60+ tools to search objects, read/write/activate source, create programs, classes, CDS, BDEF, tables and packages, run syntax checks, ATC, unit tests and coverage, manage transports, execute runtime analysis (class runs, SQL, dumps, traces), drive the ABAP debugger, and call any /sap/bc/adt endpoint via a generic request tool, with role-gated read/write access, package allowlists and optional per-developer identity propagation.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
sri-adt-mcp
Give your AI coding agent a full SAP ABAP developer seat — search, read, edit, activate, test, transport and debug ABAP over the Model Context Protocol.
sri-adt-mcp is an MCP server that gives AI coding agents (Claude Code, Cursor, Codex, VS Code Copilot, or any MCP client) the capabilities of SAP ABAP Development Tools (ADT). Agents can search, read, create, edit, activate, check, test, transport and debug ABAP objects, the same as a developer in Eclipse.
It runs on SAP BTP Cloud Foundry and reaches the ABAP system through a BTP destination — so no backend credentials ever touch the developer's machine.
Why sri-adt-mcp
🧠 Any MCP client, one URL — works with Claude Code, Cursor, Codex, VS Code Copilot, or anything that speaks MCP.
🔐 Zero credentials on the dev machine — browser OAuth login to BTP; backend credentials stay in the destination and never leave BTP.
🧰 60+ tools spanning the whole ADT surface — navigate, edit, activate, syntax-check, ATC, unit tests, transports, runtime, debugger, abapGit.
🏢 Enterprise-ready controls — role-gated read vs. write, package allowlists, global read-only mode, and multiple destinations from one deployment.
🚪 No dead ends —
adt_requestreaches any/sap/bc/adtendpoint your release supports, even without a dedicated tool.🪪 Per-developer identity, optional — flip the destination to PrincipalPropagation and every call runs as the real developer, no code change.
If this saves you from hand-wiring ADT calls, please ⭐ star the repo — it genuinely helps others find it.
Related MCP server: abap-adt-mcp
Architecture
flowchart LR
A["AI Agent<br/>Claude Code · Cursor · Codex · VS Code"]
subgraph BTP["SAP BTP — Cloud Foundry"]
M["sri-adt-mcp"]
X["XSUAA<br/>(OAuth / roles)"]
D["BTP Destination"]
end
S[("ABAP System<br/>/sap/bc/adt/*")]
A -- "MCP over HTTP" --> M
A -. "OAuth2 login" .-> X
M -- "validate JWT + scopes" --> X
M -- "SAP Cloud SDK" --> D
D -- "Cloud Connector / Internet" --> SNo credentials on the developer's machine. In the agent you add a URL and sign in with your BTP account in the browser. The agent handles and refreshes tokens.
Backend credentials live in the destination. They never leave BTP.
Access is controlled by BTP role collections. Users without write rights only see read-only tools.
How identity works
Access to the MCP server: every request needs an XSUAA token for a signed-in user. Technical tokens (
client_credentials) are rejected.Access to the ABAP system: the destination decides which user ABAP sees.
With
BasicAuthentication, all calls run as the user configured in the destination. That user owns locks, transports and inactive objects.The signed-in user's JWT is always passed to the destination. So if you switch the destination to
PrincipalPropagation(on-premise, via Cloud Connector) or an OAuth2 user-propagating type, calls run as each developer's own ABAP user, with no code change.
Prerequisites
A BTP subaccount with Cloud Foundry, and entitlements for
xsuaa(application),destination(lite) andconnectivity(lite).An ABAP system (S/4HANA, or ABAP Platform ≥ 7.5x) with the SICF service
/sap/bc/adtactive.For on-premise systems: SAP Cloud Connector, with a system mapping that allows the path
/sap/bc/adt(with sub-paths).The ABAP user needs the usual developer authorizations: S_DEVELOP, S_ADT_RES, S_TCODE (SE80), and S_TRANSPRT/S_CTS_ADMI for transports.
MTA Build Tool (
npm i -g mbt) and the CF CLI with the MultiApps plugin.
1. Create the destination
In the BTP cockpit, go to Connectivity → Destinations → New Destination.
Property | Value |
Name |
|
Type | HTTP |
URL |
|
Proxy Type |
|
Authentication |
|
Additional property | e.g. |
2. Deploy
git clone <this repo> && cd sri-adt-mcp
# Optional: edit mta.yaml properties (SRI_ADT_DESTINATION, SRI_ADT_READONLY, SRI_ADT_ALLOWED_PACKAGES)
cf login -a https://api.cf.<region>.hana.ondemand.com
npm run deploy # mbt build && cf deploy
cf app sri-adt-mcp # note the route
curl https://<route>/healthThe MTA creates:
the app;
sri-adt-mcp-xsuaa, from xs-security.json;sri-adt-mcp-destination;sri-adt-mcp-connectivity.
3. Assign roles
In the BTP cockpit, go to Security → Users and assign:
SRI_ADT_Developerfor all tools;SRI_ADT_Viewerfor read-only tools.
4. Connect your agent
Only the URL is needed. On first use the agent opens a browser to sign in with BTP.
Claude Code (.mcp.json in your project, or claude mcp add --transport http sri-adt https://<route>/mcp). Then run /mcp → sri-adt → Authenticate.
{ "mcpServers": { "sri-adt": { "type": "http", "url": "https://<route>/mcp" } } }VS Code (.vscode/mcp.json)
{ "servers": { "sri-adt": { "type": "http", "url": "https://<route>/mcp" } } }Cursor (~/.cursor/mcp.json)
{ "mcpServers": { "sri-adt": { "url": "https://<route>/mcp" } } }Codex (~/.codex/config.toml). Then run codex mcp login sri-adt.
[mcp_servers.sri-adt]
url = "https://<route>/mcp"How the OAuth login works
sequenceDiagram
participant Agent
participant MCP as sri-adt-mcp
participant XSUAA
Agent->>MCP: discover /.well-known/oauth-*
Agent->>MCP: POST /oauth/register
MCP-->>Agent: fixed public client_id
Agent->>MCP: GET /oauth/authorize
MCP->>XSUAA: redirect to login (browser)
XSUAA-->>Agent: authorization code
Agent->>MCP: POST /oauth/token (code)
MCP->>XSUAA: exchange + inject client secret
XSUAA-->>MCP: access token
MCP-->>Agent: access tokenXSUAA doesn't support dynamic client registration, which MCP clients expect. So the app acts as a small authorization-server front end:
It serves
/.well-known/oauth-protected-resourceand/.well-known/oauth-authorization-server./oauth/registerreturns a fixed public client id./oauth/authorizeredirects to the XSUAA login page./oauth/tokenpasses token requests to XSUAA, adding the XSUAA client secret on the server side.
The agents' local callback URLs are allowed through redirect-uris in xs-security.json. If your client uses a different callback, add it there and run cf update-service sri-adt-mcp-xsuaa -c xs-security.json.
Calling from your own app (custom agents)
A custom agent running on BTP (e.g. a CAP app with a logged-in user) can call the server on behalf of its user by exchanging the user's token — the user's identity, role collections and per-user routing all carry over. Technical client_credentials tokens are still refused.
Create a service key on
sri-adt-mcp-xsuaa(cf create-service-key sri-adt-mcp-xsuaa agent-key) to get itsclientid,clientsecretandurl.In the calling app's subaccount, create a destination:
Property
Value
URL
https://<route>/mcpAuthentication
OAuth2JWTBearerClient ID / Secret
from the service key
Token Service URL
<url>/oauth/tokenCall the MCP endpoint through that destination with the user's JWT (e.g.
executeHttpRequest({ destinationName, jwt: userJwt }, …)in CAP / Cloud SDK). The destination service performs thejwt-bearerexchange.
The calling user still needs the SRI_ADT_Developer or SRI_ADT_Viewer role collection.
Configuration
Set these as properties in mta.yaml, or with cf set-env.
Variable | Purpose |
| Required. Default destination name. |
| Further destinations that callers may select with a tool's |
| Per-developer routing: map each signed-in user to their own destination. JSON ( |
| Derive a per-user destination by convention, e.g. |
|
|
| Enables property-based routing: the destination additional-property whose value is matched (case-insensitive) against the signed-in user, e.g. |
| With property-based routing, only consider destinations whose name starts with this prefix (e.g. |
| System alias used when a caller passes no |
|
|
| Packages that create, write and delete may touch, e.g. |
| Timeout per backend request (default 120000). |
| Maximum characters returned per tool call (default 200000). |
| External base URL, if the app sits behind a custom domain or proxy. By default it is taken from the request headers. |
Team access / per-developer identity
By default, with a BasicAuthentication destination, every signed-in user acts as the one ABAP user configured in that destination. For a single person that's fine; for a team it means shared locks, one transport owner, and no per-developer attribution.
Two ways to give each developer their own ABAP identity:
Principal Propagation (no stored passwords) — switch the destination to
PrincipalPropagation(on-premise via Cloud Connector) or an OAuth2 user-propagating type. The server already forwards each user's JWT, so no code or config change is needed. Best when your Cloud Connector / trust is set up for it.Per-developer destinations (no Cloud Connector work) — give each developer their own
BasicAuthenticationdestination holding their ABAP user, and let the server route each signed-in user to theirs. One app, one URL for the whole team; the server reads the user from their XSUAA token and picks the matching destination.# one destination per developer in the subaccount: adt_dest_alice, adt_dest_bob, ... SRI_ADT_USER_DESTINATION_TEMPLATE=adt_dest_{user} # or an explicit map when the ABAP user differs from the BTP logon: SRI_ADT_USER_DESTINATIONS={"alice@corp.com":"adt_dest_alice","bob@corp.com":"adt_dest_bob"} SRI_ADT_USER_DESTINATION_REQUIRED=trueThe explicit map wins; the template is the fallback; if neither matches, the user falls back to
SRI_ADT_DESTINATION(or is refused whenSRI_ADT_USER_DESTINATION_REQUIRED=true). Mapped destinations are allowed automatically — you don't need to repeat them inSRI_ADT_DESTINATIONS. The trade-off vs. principal propagation is that each developer's ABAP password is stored in their destination and must be maintained when it rotates.Property-based routing (no naming convention, no redeploy to onboard). Instead of encoding the user in the destination name, tag each destination with a custom additional property and let the server discover it:
SRI_ADT_USER_PROPERTY=mcpuserThen create a destination named anything, with additional property
mcpuser = alice@corp.comand Alice's ABAP credentials. On each request the server lists the subaccount's destinations (cached ~5 min, refreshed on a miss), finds the one whose property equals the signed-in user, and routes to it. Adding a developer is just creating a tagged destination — no app config change, no redeploy. A user with no matching destination is refused with a message telling them exactly which property to set. This needs the destination-service binding (already bound by the MTA); the property stores an identity (an email), not a secret.A simple team convention is to name every per-developer destination under a shared prefix (e.g.
adt_mcp_dest_alice,adt_mcp_dest_bob) and scope matching to it, so the server never considers unrelated destinations:SRI_ADT_USER_PROPERTY=mcpuser SRI_ADT_USER_DESTINATION_PREFIX=adt_mcp_destMultiple systems per developer (two-level routing). A developer often needs more than one backend (e.g. S/4 and ECC). Give them one destination per system, named
<prefix>_<system>_<who>, each taggedmcpuser:adt_mcp_dest_s4_sj mcpuser=sri.jayant@corp.com → S/4 adt_mcp_dest_ecc_sj mcpuser=sri.jayant@corp.com → ECC adt_mcp_dest_s4_rg mcpuser=rahul@corp.com → S/4SRI_ADT_USER_PROPERTY=mcpuser SRI_ADT_USER_DESTINATION_PREFIX=adt_mcp_dest SRI_ADT_DEFAULT_SYSTEM=s4The server resolves in two levels: (1) who — all destinations tagged
mcpuser = <you>; (2) which system — the token after the prefix in the name (s4,ecc, …), or an explicitmcpsystemtag if you set one (the tag wins). A caller selects the system by passing it as the tool'sdestinationargument (e.g.destination: "ecc"); with no argument theSRI_ADT_DEFAULT_SYSTEM(elses4, else the only one) is used. The suffix (_sj,_rg) is for humans — the server reads the tag, not the suffix.
Either way, every teammate still needs the SRI_ADT_Developer (or SRI_ADT_Viewer) role collection to connect.
Tools
Most tools that point at an object take either type + name or uri. Types: PROG, INCL, CLAS, INTF, FUGR, FUNC (+group), FUGR_INCL, DDLS, DCLS, DDLX, BDEF, SRVD, SRVB, TABL, STRU, TTYP, DTEL, DOMA, MSAG, DEVC, XSLT, ENHO, ENHS, DDLA, SAJC.
Area | Tools |
Universal |
|
Navigate |
|
Source / edit |
|
Create |
|
Checks |
|
Quality |
|
Transports |
|
Runtime |
|
Debugger |
|
Services / DDIC / enhancements |
|
abapGit |
|
For any ADT feature without a dedicated tool, use adt_request. adt_discovery shows what your backend release supports.
Things to know
Sessions. Each signed-in user gets their own ADT session (CSRF token and cookies), so lock → edit → unlock works across tool calls. Sessions expire after 30 minutes idle.
Debugger. It works best-effort only, because it relies on long polling through the destination. Keep
debugger_listentimeouts short.Running reports. ADT has no REST endpoint for running classic reports. Use
run_classwith IF_OO_ADT_CLASSRUN, or AUnit.Safety. Use
SRI_ADT_ALLOWED_PACKAGESandSRI_ADT_READONLYfor shared or production-like systems. Remember that withBasicAuthenticationevery user acts as the destination's user.
Development
npm install
npm run build
npm testLicense
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Acumatica MCP server for ChatGPT, Claude and any AI agent: create AP bill, create AR invoice, release invoice, list open invoices and approve payment in your own Acumatica account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Acumatica yourself; Cotlet does not store your password and you need no Acumatica API key. About the official Acumatica API: Yes. Acumatica has a full contract-based REST API with OAuth 2.0 (checked 14 Oct 2026). Setup and FAQ: https://cotlet.dev/integrations/acumatica-api-mcp-server
JobDiva MCP server for ChatGPT, Claude and any AI agent: search candidates, find candidate, search jobs, add candidate note, add candidates to hotlist, create submittal and create candidate in your own JobDiva account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to JobDiva yourself; Cotlet does not store your password and you need no JobDiva API key. About the official JobDiva API: JobDiva has a REST API with public Swagger docs, 759 paths across two versions, but it only works with a client ID that JobDiva provides, and JobDiva has no official MCP server (checked 23 Oct 2026). The API has no webhooks, so changes have to be polled, and updates and deletes are POST calls. Setup and FAQ: https://cotlet.dev/integrations/jobdiva-api-mcp-server
Anaplan MCP server for ChatGPT, Claude and any AI agent: list models, list actions, upload import file, run import, run process, run export, get model history and add user in your own Anaplan account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Anaplan yourself; Cotlet does not store your password and you need no Anaplan API key. About the official Anaplan API: Yes. Anaplan has an official REST API, the Integration API v2.0, and an official MCP server, the Anaplan AI Gateway, but Anaplan's help says the AI Gateway gives external AI systems read-only access (checked 5 Nov 2026). Setup and FAQ: https://cotlet.dev/integrations/anaplan-api-mcp-server
SnelStart MCP server for ChatGPT, Claude and any AI agent: create sales invoice, add relation, book entry, list open items and upload document in your own SnelStart account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to SnelStart yourself; Cotlet does not store your password and you need no SnelStart API key. About the official SnelStart API: Yes, but it is gated (checked 14 Oct 2026). SnelStart has a B2B API for software partners: you request a connection, get a development key and portal access, and a production integration for several users needs certification, OAuth, a webhook URL and at least five named customers. Setup and FAQ: https://cotlet.dev/integrations/snelstart-api-mcp-server
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to access SAP ADT APIs for reading, writing, debugging, deploying, and testing ABAP code through natural language or DSL automation.530MIT
- AlicenseAqualityDmaintenanceEnables AI agents to read, write, activate, and transport ABAP code in SAP systems via ABAP ADT REST API, without needing SAP GUI.24MIT
- AlicenseBqualityAmaintenanceEnables LLMs to develop, debug, test, and manage SAP ABAP objects on a live system through the ABAP Development Tools (ADT) protocol.2911MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to SAP systems through the ABAP Development Tools API, exposing 85 tools that cover the full ABAP development lifecycle — reading and writing source, creating and activating objects, managing transports, running syntax/ATC checks and unit tests, querying tables, refactoring, remote debugging, tracing, and executing code — all without SAP GUI. Supports single- or multi-system landscapes with credentials supplied by the MCP client at launch.MIT