onedevatlasBeta
Browse the atlas
AllABAPCAPUI5BTP
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 →

MarkWuRY168/SAP_MCP

Publishes SAP system functions as MCP tools from configuration tables held inside the SAP system, so adding a tool is a configuration change rather than a code change.

The inversion is the point: rather than a fixed tool set decided by the server's author, the tool list lives in configuration tables in the SAP system, and the server reads it. Deploy once and extend by configuring — a shape that suits a team exposing its own custom transactions and function modules rather than the standard surface everything else here covers. A FastAPI service with a web management interface for service status, logs, port conflicts and the configuration itself, and documentation in Chinese, Japanese and English.

GitHubnot reachable

Facts

Last pushLicenceMIT

Where it sits

Lives in
ABAP
Provides
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).

Who is behind it

MarkWuRY168MarkWuRY168PersonMaintains this
In the atlas: maintains 1, contributes to 1@MarkWuRY168maintainer

Before choosing this

Signals

RepositoryNot reachableNot reachable since 2026-10-20

Since 2026-10-20 the repository this entry names answers that it does not exist.

Conditions

PracticalFunctional boundary

What it exposes is whatever somebody put in the configuration table, which moves the governance question inside the SAP system and out of the server — an advantage if that table is controlled and a hazard if it is not. The web management interface is a second surface to secure alongside the MCP one.

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 →

What it declares

Every artifact

Type
MCP server
Origin
Independently maintained

As an MCP server

Runs as
local process
Transport
HTTP
Authentication
user and password
Guardrails
3 quoted from README show all

  • Manage tool lists through configuration tables in SAP system without needing to update code each time

  • Configuration files added to .gitignore, will not be committed to version control

  • Support configuring sensitive information through environment variables

Connections1

Architecture

Download
Your machineMarkWuRY168/SAP_MCP — README, checked 2026-09-11: “**MCP Server**: http://localhost:6688/mcp”HTTPYour MCP client, actorYour MCP clientMarkWuRY168/SAP_MCP, moduleMarkWuRY168/SAP_MCP
SAPnot SAP's, or the project's ownstated in the document

Others providing4

Compare all 5 on the Serve your application over MCP page →
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. Skybuffer AI MCP serverABAP add-on serving business data and transactions as MCP tools

Details

Sources2
sap-ai-mcp-serversdiscovered herechecked
github.com/MarkWuRY168/SAP_MCPtree, pushes, contributors, CIchecked

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
not reachable since, 3 crawls
discovered viasap-ai-mcp-servers
first seen in the atlas
ecosystem and domainabap, ai-and-agents
History in the atlas2
  1. Triaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README. Filed on the BTP door because there is no door for the SAP product it fronts and hard rule 9 allows one — the same strain recorded on the LeanIX entries.
  2. First seen.
For your agent
Ref
artifact:markwury168-sap-mcp
JSON
/artifacts/markwury168-sap-mcp.json
MCP
Connecting an agent