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 →

Skybuffer AI MCP server

An 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.

The server is an ABAP add-on in the /SKYBFR/ namespace, activated as an ICF node in SICF, and every tool runs as the signed-in user with the standard PFCG checks, so the system stays the authority on who sees what and each change lands in SAP with a change document. Three families of tools: business data read from the tables, views or CDS views entered in /SKYBFR/YAICDSNM, which the server turns into tools by itself; transactional tools that create, update and delete; and development tools for object metadata, source code and ST22 dumps. A custom tool is an ABAP class implementing /SKYBFR/IF_YAI_OPERATION and /SKYBFR/IF_YAI_SCHEMA, registered in /SKYBFR/YAICMCPN and moved with ordinary transports. It needs neither SAP BTP nor SAP Integration Suite; a client outside the network reaches it through the Cloud Connector or the SAP Destination service, and the Integration Suite's MCP gateway can sit in front of it. Platform MCP servers for code intelligence and development rules run beside it on SAP HANA or BTP and are not this entry; no release floor, licence or price is stated, and the product is reached through a booked session.

Where it sits

Lives in
Provides
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).Serve your application over MCPABAPServe your application over MCPcapabilityExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).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.
Requires
ABAP platformABAP platformoutside the atlasis installed as an ABAP add-on and served from an ICF node of the system it runs in, on ECC or S/4HANA

Who is behind it

Skybuffer AS

Before choosing this

Signals

CommercialCommercialIts maker offers it commercially

Its maker states it is offered commercially: “Business AI Scenarios Package is licensed per installation number and is dependent on subscription end date.” (Product License – Documentation, checked 2026-10-22).

Conditions

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 Serve your application over MCPAn MCP server exposes an SAP API, or 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
inside the SAP system
Transport
HTTP
Read-only
nostates it is not
Guardrails
4 quoted from its documentation show all
  • Every call runs as the signed-in user, with SAP authorizations enforced in the ABAP kernel.

  • The tools run in ABAP as the calling user, so the standard PFCG authorization checks apply. An assistant can never see or change more than the person using it.

  • Note: Standard SAP authorization checks are never skipped; this is for additional, tool-specific checks.

  • Every change is recorded in SAP, next to the user who made it.

For agent access to ABAP code

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

Connections4

Skybuffer AI MCP server connectionsSkybuffer AI MCP serverPROVIDES→ provides3provides stated Gives a coding assistant object metadata, source code and ST22 short dumps from the system through the same MCP tools, under the developer's own authorizations. MCP server for SAP ECC and S/4HANA: Skybuffer AI: https://www.skybuffer.com/mcp-server/Agent access to your codeprovides stated Publishes business data and transactions of the system it runs in as MCP tools: reads from the data sources an administrator lists, and create, update and delete operations written as ABAP classes, each call under the signed-in user's authorizations with a change document behind it. MCP server for SAP ECC and S/4HANA: Skybuffer AI: https://www.skybuffer.com/mcp-server/ MCP server for SAP ECC and S/4HANA: Skybuffer AI: https://www.skybuffer.com/mcp-server/ MCP server for SAP ECC and S/4HANA: Skybuffer AI: https://www.skybuffer.com/mcp-server/Agent access to your systemsprovides stated Makes the ABAP system itself the MCP server, behind an ICF node: a table, view or CDS view entered in /SKYBFR/YAICDSNM becomes a tool without code, and a custom tool is an ABAP class implementing /SKYBFR/IF_YAI_OPERATION and /SKYBFR/IF_YAI_SCHEMA, registered by name and class in /SKYBFR/YAICMCPN and listed to clients through tools/list. MCP Server Configuration in ABAP System – Documentation: https://doc.skybuffer.com/documentation/skybuffer-ai/business-ai-scenarios-package/mcp-server/mcp-server-configuration-in-abap-system/ MCP Tools Creation – Documentation: https://doc.skybuffer.com/documentation/skybuffer-ai/business-ai-scenarios-package/mcp-server/mcp-tools-creation/ MCP Tools Creation – Documentation: https://doc.skybuffer.com/documentation/skybuffer-ai/business-ai-scenarios-package/mcp-server/mcp-tools-creation/Serve your application over MCPNEEDS→ needs1needs stated is installed as an ABAP add-on and served from an ICF node of the system it runs in, on ECC or S/4HANA MCP server for SAP ECC and S/4HANA: Skybuffer AI: https://www.skybuffer.com/mcp-server/ MCP Server Configuration in ABAP System – Documentation: https://doc.skybuffer.com/documentation/skybuffer-ai/business-ai-scenarios-package/mcp-server/mcp-server-configuration-in-abap-system/ABAP platform
Transport
HTTP
ABAP platformMCP server for SAP ECC and S/4HANA: Skybuffer AI, checked 2026-10-22: “The MCP server runs in the ABAP system.”; MCP Server Configuration in ABAP System – Documentation, checked 2026-10-22: “Step 3. Use right mouse button click and choose Test Service to get MCP Server URL:”; MCP Tools Creation – Documentation, checked 2026-10-22: “curl -X POST http://[YOUR_SERVER_PATH]/mcp \ -H “Content-Type: application/json” \ -H “Accept: application/json, text/event-stream” \ -H “Mcp-Session-Id: [YOUR_SESSION_ID]””HTTPdocumentedrequiresYour MCP client, actorYour MCP clientABAP platform, SAP solutionABAP platformSAP solutionSkybuffer AI MCP server, moduleSkybuffer AI MCPserver
SAPnot SAP's, or the project's ownstated by the sourcedocumented only

Others providing53

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. odata_mcp_goGo binary bridging any OData v2 or v4 service to MCP
  7. odata_mcpPython bridge generating MCP tools from OData v2 metadata
  8. 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.
  9. sap-security-mcpRead-only security analysis MCP server for SAP audits and SoD review
  10. KlystronMCP server in ABAP inside the application server, with agent skills
  11. pyrfc-mcpMCP server calling RFC-enabled function modules behind an allowlist
Serve your application over MCP
  1. abap-ai/mcpMCP server SDK written in ABAP
  2. abap-ai/mcp2Stateless ABAP MCP server SDK for the 2026-07-28 protocol draft
  3. abap-agent-runtimeABAP-native MCP endpoint that drives opted-in abap2UI5 apps
  4. MarkWuRY168/SAP_MCPMCP server publishing SAP functions as tools from config tables
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. dassian-adtFork of mcp-abap-abap-adt-api with 25 tools and session recovery
  13. erpl-adtC++ binary speaking the ADT REST API as a CLI and MCP server
  14. bw-modeling-mcpMCP server for BW/4HANA modelling objects
  15. EPOD ADT MCP ServerMCP server for ABAP on the ADT session, in Eclipse or standalone
  16. ZARC1_EXTENSION_FORMSarc-1 extension for SAPscript and Smart Forms objects
  17. 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.
  18. fr0ster/mcp-abap-adtABAP MCP server with full CRUD on on-premise and ABAP Cloud
  19. abapsmithABAP MCP server over ADT with a local journal that can undo writes
  20. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP system
  21. aibap.mcpGo MCP server that writes, activates and runs ABAP classes via ADT
  22. BellaEclipse plugin bringing Claude into ABAP Development Tools
  23. Maherd18/sap-mcp-serverPolicy-checked MCP server for ABAP development over ADT
  24. sapdumpmcpMCP server reading ABAP short dumps over ADT
  25. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystem
  26. mcp-abap-abap-adt-apiWrite-oriented MCP server over abap-adt-api
  27. mcp-abap-adtRead-oriented MCP server fetching ABAP programs, classes, tables
  28. SAP MCP Connection ManagerWindows desktop manager handing SAP connections to assistants over MCP
  29. ABAPilotMCP connector for ECC and on-premise S/4HANA with a licensed SAP side
  30. vibing-steampunkADT-to-MCP bridge in Go reaching past what ADT exposes
  31. ADT MCP ServerLocal HTTP MCP server started from ABAP Development Tools for VS Code
  32. ABAP Development Tools for VS CodeSAP's ABAP tools in VS Code for editing, debugging, ATC and transports
  33. SAP Joule for Developers, ABAP AI capabilitiesSAP's AI for ABAP development in ADT for Eclipse and VS Code
  34. ABAPDocMCPMCP server turning a transport request into a WRICEF specification
  35. claude-sap-kitClaude Code plugin adding Custom_* tools to arc-1
  36. abap-adt-cliCLI that pulls and pushes ABAP packages as local files over ADT
  37. workskong/mcp-abap-adtLight MCP adapter for ABAP over ADT, documented in Korean
  38. KlystronMCP server in ABAP inside the application server, with agent skills
  39. pyrfc-mcpMCP server calling RFC-enabled function modules behind an allowlist
  40. ABAP-AI-CODE-TOOLSabapGit package adding create, modify and delete tools to ABAP AI Code
  41. ABAP AI CodeAgentic coding assistant in ABAP that runs as an SAP GUI report
  42. VERTEXADT extension for Eclipse and VS Code showing three SAP GUI tools

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
Flavors1
Standard ABAP
“It runs inside the ABAP stack of SAP ECC and SAP S/4HANA, on-premise or connected from your SAP BTP subaccount.” — MCP server for SAP ECC and S/4HANA: Skybuffer AIchecked
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:skybuffer-ai-mcp-server
JSON
/artifacts/skybuffer-ai-mcp-server.json
MCP
Connecting an agent