MCP serverMCP servertypeExposes tools to a coding agent over MCP.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

SAP LeanIX MCP Server

Hosted MCP endpoint onto an SAP LeanIX instance, exposing selected enterprise-architecture APIs as tools — fact sheets, applications, completeness and custom reports.

Enterprise-architecture data sits behind APIs an agent would have to be taught one at a time. LeanIX exposes selected ones as MCP tools with structured descriptions, inputs and output types, so an assistant can ask what is available and then invoke things like getting an application by id or listing fact sheets with a low completeness score as steps in a workflow. Hosted and secured against your own instance; a companion Claude plugin and agent skills are published separately.

Where it sits

Lives in
Provides
Agent access to your systemsBTPAgent 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).
Requires
SAP LeanIXSAP LeanIXoutside the atlasExposing enterprise-architecture data from a SAP LeanIX workspace as MCP tools

Before choosing this

Conditions

PracticalFunctional boundary

This is enterprise-architecture data, not a development surface — it answers what your landscape contains, never what your code does, and nothing in it belongs in a build. Entered here because it is a first-party SAP MCP endpoint and the catalogue that tracks this corner lists it; the atlas maps SAP development, so treat it as adjacent rather than as tooling for a project.

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
By SAP

Connections3

Learn more1

Readings
  1. From confident to correct: AI search results you can actually trustSAP TechEd — session catalogue
Where SAP LeanIX MCP Server runsSAP cloudBy its type: an MCP server is called by an MCP clientcallsdocumentedrequiresYour MCP client, actorYour MCP clientSAP LeanIX MCP Server, moduleSAP LeanIX MCPServerSAP LeanIX, SAP solutionSAP LeanIXSAP solution
SAPnot SAP's, or the project's ownstated in the documentdocumented only
Agent access to your systems
  1. mcp-integration-suiteMCP server for the general Integration Suite functions
  2. mcp-is-tpmJava MCP server for Integration Suite Trading Partner Management
  3. calmcpMCP server with read tools over the SAP Cloud ALM APIs
  4. CostingGeek/sap-mcpPython MCP server fetching sales orders from SAP's business data graph
  5. mcp-sap-focusedrunMCP tools over SAP Focused Run's Landscape Management Database
  6. cloud-alm-itsm-mcpMCP server querying installations via the SAP Cloud ALM ITSM API
  7. hana-mcp-serverMCP server for schema discovery and guarded SQL on SAP HANA
  8. sap_analytics_cloud_mcpMCP server for the SAP Analytics Cloud REST API
  9. mcp-sap-cpiMCP server for Cloud Integration runtime: messages, logs, deployment
  10. AI Core MCP ServerSAP AI Core APIs as MCP tools from one JSON config file
  11. BTP CF MCP ServerCloud Foundry V3 API on SAP BTP as MCP tools
  12. BTP MCP ServerBTP Core Services as MCP tools with in-chat dashboards
  13. btp-sap-odata-to-mcp-serverExposes S/4HANA or ECC OData services as MCP tools
  14. CI MCP ServerSAP Cloud Integration OData APIs as MCP tools
  15. odata-mcp-proxyConfig-driven proxy turning OData and REST endpoints into MCP tools
  16. sap-pi-mcp-serverMCP server for SAP PI and PO monitoring and directory metadata
  17. sap-bdc-mcp-serverMCP server managing Delta shares in SAP Business Data Cloud
  18. @mariodefe/sap-datasphere-mcpMCP server with forty-five tools across a Datasphere tenant
  19. midasol/sap-mcp-serverPython MCP server for SAP Gateway OData operations
  20. odata_mcp_goGo binary bridging any OData v2 or v4 service to MCP
  21. odata_mcpPython bridge generating MCP tools from OData v2 metadata
  22. sap-bdc-mcpMCP tooling for SAP Business Data Cloud discovery and contracts
  23. mcp-sap-datasphere-serverRead-only MCP server for exploring SAP Datasphere
  24. MCP Server for SAP BTP AdministrationSAP-hosted MCP endpoint for BTP account administration
  25. SAP-samples/hana-cli-claude-pluginClaude Code plugin registering hana-cli's MCP server
  26. SAP-samples/hana-developer-cli-tool-exampleDeveloper-centric command line for SAP HANA
  27. cpi-mcp-serverGo MCP server over Cloud Integration packages and integration flows

Details

Sources1
sap-ai-mcp-serversdiscovered 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 viasap-ai-mcp-servers
first seen in the atlas
ecosystem and domainbtp, ai-and-agents
History in the atlas3
  1. 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.
  2. Entered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it. Classified btp because the ecosystem list has no door for enterprise architecture and hard rule 9 allows only one; the strain is recorded here rather than hidden in the choice.
  3. First seen.
For your agent
Ref
artifact:sap-leanix-mcp-server
JSON
/artifacts/sap-leanix-mcp-server.json
MCP
Connecting an agent