Connector guide6-minute read20 MCP tools7 languages

How to Connect SAP S/4HANA Cloud to Claude — via MCP

Drive SAP S/4HANA Cloud Public Edition from any AI agent: business partners, customers, suppliers, sales orders, purchase orders, billing documents, products, journal entries. OAuth 2.0 client_credentials via BTP Communication Arrangement.

HCBy HelpCode teamUpdated 6 min read Open-source on GitHub

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

SAP S/4HANA Cloud

SAP S/4HANA Cloud

Drive SAP S/4HANA Cloud Public Edition from any AI agent: business partners, customers, suppliers, sales orders, purchase orders, billing documents, products, journal entries. OAuth 2.0 client_credentials via BTP Communication Arrangement.

tools

20

Region

INTL

Category

ERP

Authentication

OAuth 2.0

Required env vars

S4_BASE_URLS4_TOKEN_URLS4_CLIENT_IDS4_CLIENT_SECRET
Install in one click on Cloud

7-day free trial · No credit card

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

Skip the install. Get this working in under 2 minutes.

Start a free trial on cloud.anythingmcp.com, add the SAP S/4HANA Cloud in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.

Start free trial

Summary

Drive SAP S/4HANA Cloud Public Edition from any AI agent: business partners, customers, suppliers, sales orders, purchase orders, billing documents, products, journal entries. OAuth 2.0 client_credentials via BTP Communication Arrangement.

Try asking

Example prompts for SAP S/4HANA Cloud

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

SAP S/4HANA Cloud · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → SAP S/4HANA Cloud, paste your credentials, and connect Claude — done. No Docker, no git clone, no local server.

SAP S/4HANA Cloud + Claude

Ask Claude about your SAP S/4HANA Cloud Public Edition data: business partners, customers, suppliers, sales orders, purchase orders, billing documents, deliveries, products and journal entries. The connector has 15 read-only tools on S/4HANA's OData APIs and authenticates with OAuth 2.0 client credentials from a communication arrangement.

What you can ask Claude

  • "Show me business partner 1000123 and tell me whether it is a customer, a supplier or both." Uses s4_get_business_partner, s4_list_customers and s4_list_suppliers.
  • "List the sales orders for sold-to party 17100001." Uses s4_list_sales_orders with an OData filter on SoldToParty.
  • "What's on sales order 0000012345, line by line?" Uses s4_get_sales_order and s4_list_sales_order_items.
  • "Which purchase orders do we have with supplier 17300001?" Uses s4_list_purchase_orders with a filter on Supplier.
  • "List the billing documents dated this month." Uses s4_list_billing_documents with a date filter.
  • "Look up material TG11 in the product master." Uses s4_get_product.

What you need

  • An S/4HANA Cloud Public Edition tenant and an administrator who can set up communication arrangements.
  • A communication arrangement for every API area Claude should read (business partners, sales orders, purchase orders, billing and so on), with a communication user and system that use OAuth 2.0 with the client-credentials grant.
  • Four values for the connector: S4_BASE_URL (your tenant's base URL), S4_TOKEN_URL (the tenant's OAuth token URL), S4_CLIENT_ID and S4_CLIENT_SECRET.

Step 1 — Get credentials

Setup (one-off, done by the S/4 admin):

  1. In your S/4HANA Cloud tenant open Communication Arrangements and create one for SAP_COM_0008 — Business Partner Integration (and others as needed: 0109 Sales Order, 0026 Purchase Order, 0186 Billing).
  2. Create a Communication User + Communication System. Pick OAuth 2.0 as the authentication method, grant type Client Credentials.
  3. S/4 generates a Client ID, Client Secret, and a per-tenant Token URL like https://my300000.authentication.eu10.hana.ondemand.com/oauth/token.
  4. The tenant Base URL is https://my300000.s4hana.cloud.sap (your tenant ID replaces 300000).
  5. Set the four env vars below.

The connector sends the client ID and secret in an HTTP Basic header, as Public Edition requires, and renews the token (typically valid for an hour) on its own shortly before it expires.

Step 2 — Install the adapter

On Cloud, open Connectors → SAP S/4HANA Cloud and paste the four values. To self-host:

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Claude

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

On claude.ai (the connector then also appears in Claude Desktop):

  1. Open claude.ai/customize/connectors.
  2. Click +, then Add custom connector.
  3. Name it AnythingMCP and enter the URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
  4. Click Add, then Connect. Sign in to AnythingMCP and choose which of your MCP servers Claude may use.

In Claude Code, run the command below, then type /mcp in a session and choose Authenticate:

claude mcp add --transport http anythingmcp https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID

Self-hosting? Use your own AnythingMCP URL instead of cloud.anythingmcp.com. For claude.ai it has to be reachable from the internet, because Claude connects from Anthropic's servers, not from your computer.

All tools below appear in your chat — start typing prompts.

Available tools

ToolWhat it does
s4_list_business_partnersList business partners (combined customers + suppliers) from API_BUSINESS_PARTNER
s4_get_business_partnerGet one business partner by its 10-character ID
s4_list_customersList customer master records (subset of business partners)
s4_list_suppliersList supplier master records (subset of business partners)
s4_list_sales_ordersList sales orders (headers)
s4_get_sales_orderGet one sales order by its 10-char number
s4_list_sales_order_itemsList the items (line entries) of a given sales order
s4_list_purchase_ordersList purchase orders (headers)
s4_get_purchase_orderGet one purchase order by its 10-char number
s4_list_billing_documentsList billing documents (customer invoices, credit memos)
s4_list_outbound_deliveriesList outbound delivery headers (goods leaving the warehouse)
s4_list_journal_entriesList journal entry items (general ledger postings)
s4_list_productsList materials / products (item master)
s4_get_productGet one product/material by its ID
s4_list_purchase_requisitionsList purchase requisition items (pre-PO demand requests)

Besides these, the connector carries five built-in OData tools: s4_cloud_list_services, s4_cloud_describe_service, s4_cloud_describe_entity, s4_cloud_query and s4_cloud_get_entity. They read the $metadata of the eight APIs the connector is set up for, so the agent can reach any field of those services with SAP's labels. A service outside that list needs its communication arrangement first. Running S/4HANA on-premise or in Private Cloud? Use SAP S/4HANA (OData) or SAP S/4HANA via HANA SQL instead.

The list tools take top to cap the number of rows; the sales order, purchase order, billing document and business partner lists also take an OData filter.

Troubleshooting

  • No tool works at all. The token request is failing. Check that S4_TOKEN_URL is your tenant's token URL, and that the client ID and secret belong to the communication arrangement you set up.
  • Some areas work, others are refused. Each API needs its own communication arrangement. If business partners come back but sales orders don't, the arrangement for the sales order API is missing for this communication user.
  • A filtered call fails. The filter value is OData syntax with the API's own field names, for example SoldToParty eq '17100001', with strings in single quotes. Ask Claude to show the filter it used and correct the field name.
  • Answers are slow or cut off on big lists. Ask for fewer rows; Claude passes that as top.

FAQ

Can Claude create or change sales orders in S/4HANA? No. All 15 tools read data. Nothing is created, changed or posted in your tenant.

Does it work with S/4HANA on-premise or Private Cloud? This connector is built for S/4HANA Cloud Public Edition. For S/4HANA on-premise and Private Cloud there are two ready adapters: SAP S/4HANA (OData) on SAP Gateway, and SAP S/4HANA (HANA SQL), which reads the HANA database with SAP's data dictionary as tools. Both run on a self-hosted AnythingMCP inside your network.

Does it work with Claude Code as well as Claude Desktop? Yes. A custom connector you add on claude.ai is also available in Claude Desktop, and Claude Code adds the same URL with claude mcp add --transport http. Custom connectors are available on every Claude plan; the Free plan allows one, which is enough because a single AnythingMCP connector carries all your connectors.

Is my data stored by AnythingMCP? Your client ID and secret are stored encrypted (AES-256-GCM) in your workspace and are never shown to Claude. When Claude uses a tool, AnythingMCP calls S/4HANA and passes the result to Claude, and the call is recorded in your workspace's audit log. AnythingMCP Cloud is hosted in Frankfurt, Germany; if the data must stay on your own infrastructure, self-host AnythingMCP.

Next steps

Was this guide helpful?

Your SAP S/4HANA Cloud agent is one click away.

Install the connector, paste the key, prompt Claude. Free for 7 days, no credit card.

Related guides

Connectors

How to Connect SAP S/4HANA Cloud to ChatGPT — via MCP

Drive SAP S/4HANA Cloud Public Edition from any AI agent: business partners, customers, suppliers, sales orders, purchase orders, billing documents, products, journal entries. OAuth 2.0 client_credentials via BTP Communication Arrangement.

Connectors

How to Connect SAP S/4HANA Cloud to Cursor — via MCP

Drive SAP S/4HANA Cloud Public Edition from any AI agent: business partners, customers, suppliers, sales orders, purchase orders, billing documents, products, journal entries. OAuth 2.0 client_credentials via BTP Communication Arrangement.

Connectors

How to Connect SAP S/4HANA Cloud to Gemini — via MCP

Drive SAP S/4HANA Cloud Public Edition from any AI agent: business partners, customers, suppliers, sales orders, purchase orders, billing documents, products, journal entries. OAuth 2.0 client_credentials via BTP Communication Arrangement.

Connectors

SAP S/4HANA Cloud to MCP — Drive SAP S/4HANA Cloud from any AI Agent

Drive SAP S/4HANA Cloud Public Edition from any AI agent: business partners, customers, suppliers, sales orders, purchase orders, billing documents, products, journal entries. OAuth 2.0 client_credentials via BTP Communication Arrangement.

Connectors

How to Connect Baserow to Claude — via MCP

Read Baserow tables, fields, and rows from Baserow Cloud or a self-hosted instance. 4 generic read-only tools using database-token authentication.

OJ
Connectors

How to Connect Odoo 14-18 (JSON-RPC) to Claude — via MCP

Odoo ERP 14 to 18 over the classic JSON-RPC endpoint: search, read, create and update any model, plus partners, sales orders, invoices and products. For Odoo Online, Odoo.sh and self-hosted Odoo older than 19 (works on 19 too). API key + user id.