MCP serverMCP servertypeExposes tools to a coding agent over MCP.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

ABAP MCP

A VS Code extension that deploys a bundled ABAP MCP server into each workspace folder on open: 25 ADT and OData tools and five spec-driven-development prompts over one SAP session.

Installed from the VS Code Marketplace, it writes a .vscode/mcp.json into each workspace folder on open and points it at the server binary bundled for that operating system, so the SAP connection variables are all that is left to fill in. The server exposes 25 tools over a single SAP session: 16 ADT tools that search the repository, read object source and metadata, write Z* objects under a lock with a syntax check on every create, assign transports, run ATC and ABAP Unit, preview table and CDS data, and read ST22 dumps and Gateway error-log entries from the live system; and 9 OData tools that find a service across the V2 Gateway catalogue and the V4 catalogue, read its entity sets and actions, then query and write business data through it. The two halves use two SAP clients: SAP_CLIENT for repository work, and an optional SAP_TEST_CLIENT that only the odata_* tools follow, because the service under test is often activated only in the test client. The same binary serves a five-phase spec-driven-development workflow as MCP prompts (spec, plan, tasks, impl, gap), and each phase writes files under specs/ that the next phase reads back. Nothing else is copied into the workspace: every tool carries its own usage contract over the MCP protocol.

Where it sits

Lives in
Provides
Agent access to your codeABAPAgent access to your codecapabilityLetting 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.Agent access to your systemsABAPAgent access to your systemscapabilityGiving 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).Calling a service by handABAPCalling a service by handcapabilitySending a request to an OData service or a push channel on a system and reading what comes back, while building it or chasing an error, before any client exists. Distinct from [unit testing](capability:abap-unit-testing), which proves logic in code and keeps the proof.Agent guidanceABAPAgent guidancecapabilityPackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.
Requires
ABAP platformABAP platformoutside the atlasthe system the tools work against; the listing names SAP ABAP system credentials as a requirement and the connection variables live in the deployed mcp.jsonADT resourcesADT resourcesartifactthe repository half of the tools reaches objects, checks and the data preview through the system's ADT services

Before choosing this

Conditions

PracticalFunctional boundary

The bundled binaries are x64 only, and on an unsupported platform the extension shows an activation error. The SAP password sits in .vscode/mcp.json, which the listing calls not secure for production use, and a force deploy or a version update overwrites that file, so the credentials have to be entered again. Object creation and change are confined to $TMP or a Z*-custom package.

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 →
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 →

What it declares

Every artifact

Type
MCP server
Origin
Independently maintained

As an MCP server

Transport
stdio

For agent access to ABAP code

Read
sourcesearchwhere-usedDDICCDStable data
Change
writecreateactivatetransportsgit
Check
syntaxATCABAP Unit
Run
run codedumps
property statedstated nonot said

For agent guidance

Installs into
Claude CodeGitHub Copilot
System reach
Supplied with it
Topics
RAPClean core

Tasks this contributes to1Beta

Generate a RAP business object by prompting an agentA developer describes the travel application they want and an agent creates the RAP objects in the ABAP system, instead of printing source for the developer to paste into the editor.Covers, under conditionsspecification-first path to the objects

SAP ABAP system credentials in the workspace .vscode/mcp.json; the listing names SAP system access as a requirement. Claude Code or GitHub Copilot as the client, which is where the prompts appear as slash commands under the abap-mcp server. Windows, macOS or Linux on x64, because the extension bundles a platform-specific server binary. Objects go to $TMP unless an existing Z*-custom package and a transport request are supplied.

All options on the Agent access to ABAP code page →

Connections8

ABAP MCP connectionsABAP MCPPROVIDES→ provides4provides stated Puts 16 ADT tools in front of a coding agent over one SAP session: repository search, source and metadata for about twenty object types, creation and change of Z* objects with lock, syntax check and activation, transport assignment, ATC findings, ABAP Unit runs, where-used, a read-only data preview over tables and CDS views, and ST22 dump and Gateway error-log reads. Syntax reference is read from the connected system's own ABAP Keyword Documentation at call time, so it matches that system's release. ABAP MCP — Visual Studio Marketplace, MCP Tools Reference: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcp ABAP MCP — Visual Studio Marketplace, ADT / repository tools: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcpAgent access to your codeprovides stated Nine OData tools read and write business data on the connected system through a published service: a search across the V2 Gateway catalogue and the V4 catalogue together, a metadata lookup returning entity sets, keys and actions, then query, count, create with deep insert, update, delete, bound and unbound RAP action calls, and an atomic $batch. Every response names the SAP client the call used, and the tools repair read-safe mistakes on their own while never re-sending a write silently. ABAP MCP — Visual Studio Marketplace, OData Service Access (V2 & V4): https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcp ABAP MCP — Visual Studio Marketplace, MCP Tools Reference: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcpAgent access to your systemsprovides stated Serves a five-phase spec-driven-development workflow for ABAP as MCP prompts from the bundled server (spec, plan, tasks, impl, gap), so the phases appear in the slash-command list under the abap-mcp server once it connects and no command, agent or instruction file is copied into the workspace. The plan phase checks GetReleasedAPI for every standard BAPI, function module and table used and validates against Clean Core principles; the impl phase runs one tasks file at a time against the live system through create or change, ATC, activate, ABAP Unit and an OData smoke test. ABAP MCP — Visual Studio Marketplace, Spec-Driven Development (SDD) Prompts: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcp ABAP MCP — Visual Studio Marketplace, Prompts — Spec-Driven Development (SDD): https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcp ABAP MCP — Visual Studio Marketplace, Prompts — Spec-Driven Development (SDD): https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcpAgent guidanceprovides stated Calls a service on the connected system from the agent session, which is what shows whether an activated service binding publishes and answers. An optional `SAP_TEST_CLIENT` sends every `odata_*` call to a test client while the ADT tools stay in the development client, and the troubleshooting section reads a 401, a 403 or a 404 from a service the catalogue search can see as a question about which client was used. ABAP MCP — Visual Studio Marketplace, OData Service Access (V2 & V4): https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcp ABAP MCP — Visual Studio Marketplace, Why SAP_TEST_CLIENT matters: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcp ABAP MCP — Visual Studio Marketplace, Troubleshooting: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcpCalling a service by handNEEDS→ connects to2connects to stated reads and writes repository objects over ADT in SAP_CLIENT, and reads and writes business data through published OData services in SAP_TEST_CLIENT where one is configured ABAP MCP — Visual Studio Marketplace, Why SAP_TEST_CLIENT matters: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcp ABAP MCP — Visual Studio Marketplace, OData Service Access (V2 & V4): https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcpABAP platformconnects to stated the agent picks up the tools and the SDD prompts once the server connects, with each tool carrying its own usage contract over the protocol ABAP MCP — Visual Studio Marketplace, Self-Documenting Tools & Prompts: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcpGitHub Copilot→ needs2needs stated the system the tools work against; the listing names SAP ABAP system credentials as a requirement and the connection variables live in the deployed mcp.json ABAP MCP — Visual Studio Marketplace, Requirements: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcpABAP platformneeds stated the repository half of the tools reaches objects, checks and the data preview through the system's ADT services ABAP MCP — Visual Studio Marketplace, ADT / repository tools: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcp ABAP MCP — Visual Studio Marketplace, ADT / repository tools: https://marketplace.visualstudio.com/items?itemName=harieprasad.abap-mcpADT resources
ABAP MCP — Visual Studio Marketplace, Quick Start, checked 2026-10-31: “"type": "stdio"”stdiodocumentedHTTPOData V2, OData V4, outbound,syncdocumentedrequiresdocumentedMCP, inboundWhere ABAP MCP runsYour ABAP systemThird partyYour MCP client, actorYour MCP clientABAP platform, SAP solutionABAP platformSAP solutionABAP MCP, moduleABAP MCPADT resources, service instanceADT resourcesGitHub Copilot, Hosted serviceGitHub CopilotHosted service
SAPnot SAP's, or the project's ownstated in the documentdocumented only

Others providing71

Agent access to ABAP code
  1. @abap2ui5/mcp-serverMCP server for the abap2UI5 check, deploy and run loop
  2. arc-1-bopf-enharc-1 extension for reading and maintaining BOPF enhancements
  3. HammerNative macOS code editor for ABAP and CDS
  4. arc-1-lspEdition of ARC-1 that runs ADT calls through adt-ls
  5. arc-1MCP server over the ADT REST API for ABAP objects
  6. arc1-abap-bridgeVS Code bridge between arc-1 and ADT for VS Code
  7. arc1-adt-abap-mcp-extEclipse add-on enabling the ADT MCP server with read-only tools
  8. ABAP Accelerator MCP ServerAWS's ABAP MCP server for Amazon Q Developer and Kiro
  9. Modernization Agents for SAP on AWSAWS agents for ABAP, PI/PO and BW modernisation work
  10. @mcp-abap-adt/coreABAP ADT MCP server published as an npm scope and plugin
  11. chandrashekhar-mahajan/abap-mcp-serverABAP MCP server with ADT tools and five authentication strategies
  12. ADAMMCP server driving SAP's ABAP debugger over ADT for an agent
  13. dassian-adtFork of mcp-abap-abap-adt-api with 25 tools and session recovery
  14. erpl-adtC++ binary speaking the ADT REST API as a CLI and MCP server
  15. bw-modeling-mcpMCP server for BW/4HANA modelling objects
  16. EPOD ADT MCP ServerMCP server for ABAP on the ADT session, in Eclipse or standalone
  17. ZARC1_EXTENSION_FORMSarc-1 extension for SAPscript and Smart Forms objects
  18. fgalastri/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.
  19. fr0ster/mcp-abap-adtABAP MCP server with full CRUD on on-premise and ABAP Cloud
  20. abapsmithABAP MCP server over ADT with a local journal that can undo writes
  21. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP system
  22. aibap.mcpGo MCP server that writes, activates and runs ABAP classes via ADT
  23. BellaEclipse plugin bringing Claude into ABAP Development Tools
  24. Maherd18/sap-mcp-serverPolicy-checked MCP server for ABAP development over ADT
  25. sapdumpmcpMCP server reading ABAP short dumps over ADT
  26. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystem
  27. mcp-abap-abap-adt-apiWrite-oriented MCP server over abap-adt-api
  28. mcp-abap-adtRead-oriented MCP server fetching ABAP programs, classes, tables
  29. SAP MCP Connection ManagerWindows desktop manager handing SAP connections to assistants over MCP
  30. RAP StudioLocal RAP and classic ABAP runtime with a browser workbench
  31. abap-config-mcpABAP MCP server that writes customizing through the SM30 runtime
  32. ABAPilotMCP connector for ECC and on-premise S/4HANA with a licensed SAP side
  33. vibing-steampunkADT-to-MCP bridge in Go reaching past what ADT exposes
  34. ADT MCP ServerMCP server shipped in ABAP Development Tools for Eclipse and VS Code
  35. ABAP Development Tools for VS CodeSAP's ABAP tools in VS Code, over RFC to on-premise or HTTP to cloud
  36. SAP Joule for Developers, ABAP AI capabilitiesSAP's AI for ABAP development in ADT for Eclipse and VS Code
  37. ABAPDocMCPMCP server turning a transport request into a WRICEF specification
  38. claude-sap-kitClaude Code plugin adding Custom_* tools to arc-1
  39. Skybuffer AI MCP serverABAP add-on serving business data and transactions as MCP tools
  40. abap-adt-cliCLI that pulls and pushes ABAP packages as local files over ADT
  41. workskong/mcp-abap-adtLight MCP adapter for ABAP over ADT, documented in Korean
  42. KlystronMCP server in ABAP inside the application server, with agent skills
  43. pyrfc-mcpMCP server calling RFC-enabled function modules behind an allowlist
  44. ABAP-AI-CODE-TOOLSabapGit package adding create, modify and delete tools to ABAP AI Code
  45. ABAP AI CodeAgentic coding assistant in ABAP that runs as an SAP GUI report
  46. VERTEXADT extension for Eclipse and VS Code showing three SAP GUI tools
Agent access to your systems
  1. @abap2ui5/mcp-serverMCP server for the abap2UI5 check, deploy and run loop
  2. abap2UI5 for VS CodeVS Code extension to preview, activate and lint abap2UI5 apps
  3. abapsmithABAP MCP server over ADT with a local journal that can undo writes
  4. btp-sap-odata-to-mcp-serverExposes S/4HANA or ECC OData services as MCP tools
  5. midasol/sap-mcp-serverPython MCP server for SAP Gateway OData operations
  6. abap-config-mcpABAP MCP server that writes customizing through the SM30 runtime
  7. odata_mcp_goGo binary bridging any OData v2 or v4 service to MCP
  8. odata_mcpPython bridge generating MCP tools from OData v2 metadata
  9. sap-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.
  10. Skybuffer AI MCP serverABAP add-on serving business data and transactions as MCP tools
  11. sap-security-mcpRead-only security analysis MCP server for SAP audits and SoD review
  12. KlystronMCP server in ABAP inside the application server, with agent skills
  13. pyrfc-mcpMCP server calling RFC-enabled function modules behind an allowlist
Calling a service by hand
  1. abap-odata-testABAP client for calling and asserting on OData services
  2. ODAPUUI5 app for OData test requests and ABAP Push Channels
Agent guidance
  1. abap2UI5 for VS CodeVS Code extension to preview, activate and lint abap2UI5 apps
  2. sap-basis-opsRunbook skills for Basis operations at the OS and database layer
  3. abap-offstack-aunitAgent skill for off-stack ABAP Unit tests and an abaplint gate
  4. ARC-1 SkillsTwenty-two agent skills shipped with arc-1
  5. sapskillsAgent skills for Clean ABAP, ADT in VS Code and guardrails
  6. SuperClaude for SAPClaude Code plugin with an ABAP MCP server and write guards
  7. claude-abap-devFive ABAP workflows for Claude Code on existing MCP servers
  8. DanKromp/skillOverflowCollection of 41 agent skills, 37 for SAP development tasks
  9. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP system
  10. sapcli Claude Code PluginAgents and skills that drive sapcli instead of ADT
  11. sap-odata-explorerRust CLI and desktop app for exploring SAP OData services
  12. abap-skillsSeventeen agent skills for ABAP development
  13. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystem
  14. WerkbankLocal desktop workspace for AI conversations with SAP connectors
  15. claude-abap-skillsClaude Code plugins with Clean ABAP rules and templates
  16. SAP Power for KiroSAP skills for the Kiro IDE
  17. SAP Developers MCPHosted MCP server of developers.sap.com tutorials and missions
  18. secondsky/sap-skillsForty SAP development plugins for coding agents
  19. claude-sap-kitClaude Code plugin adding Custom_* tools to arc-1
  20. rap-skillsRAP skills delivered branch-per-target for each deployment
  21. KlystronMCP server in ABAP inside the application server, with agent skills

Details

Sources1
Added by handdiscovered herechecked

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 atlas2
  1. RAP, Clean core
  2. First seen.
For your agent
Ref
artifact:harieprasad-abap-mcp
JSON
/artifacts/harieprasad-abap-mcp.json
MCP
Connecting an agent