Enterprise2-minute readEN · DE · IT

SAP + AI: which connector should I install?

Drop-in MCP adapters for SAP Business One, SAP S/4HANA Cloud and SAP Concur — plus a DIY pattern for SAP ECC / on-premise systems.

HCBy HelpCode teamUpdated 2 min read Open source on GitHub

No credit card · 7-day trial · Self-host alternative available

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Source-available BSL-1.1
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Drop-in MCP adapters for SAP Business One, SAP S/4HANA Cloud and SAP Concur — plus a DIY pattern for SAP ECC / on-premise systems.

Three drop-in SAP adapters — install in one click

AnythingMCP now ships three pre-configured SAP connectors. Pick the one that matches your tenant — credentials in, MCP server out, no JSON-wrangling required.

AdapterBest forAuthTools
SAP Business OneDACH SMBs running B1 (Service Layer OData v4)Username + Password + Company DB12
SAP S/4HANA CloudEnterprise on S/4HANA Cloud Public EditionOAuth 2.0 client_credentials (BTP)15
SAP ConcurTravel & expense management (Concur sandbox is free)OAuth 2.0 refresh-token10

Click the adapter you need, paste your credentials, mint an MCP API key — done.

What's NOT covered (yet)

  • SAP S/4HANA On-Premise — APIs are tenant-specific and reachable only inside your network. Use the DIY pattern below.
  • SAP ECC (R/3 / 6.x) — Legacy. Reachable via Netweaver Gateway OData. DIY pattern below.
  • SAP SuccessFactors — Requires OAuth 2.0 SAML Bearer assertion (X.509-signed). On the roadmap; open an issue to vote it up.
  • SAP Ariba / Fieldglass / Commerce Cloud / Sales Cloud — Possible but not yet pre-configured.

DIY pattern for S/4HANA on-prem and ECC

Both legacy systems expose OData via SAP Netweaver Gateway. AnythingMCP works as a generic gateway: point it at your endpoints and it generates an MCP server.

Step 1 — Deploy AnythingMCP

git clone https://github.com/HelpCode-ai/anythingmcp.git
cd anythingmcp && docker compose up -d

Step 2 — Create a REST connector pointing at your Gateway

In the AnythingMCP dashboard, set the base URL to your Gateway OData endpoint:

  • S/4HANA On-Premise: https://your-sap-server:port/sap/opu/odata/sap
  • ECC via Netweaver Gateway: same shape, requires sap-client header

Authenticate with Basic Auth (technical user) or OAuth 2.0 SAML Bearer if your tenant has SAP IAS. Add the sap-client header and, for write operations, x-csrf-token: fetch followed by the returned token.

Step 3 — Import OData $metadata as an OpenAPI spec

Fetch GET /sap/opu/odata/sap/{API_NAME}/$metadata, paste the XML into AnythingMCP's OpenAPI importer — the tools generate automatically.

Step 4 — Add the MCP server to Claude

{
  "mcpServers": {
    "sap": { "url": "https://cloud.anythingmcp.com/mcp" }
  }
}

Or on claude.ai → Settings → Connectors → Add custom connector. Bearer token = your MCP API key.

Security best practices

  1. Dedicated technical user with the minimum SAP authorization profile required.
  2. Read-only first — expose GET endpoints only; add writes one connector at a time.
  3. Audit log on — every tool invocation is logged in AnythingMCP and reviewable.
  4. Rate-limit — set per-tool quotas so a runaway prompt can't DoS your SAP box.

Next steps

Was this guide helpful?

Ready to ship

Ship MCP to your stack in 60 seconds.

Spin up AnythingMCP on managed Cloud or self-host it on your infrastructure. Free for 7 days, no credit card.

Related guides