MCP serverMCP serverExposes tools to a coding agent over MCP.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
pyrfc-mcp
An MCP server for calling an SAP system's RFC-enabled function modules from an agent, built so that discovering a function does not authorise calling it: a read or a write is denied unless the function name matches an allowlist the server is configured with.
Six tools sit over PyRFCPyRFCSAP's Python bindings over the SAP NetWeaver RFC SDK. For the things here it is what a Python program calls ABAP function modules through, and it carries the SDK's own prerequisite with it.: search_rfc_functions finds a function by pattern or group, get_rfc_function_interface returns its parameters, call_rfc_function executes it in read or write mode, commit_rfc_transaction and rollback_rfc_transaction close what a write opens, and read_abap_source fetches a program's source over ADT where that is reachable and over RFC otherwise, with no transport choice handed to the caller. The policy layer is the part that is not a thin wrapper: a read or a write needs the function name to match an explicit allowlist, mutating names are denied by rule, the generic table readers are guarded at table level, and a result is rejected rather than truncated when its nested table rows or serialised bytes exceed the configured limit, with every policy decision and call outcome written to an audit log. A write returns an opaque transaction_id to reuse for related writes and then hand to commit or rollback, which pins the whole SAP LUW to one RFC connection, and an abandoned transaction expires and rolls back on its own. It runs as a stdio process from a local install, with connection and policy settings in a .env file and a doctor command that checks both those and the native dependencies without contacting SAP unless --connect is passed. A demo backend answers with synthetic RFC metadata and business records through the same discovery, validation, authorisation and limiting layers, so the tools can be exercised before any SAP prerequisite is in place.
Facts
Last pushLicenceMIT
Where it sits
Lives in
Provides
Agent access to your systemsABAPAgent access to your systemsGiving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. [Serving your application over MCP](capability:mcp-servers) exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to [agent access to your code](capability:agent-code-access).Agent access to your codeABAPAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Tool governanceABAPTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.
Optional
SAP NetWeaver RFC SDKSAP NetWeaver RFC SDKthe native library PyRFC binds to, and the prerequisite the README sends a reader to its setup document for before any live callPyRFCPyRFCthe RFC client every live call goes through, pinned to the 3.3.1 release the README calls archived and yanked
Who is behind it
Yassin BahriYassin BahriMaintains this
In the atlas: maintains 2, contributes to 2@yassinbahrimaintainer
In the atlas: maintains 2, contributes to 2@yassinbahrimaintainer
Before choosing this
Conditions
PracticalFunctional boundary
Real SAP calls need the proprietary SAP NetWeaver RFC SDKSAP NetWeaver RFC SDKSAP's native library for calling ABAP functionality and for being called from ABAP. Downloaded from SAP under its own terms rather than from a package registry, so anything built on it carries that prerequisite per platform. and the pyrfc==3.3.1 release the README calls archived and yanked, on Python 3.11, so without those only the demo backend answers. Not over HTTP as it stands: credentials are read from the environment for stdio, and the README says not to expose the server over HTTP without implementing the MCP authorization specification and deployment-level rate limiting. Multi-tenant auth and RBAC beyond the one server-wide policy, rate limiting, metrics and tracing, and deployment packaging are listed as not built. The result limits protect the client and not the system, since the README states they cannot reduce work already performed inside SAP, and the MCP tool annotations that describe read and write risk are advisory metadata rather than an authorisation boundary, so the service account's S_RFC and table authorisations are still what decides.
PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Agent access to your systemsAn MCP server uses SAP APIs to supply tools, resources or data to an agent.
- § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
- § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
MCP does not replace the API's documented-use boundary. Check that every endpoint is published for the intended use and whether the policy's AI-call or extraction provisions apply to the design.
SAP API Policy 4.2026a →PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Agent access to your codeAn MCP server calls ADT or another SAP API of a running system for an agent.
- § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
- § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
An agent that plans and executes ADT calls is the case section 2.2.2 names. Check that the endpoints are published for the intended use, and that the design runs within a pathway SAP identifies for it.
SAP API Policy 4.2026a →What it declares
Every artifact
- Type
- MCP server
- Origin
- Independently maintained
As an MCP server
- Runs as
- local process
- Transport
- stdio
- Read-only
- nostates it is not
- Guardrails
6 quoted from README show all
It is deny-by-default: discovering an RFC does not authorize calling it.
Function allowlists, mutating-name deny rules, sensitive-table guards, result limits, and connection-affine transactions remain enforced at the server.
Reads and writes are denied unless their function names match explicit allowlists.
MCP tool annotations describe read/write risk for capable clients, but are advisory metadata—not an authorization boundary.
Do not expose the server over HTTP without implementing the MCP authorization specification and deployment-level rate limiting.
they cannot reduce work already performed inside SAP
For agent access to ABAP code
- Read
- sourcesearchwhere-usedDDICCDStable data
- Change
- writecreateactivatetransportsgit
- Check
- syntaxATCABAP Unit
- Run
- run codedumps
Connections
Group by
NodeRelationBasis
Functional
Agent access to your codeAgent access to your codeLetting a coding agent read and act on your project or systemSAP and community, unassessed
provides
stated
provides Agent access to your code
Reads ABAP program source out of the system for the agent through one tool, over ADT where that is reachable and over RFC otherwise.
“automatic ABAP source reading (ADT when reachable, transparent RFC fallback otherwise”“`read_abap_source(object_type, object_name, function_group=None)`”
Letting a coding agent read and act on your project or system
Agent access to your systemsAgent access to your systemsGiving an AI agent access to the systems you run over MCPSAP and community, narrow by design
provides
stated
provides Agent access to your systems
Puts an SAP system's RFC-enabled function modules in front of an agent as tools, with finding a function and reading its interface kept apart from calling it, and a policy layer deciding which names may be called at all.
“MCP server exposing SAP RFC-enabled function modules (BAPIs/RFCs) to AI agents through a discovery-first interface”“A policy-controlled MCP server for discovering and calling SAP RFC functions”
Giving an AI agent access to the systems you run over MCP
Tool governanceTool governanceControlling what an agent may call, with an audit trailSAP and community, unassessed
provides
stated
provides Tool governance
Decides what an agent may call before the call happens: read and write allowlists of function names, a deny rule for mutating names, a table-level guard on the generic table readers, fail-closed limits on what a result may return, and an audit log of every policy decision and call outcome.
“including a deny-by-default read/write policy, a table-level guard against the generic-table-reader injection surface (`RFC_READ_TABLE` et al.), fail-closed RFC response limits, and audit logging of every policy decision and call outcome”“It is deny-by-default: discovering an RFC does not authorize calling it.”
Controlling what an agent may call, with an audit trail
Technical
connects to
stated
connects to ABAP platform
Calls remote-enabled function modules in the system and reads program source from it; a write holds the whole SAP unit of work on one RFC connection until it is committed or rolled back.
Remote Function Call (RFC)
“MCP server exposing SAP RFC-enabled function modules (BAPIs/RFCs) to AI agents through a discovery-first interface”“This pins the entire SAP LUW to one RFC connection”
SAP's application server and development platform for ABAP. For the things here it is the system a developer's editor or an agent's tool reaches over ADT, and a program calls over RFC; where it runs is the deployment's, as for SAP BW/4HANA.
optionally needs
stated
optionally needs PyRFC
a real SAP system is called; demo mode replaces the SAP transport with a synthetic backend
the RFC client every live call goes through, pinned to the 3.3.1 release the README calls archived and yanked
“the archived/yanked `pyrfc==3.3.1` connector”“No SAP account, PyRFC installation, or SAP NW RFC SDK is needed for demo mode.”
SAP's Python bindings over the SAP NetWeaver RFC SDK. For the things here it is what a Python program calls ABAP function modules through, and it carries the SDK's own prerequisite with it.
optionally needs
stated
optionally needs SAP NetWeaver RFC SDK
a real SAP system is called; demo mode replaces the SAP transport with a synthetic backend
the native library PyRFC binds to, and the prerequisite the README sends a reader to its setup document for before any live call
“Real SAP connectivity additionally requires the proprietary SAP NW RFC SDK”“No SAP account, PyRFC installation, or SAP NW RFC SDK is needed for demo mode.”
SAP's native library for calling ABAP functionality and for being called from ABAP. Downloaded from SAP under its own terms rather than from a package registry, so anything built on it carries that prerequisite per platform.
Download
Install
python -m pip install pyrfc-mcp rfc-mcp doctor --demo --connect rfc-mcp --demo
Copied from yassinbahri/pyrfc-mcp — README, Try it without SAP, read . Not run by the atlas.
Architecture
Download
SAP NetWeaver RFC SDKSAP's native library for calling ABAP functionality and for being called from ABAP. Downloaded from SAP under its own terms rather than from a package registry, so anything built on it carries that prerequisite per platform.
PyRFCSAP's Python bindings over the SAP NetWeaver RFC SDK. For the things here it is what a Python program calls ABAP function modules through, and it carries the SDK's own prerequisite with it.
ABAP platformSAP's application server and development platform for ABAP. For the things here it is the system a developer's editor or an agent's tool reaches over ADT, and a program calls over RFC; where it runs is the deployment's, as for SAP BW/4HANA.
pyrfc-mcpAn MCP server for calling an SAP system's RFC-enabled function modules from an agent, built so that discovering a function does not authorise calling it: a read or a write is denied unless the function name matches an allowlist the server is configured with.independent, abap
Your MCP client → pyrfc-mcpStated in the document, datayassinbahri/pyrfc-mcp — README, Security posture, checked 2026-09-29: “Stdio credentials come from the environment and are never placed in MCP tool arguments.”
pyrfc-mcp → SAP NetWeaver RFC SDKDocumented only, under a conditionthe native library PyRFC binds to, and the prerequisite the README sends a reader to its setup document for before any live callIf a real SAP system is called; demo mode replaces the SAP transport with a synthetic backend
pyrfc-mcp → PyRFCDocumented only, under a conditionthe RFC client every live call goes through, pinned to the 3.3.1 release the README calls archived and yankedIf a real SAP system is called; demo mode replaces the SAP transport with a synthetic backend
pyrfc-mcp → ABAP platformDocumented only, data, RFC, outbound, sync, lands on Remote Function Call (RFC)Calls remote-enabled function modules in the system and reads program source from it; a write holds the whole SAP unit of work on one RFC connection until it is committed or rolled back.
SAPnot SAP's, or the project's ownstated in the documentdocumented onlyunder a condition
README
quoted from yassinbahri/pyrfc-mcp under MIT, readyassinbahri/pyrfc-mcp/README.mdthe maintainer’s wordsOn GitHub
pyrfc-mcp
MCP server exposing SAP RFC-enabled function modules (BAPIs/RFCs) to AI
agents through a discovery-first interface, built on SAP's pyrfc
connector — plus automatic ABAP source reading (ADT when reachable,
transparent RFC fallback otherwise, see
docs/adt_rfc_integration_plan.md).
It is deny-by-default: discovering an RFC does not authorize calling it. Function allowlists, mutating-name deny rules, sensitive-table guards, result limits, and connection-affine transactions remain enforced at the server.
Try it without SAP
The supported demo backend uses deterministic synthetic RFC metadata and business records. It exercises the real discovery, validation, authorization, result-limiting, and MCP tool layers; only the final SAP transport is replaced.
python -m pip install pyrfc-mcp
rfc-mcp doctor --demo --connect
rfc-mcp --demoNo SAP account, PyRFC installation, or SAP NW RFC SDK is needed for demo mode. Configure an MCP client with the included .mcp.json.example to explore it immediately.
Setup
See docs/setup.md for the SAP NW RFC SDK + Python 3.11 prerequisites (required before real SAP calls work) and docs/architecture.md for the layer overview, including the read/write policy model, the generic-table-reader guard, and audit logging.
For a real system, install the proprietary SDK prerequisites, then:
uv sync --extra dev
copy .env.example .env # fill in connection + policy settings
uv run rfc-mcp doctor # validates config and native dependencies, no SAP call
uv run rfc-mcp doctor --connect # explicitly performs a live SAP ping
uv run pytest # unit tests, synthetic backend, no SAP needed
uv run mcp dev src/rfc_mcp/mcp/server.pyReal SAP connectivity additionally requires the proprietary SAP NW RFC SDK
and the archived/yanked pyrfc==3.3.1 connector. Read the support warning
and installation steps in docs/setup.md before running
uv sync --extra sap or the smoke test.
doctor intentionally redacts connection and credential values. It does not
contact SAP unless --connect is present, and it also supports --json for
automation.
Tools
search_rfc_functions(pattern, group=None, limit=50)get_rfc_function_interface(function_name)call_rfc_function(function_name, parameters, mode="read"|"write", transaction_id=None)commit_rfc_transaction(transaction_id, wait=False)rollback_rfc_transaction(transaction_id)read_abap_source(object_type, object_name, function_group=None)— one tool, no transport choice exposed to the caller; see docs/architecture.md.
ABAP knowledge skill
.claude/skills/sap-abap/ vendors the third-party
sap-abap Claude Skill so an agent using this server also has accurate
ABAP language knowledge on hand. It's licensed separately (GPL-3.0, its own
LICENSE/NOTICE.md) from the rest of this project — see below.
Scope
Foundation, connection layer, discovery, execution, and MCP integration are
built and tested, including a deny-by-default read/write policy, a table-level guard
against the generic-table-reader injection surface (RFC_READ_TABLE et
al.), fail-closed RFC response limits, and audit logging of every policy
decision and call outcome. Not
built: multi-tenant auth/RBAC beyond the single server-wide policy, rate
limiting, metrics/tracing, and deployment packaging — see
docs/architecture.md's "Out of scope" section for
what’s deliberately deferred and why.
Write calls return an opaque transaction_id. Reuse it for related writes,
then pass it to commit or rollback. This pins the entire SAP LUW to one RFC
connection; abandoned transactions expire and roll back automatically.
Security posture
- Reads and writes are denied unless their function names match explicit
allowlists. The example configuration only permits discovery, source
reading, and the harmless
STFC_CONNECTIONsmoke test. - MCP tool annotations describe read/write risk for capable clients, but are
advisory metadata—not an authorization boundary. Server policy and the SAP
service account's
S_RFC/table authorizations remain mandatory. - Stdio credentials come from the environment and are never placed in MCP tool arguments. Do not expose the server over HTTP without implementing the MCP authorization specification and deployment-level rate limiting.
- RFC results are rejected rather than silently truncated when their cumulative
nested table rows or serialized UTF-8 JSON size exceed
RFC_MCP_RESULT_MAX_TABLE_ROWSorRFC_MCP_RESULT_MAX_SERIALIZED_BYTES. These limits protect MCP consumers; they cannot reduce work already performed inside SAP. - See SECURITY.md for reporting and deployment guidance.
License
MIT (see LICENSE), with one carved-out exception:
.claude/skills/sap-abap/ is vendored third-party
content under GPL-3.0 — see its own LICENSE and NOTICE.md. Including
that directory does not place the rest of the project under GPL-3.0.
History
Latest
Features 4, Changed 3, Fixes 1
Notes
Added
- A supported synthetic demo backend that exercises the real discovery, policy, validation, result-limit, and MCP layers without SAP or PyRFC.
- The
rfc-mcp --demofirst-run path with safe demo allowlist defaults. - The
rfc-mcp doctorpreflight command, optional live connectivity testing, redacted output, and machine-readable JSON reports. - Trusted Publishing workflow for secret-free, release-triggered PyPI uploads.
Changed
- SAP connection settings are loaded only when the SAP backend is selected.
- Connection consumers now depend on a typed connection-manager protocol, allowing production and synthetic transports to share the same runtime.
- Package metadata now includes project links and expanded discovery keywords.
Fixed
- CodeQL initialization and analysis actions now use the same release.
Removed 1, Features 4, Changed 3
Notes
Added
- Connection-affine SAP transactions with opaque IDs, expiry, and shutdown rollback.
- Bounded connection-pool acquisition timeouts.
- MCP read/write risk annotations.
- Locked dependencies, CI, security scanning, contribution guidance, and templates.
Changed
- Read access is deny-by-default and must be explicitly allowlisted.
- PyRFC is an optional, exactly pinned legacy dependency.
- Local MCP configuration is now supplied as a portable example.
Removed
- Generated bytecode, local session files, and runtime logs from the distributable tree.
Others providing
Agent access to your systemsAgent access to your systemsGiving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. Serving your application over MCP exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to agent access to your code.SAP and community, narrow by design
- @abap2ui5/mcp-server@abap2ui5/mcp-serverAn MCP server that puts the abap2UI5 development loop on the machine an agent runs on: check the view the ABAP builds, photograph it, deploy the class into a sandbox, boot the app headless and read the errors.community org, abapMCP server for the abap2UI5 check, deploy and run loop
- abap2UI5 for VS Codeabap2UI5 for VS CodeA VS Code extension for abap2UI5 apps: F9 starts the app class in a preview beside the source, Ctrl+F3 activates the class and reloads it, and the abap2UI5 linter runs in the editor while you type.community org, abapVS Code extension to preview, activate and lint abap2UI5 apps
- abapsmithabapsmithAn MCP server that lets an LLM develop in ABAP on a live system over ADT, with writes off by default and every mutation recorded in a local journal that can undo it.independent, abapABAP MCP server over ADT with a local journal that can undo writes
- btp-sap-odata-to-mcp-serverbtp-sap-odata-to-mcp-serverExposes every OData service on an S/4HANA or ECC system as MCP tools, in three discovery levels so a large catalogue does not have to be loaded at once.independent, btpExposes S/4HANA or ECC OData services as MCP tools
- midasol/sap-mcp-servermidasol/sap-mcp-serverA Python MCP server for SAP Gateway with four read-only tools that authenticate, query, fetch one entity and list services, and one of the few here that publishes its test results.independent, btpPython MCP server for SAP Gateway OData operations
- odata_mcp_goodata_mcp_goA Go binary that bridges any OData v2 or v4 service to MCP — and can collapse the whole service into one tool when the generated tool list is too large to be usable.independent, btpGo binary bridging any OData v2 or v4 service to MCP
- odata_mcpodata_mcpThe Python original: reads an OData v2 service's metadata and generates MCP tools from it, with the SAP-specific conversions the raw protocol leaves to you.independent, btpPython bridge generating MCP tools from OData v2 metadata
- sap-mcp-serversap-mcp-serverReads SAP ECC and S/4HANA for an agent over Gateway OData and RFC, with a Node bridge that speaks the RFC protocol without the proprietary SAP NetWeaver RFC SDK.independent, abapReads SAP ECC and S/4HANA for an agent over Gateway OData and RFC, with a Node bridge that speaks the RFC protocol without the proprietary SAP NetWeaver RFC SDK.
- Skybuffer AI MCP serverSkybuffer AI MCP serverAn ABAP add-on that serves SAP business data, transactions and development context as MCP tools from an ICF node inside SAP ECC and S/4HANA, each call running as the signed-in user under PFCG authorization checks.independent, abapABAP add-on serving business data and transactions as MCP tools
- sap-security-mcpsap-security-mcpAn entirely read-only security analysis surface: nineteen tools, five resources and eight prompts for audits, SOX and segregation-of-duties review, behind OAuth 2.0 with PKCE. The vendor hosts an endpoint, and the README documents running it yourself.independent, abapRead-only security analysis MCP server for SAP audits and SoD review
- KlystronKlystronAn MCP server written in ABAP that runs inside the application server behind an ICF service and exposes typed tools for ABAP development, quality, transports, customizing, roles, Basis operations and integration, with a client-side plugin of SAP skills.independent, abapMCP server in ABAP inside the application server, with agent skills
Agent access to ABAP codeAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from MCP servers, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed
- @abap2ui5/mcp-server@abap2ui5/mcp-serverAn MCP server that puts the abap2UI5 development loop on the machine an agent runs on: check the view the ABAP builds, photograph it, deploy the class into a sandbox, boot the app headless and read the errors.community org, abapMCP server for the abap2UI5 check, deploy and run loop
- arc-1-bopf-enharc-1-bopf-enhAn extension of four tools for arc-1, with an ABAP service behind it, that lets an agent read and maintain classic BOPF enhancements of SAP standard business objects.independent, abaparc-1 extension for reading and maintaining BOPF enhancements
- HammerHammerA native macOS code editor for ABAP and CDS, with an Object Navigator, Transport Organizer, Data Browser and Gateway Client in the same app as the editor.independent, abapNative macOS code editor for ABAP and CDS
- arc-1-lsparc-1-lspAn edition of ARC-1 that hands every ADT interaction to SAP's own embedded adt-ls language server instead of a hand-rolled HTTP client.independent, abapEdition of ARC-1 that runs ADT calls through adt-ls
- arc-1arc-1An MCP server in front of the ADT REST API that runs locally and on Cloud Foundry with twelve tools that read, search, write, activate, lint and transport ABAP objects.independent, abapMCP server over the ADT REST API for ABAP objects
- arc1-abap-bridgearc1-abap-bridgeA VS Code extension between arc-1 and ABAP Development Tools for VS Code, so GitHub Copilot can open an ABAP object by name, diff the inactive version and ask the system whether an edit would be accepted.independent, abapVS Code bridge between arc-1 and ADT for VS Code
- arc1-adt-abap-mcp-extarc1-adt-abap-mcp-extOne JAR in Eclipse's dropins that turns on SAP's own ADT MCP server and adds read-only repository tools beside it — so an AI client reads your system without leaving Eclipse.independent, abapEclipse add-on enabling the ADT MCP server with read-only tools
- ABAP Accelerator MCP ServerABAP Accelerator MCP ServerAWS's ABAP MCP server for Amazon Q Developer and Kiro, deployable locally, in Docker or centrally on ECS Fargate with OAuth principal propagation; its repository is no longer maintained.partner, abapAWS's ABAP MCP server for Amazon Q Developer and Kiro
- Modernization Agents for SAP on AWSModernization Agents for SAP on AWSAWS's suite of agents for SAP modernisation work: custom ABAP converted for S/4HANA, PI/PO interfaces moved to Integration Suite, BW objects moved to SAP Datasphere, deployed into a customer's own AWS account and reached only after registration.partner, abapAWS agents for ABAP, PI/PO and BW modernisation work
- @mcp-abap-adt/core@mcp-abap-adt/coreA descendant of the Andreschak and fr0ster servers rebuilt on its own architecture, published as an npm scope and a Claude Code plugin, with Korean and Japanese documentation beside the English.independent, abapABAP ADT MCP server published as an npm scope and plugin
- chandrashekhar-mahajan/abap-mcp-serverchandrashekhar-mahajan/abap-mcp-serverFifteen ADT tools behind five pluggable authentication strategies — Kerberos/SPNEGO, OAuth 2.0, X.509, browser SSO and basic — for systems where basic auth is not an option.independent, abapABAP MCP server with ADT tools and five authentication strategies
- dassian-adtdassian-adtA fork of mcp-abap-abap-adt-api hardened for use: 25 tools, input validation, error intelligence, MCP elicitation, session recovery and a test suite.independent, abapFork of mcp-abap-abap-adt-api with 25 tools and session recovery
- erpl-adterpl-adtOne C++ binary that speaks the ADT REST API as a CLI and as an MCP server — no Eclipse, no NetWeaver RFC SDK, no JVM — and reaches BW/4HANA modelling as well as ABAP.independent, abapC++ binary speaking the ADT REST API as a CLI and MCP server
- bw-modeling-mcpbw-modeling-mcpReads, creates and modifies BW/4HANA modelling objects through the same internal APIs Eclipse BWMT and the BW/4HANA Cockpit use — and can run centrally on BTP with each caller reaching BW as themselves.independent, btpMCP server for BW/4HANA modelling objects
- EPOD ADT MCP ServerEPOD ADT MCP ServerAn MCP server for ABAP that runs inside ABAP Development Tools for Eclipse on the ADT session of each connected project, with a standalone mode that runs with no IDE open.independent, abapMCP server for ABAP on the ADT session, in Eclipse or standalone
- ZARC1_EXTENSION_FORMSZARC1_EXTENSION_FORMSAn extension of four tools for arc-1, with an ABAP backend behind it, that reaches the classic form objects ADT has no API for: SAPscript layout sets, Smart Styles and the TADIR record of a Smart Form.independent, abaparc-1 extension for SAPscript and Smart Forms objects
- fgalastri/MCP_ABAPfgalastri/MCP_ABAPValidates an ABAP class before it is deployed by converting the global class to a local one and syntax-checking that — plus CDS DDL and table metadata retrieval.independent, abapValidates an ABAP class before it is deployed by converting the global class to a local one and syntax-checking that — plus CDS DDL and table metadata retrieval.
- fr0ster/mcp-abap-adtfr0ster/mcp-abap-adtFull CRUD across on-premise and ABAP Cloud systems, with five authentication methods and three transports: a library under Apache-2.0 and a standalone server under AGPL-3.0-only.independent, abapABAP MCP server with full CRUD on on-premise and ABAP Cloud
- abapsmithabapsmithAn MCP server that lets an LLM develop in ABAP on a live system over ADT, with writes off by default and every mutation recorded in a local journal that can undo it.independent, abapABAP MCP server over ADT with a local journal that can undo writes
- sap-ai-dev-toolkitsap-ai-dev-toolkitAn MCP proxy that pins an agent's ABAP tools to one SAP system: setup reads the BAS destinations or the local SAP GUI landscape and writes one stdio server per system, leaving the credentials in the destination or in the editor's own login prompts.independent, abapMCP proxy pinning an agent's ABAP tools to one SAP system
- aibap.mcpaibap.mcpA Go server that closes the loop: after create, write and activate it can run the class it just wrote through ADT's classrun and hand the console output back.independent, abapGo MCP server that writes, activates and runs ABAP classes via ADT
- BellaBellaAn Eclipse plugin that puts Claude into ABAP Development Tools: explain, generate, rework and implement from the editor's context menu, completion as ghost text, and a chat whose tools reach the system through the developer's existing ADT logon.independent, abapEclipse plugin bringing Claude into ABAP Development Tools
- Maherd18/sap-mcp-serverMaherd18/sap-mcp-serverAn MCP server for ABAP development over the ADT resources: eight tools, each checked against a JSON policy file before the call reaches the system, with activation and transport release held for a person to approve.independent, abapPolicy-checked MCP server for ABAP development over ADT
- sapdumpmcpsapdumpmcpAn MCP server for SAP dumps: it connects to an ABAP system over the ADT resources and lets an MCP client ask a dump for its description and call stack.independent, abapMCP server reading ABAP short dumps over ADT
- ABAP remote filesystemABAP remote filesystemA Visual Studio Code extension that opens an ABAP system over ADT as an editable filesystem and exposes system tools to GitHub Copilot and external MCP clients.independent, abapVS Code extension editing ABAP systems over ADT as a filesystem
- mcp-abap-abap-adt-apimcp-abap-abap-adt-apiThe write half of the same pair: a thin wrapper over Marcello Urbani's abap-adt-api, exposing lock, edit, activate, transport and syntax check for a full development loop.independent, abapWrite-oriented MCP server over abap-adt-api
- mcp-abap-adtmcp-abap-adtThe read-oriented half of a pair of ABAP MCP servers: high-level tools such as GetProgram, GetClass and GetTable that fetch from a system, aimed at understanding it rather than changing it.independent, abapRead-oriented MCP server fetching ABAP programs, classes, tables
- SAP MCP Connection ManagerSAP MCP Connection ManagerA Windows desktop manager that holds SAP connections and hands them to Claude Desktop or Codex through a local MCP server, each connection carrying a policy that decides what the assistant may change and what data it may read.independent, abapWindows desktop manager handing SAP connections to assistants over MCP
- ABAPilotABAPilotAn MIT-licensed MCP connector for ECC and on-premise S/4HANA that reads ABAP source and dictionary context, whose SAP-side half is a licensed product you install in the system.independent, abapMCP connector for ECC and on-premise S/4HANA with a licensed SAP side
- vibing-steampunkvibing-steampunkAn ADT-to-MCP bridge in Go that reaches past what ADT exposes — cluster tables decoded, spool and job logs read as tables, the IMG searched, selection texts written back.independent, abapADT-to-MCP bridge in Go reaching past what ADT exposes
- ADT MCP ServerADT MCP ServerSAP's own ADT MCP server, and not a package: a preference inside ABAP Development Tools for VS Code that starts a local HTTP MCP server on a port you choose.sap official, abapLocal HTTP MCP server started from ABAP Development Tools for VS Code
- ABAP Development Tools for VS CodeABAP Development Tools for VS CodeSAP's ABAP tools in VS Code: editing, debugging, ABAP Unit, ATC and transports for classes, CDS and RAP objects, over RFC to an on-premise or Private Cloud system and HTTP to a cloud one, with Joule's ADT MCP server and code completion behind an AI-unit licence.sap official, abapSAP's ABAP tools in VS Code for editing, debugging, ATC and transports
- SAP Joule for Developers, ABAP AI capabilitiesSAP Joule for Developers, ABAP AI capabilitiesSAP's AI for ABAP development in ADT for Eclipse and VS Code: chat, code completion, explain, test and CDS generation, RAP logic prediction, and since June 2026 an agentic mode over the ADT MCP Server, metered in AI units through the ABAP AI Hub Service on BTP.sap official, abapSAP's AI for ABAP development in ADT for Eclipse and VS Code
- ABAPDocMCPABAPDocMCPTurns a transport request into a WRICEF technical specification: reads the transport's objects and source over ADT and writes a structured Markdown document with an object-relationship diagram.independent, abapMCP server turning a transport request into a WRICEF specification
- claude-sap-kitclaude-sap-kitA Claude Code plugin of three skills that extends arc-1 with five Custom_* tools for an on-premise ABAP system: running a report and reading its ALV as JSON, previewing a NAST message as PDF, and reading, writing and replacing SmartForms as XML.independent, abapClaude Code plugin adding Custom_* tools to arc-1
- Skybuffer AI MCP serverSkybuffer AI MCP serverAn ABAP add-on that serves SAP business data, transactions and development context as MCP tools from an ICF node inside SAP ECC and S/4HANA, each call running as the signed-in user under PFCG authorization checks.independent, abapABAP add-on serving business data and transactions as MCP tools
- abap-adt-cliabap-adt-cliPulls an ABAP package to local files over the ADT REST API in parallel, and pushes edited objects back under a transport — bulk sync rather than one object at a time in SE80 or Eclipse.independent, abapCLI that pulls and pushes ABAP packages as local files over ADT
- workskong/mcp-abap-adtworkskong/mcp-abap-adtA deliberately light MCP adapter over ABAP ADT for object search, source, DDIC metadata, a data preview and runtime diagnostics, read-only in practice and documented in Korean.independent, abapLight MCP adapter for ABAP over ADT, documented in Korean
- KlystronKlystronAn MCP server written in ABAP that runs inside the application server behind an ICF service and exposes typed tools for ABAP development, quality, transports, customizing, roles, Basis operations and integration, with a client-side plugin of SAP skills.independent, abapMCP server in ABAP inside the application server, with agent skills
- ABAP-AI-CODE-TOOLSABAP-AI-CODE-TOOLSAn optional abapGit package that adds create, modify and delete tools to ABAP AI Code, for ABAP programs and classes, with each diff block approved before it is saved.independent, abapabapGit package adding create, modify and delete tools to ABAP AI Code
- ABAP AI CodeABAP AI CodeAn agentic coding assistant written in ABAP that runs as a SAP GUI report and reads, explains and reviews repository objects inside the system, running an LLM's tool calls as ABAP.independent, abapAgentic coding assistant in ABAP that runs as an SAP GUI report
- VERTEXVERTEXAn extension for ABAP Development Tools for Eclipse and VS Code that shows Simple Data Explorer, AVE and ACE in the editor over the developer's ADT connection.independent, abapADT extension for Eclipse and VS Code showing three SAP GUI tools
Tool governanceTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.SAP and community, unassessed
- arc-mcp-hubarc-mcp-hubA hub on SAP BTP that puts several arc-1 instances, one per SAP system, behind one login and a route each, exchanging the caller's token through a destination so each system still sees the real user.independent, btpHub on SAP BTP putting several arc-1 instances behind one login
- SuperClaude for SAPSuperClaude for SAPA Claude Code plugin that installs and wires its own ABAP MCP server, then puts a two-layer write guard between the agent and any system profile marked QA or production.independent, abapClaude Code plugin with an ABAP MCP server and write guards
- bw-modeling-mcpbw-modeling-mcpReads, creates and modifies BW/4HANA modelling objects through the same internal APIs Eclipse BWMT and the BW/4HANA Cockpit use — and can run centrally on BTP with each caller reaching BW as themselves.independent, btpMCP server for BW/4HANA modelling objects
- Maherd18/sap-mcp-serverMaherd18/sap-mcp-serverAn MCP server for ABAP development over the ADT resources: eight tools, each checked against a JSON policy file before the call reaches the system, with activation and transport release held for a person to approve.independent, abapPolicy-checked MCP server for ABAP development over ADT
- SAP API Policy Evidence SkillSAP API Policy Evidence SkillAssesses whether a described SAP API usage aligns with the SAP API Policy, gathering live evidence from SAP's own sources and returning a sourced assessment with a stated confidence — and routing the legal questions away from itself.independent, btpSkill assessing API usage against the SAP API Policy
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, ai-and-agents
History in the atlas
- The concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- Handed over as a URL. Filed behind the ABAP door because the system it reaches is an ABAP one and the reader who points it at theirs is working on that system, which is the opposite case from [open-rfc](artifact:marianfoo-open-rfc), a client an ABAP developer would never install. Three edges: [MCP servers](capability:mcp-servers) for the tool surface over function modules, [agent access to your code](capability:agent-code-access) for `read_abap_source` alone, and [tool governance](capability:tool-governance) for the allowlists, the table guard, the result limits and the audit log, which the README states as the point of the server rather than as a footnote. [RFC connectivity](capability:rfc-connectivity) was considered and left off: the RFC client here is [PyRFC](external:pyrfc), so nobody installs this to call a function module from their own code. No flavor is stated, since the README names no ABAP release or cloud edition, and `auth` and `tool_count` are left out because the README names neither a mechanism nor a number.
- First seen.
For your agent
- Ref
artifact:yassinbahri-pyrfc-mcp- JSON
- /artifacts/yassinbahri-pyrfc-mcp.json
- MCP
- Connecting an agent