AgentStack
MCP verified MIT Self-run

Abap Mcp

mcp-joaodelapace-abap-mcp · by joaodelapace

Read & write ABAP in SAP from Claude, Cursor or any MCP client, over the standard ADT API. Read-only by default.

No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add mcp-joaodelapace-abap-mcp

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Abap Mcp? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

abap-mcp — Read & write ABAP from Claude, Cursor & any MCP client

An MCP (Model Context Protocol) server that connects AI assistants (Claude Desktop, Claude Code, Cursor, …) directly to a SAP system over the standard ADT (ABAP Development Tools) HTTP API. Your AI can read, search, syntax-check — and, when you enable it, write, activate, and refactor real ABAP — without leaving the chat.

No SDK bloat. Pure Python standard library — starts in seconds even behind aggressive corporate antivirus, and runs on any Python 3.x.


Why this exists

ABAP developers are the last ones to get good AI tooling. Copilots can write ABAP text, but they can't see your system or touch your code. This bridges that gap using the same ADT REST API Eclipse uses — so it works against any modern SAP NetWeaver / S/4HANA system you can already reach.

It's the missing link between an LLM and a live SAP repository.


Safe by default

Out of the box the server is read-only. Write tools stay dormant until you explicitly opt in with SAP_ALLOW_WRITE=1 in your .env — and even then, every write additionally requires an explicit confirm flag and a transport request, with a syntax check before each save. So you can hand it to your AI and let it explore your system with zero risk, then flip the switch when you're ready to let it build.


What it can do

Read (always on):

  • abap_ping — connectivity / auth check
  • abap_search — find objects across the repository
  • abap_read_class / abap_read_program / abap_read_include / abap_read_function / abap_read_uri
  • abap_sql — read-only SELECT against tables
  • abap_syntax_check — validate source without saving
  • smartform_info / sapscript_info — inspect forms

Write & generate (enable with SAP_ALLOW_WRITE=1):

| Tool | What it does | |------|--------------| | abap_update_source / abap_patch_source | Save full source, or do a surgical find-and-replace edit on a large include without retyping it | | abap_create_object | Create new classes / programs / interfaces / includes / function groups | | abap_activate | Activate objects (handles function-group includes correctly) | | abap_classrun | Run an IF_OO_ADT_CLASSRUN class — the Eclipse "F9" — and get console output | | abap_create_enhancement | Inject an implicit enhancement (source hook) without modifying the standard object | | abap_cust_maintain | Maintain customizing tables (SM30-style), transport-aware, dry-run by default | | abap_create_dynpro | Create dynpros / screens headlessly (no GUI screen painter) | | abap_note_status / abap_note_download / abap_note_implement | Inspect, download and (dry-run or apply) SAP Notes via the Note Assistant API | | abap_create_transport | Create transport requests from the AI | | Modification-Assistant bypass | Auto-detects the ADT 405 ExceptionResourceIsModified lock failure on Z-copies of standard objects and transparently falls back to RPY_PROGRAM_UPDATE so the write still succeeds |

Note Assistant apply is dry-run by default and refuses to run against a production system id.


Setup (60 seconds)

git clone 
cd abap-mcp
cp .env.example .env      # fill in host, client, user, password

.env:

SAP_BASE_URL=http://your-sap-host.example.com:8000
SAP_CLIENT=100
SAP_USER=YOUR_SAP_USER
SAP_PASSWD=YOUR_PASSWORD
SAP_LANG=EN
SAP_ALLOW_WRITE=0          # set to 1 to enable the write/generate tools

Register with Claude Code / Desktop:

claude mcp add abap-mcp --scope user -- python /path/to/server.py

Or in any MCP client, point it at python server.py over stdio.

Ask your assistant: "ping the SAP system and list all Z-classes whose name starts with ZCL_."


Requirements

  • Python 3.8+ (no pip dependencies)
  • Network access to a SAP system's ADT endpoint (/sap/bc/adt/*)
  • A SAP user with developer authorizations (and a transport for writes)

Disclaimer

Use against systems you are authorized to develop on. Writes go through standard SAP authorization, transport and syntax checks, but you are responsible for what you commit. Not affiliated with or endorsed by SAP SE.

License

MIT. Free to use, modify and share.


Built by João Pace — SAP × AI. If this saves you time, a ⭐ on the repo helps others find it. Found a rough edge or want a connector for your system? Open an issue or reach out on LinkedIn.

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.