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

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

SAP S/4HANA Cloud + Meta Muse

Ask Muse 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 Muse

• "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 Muse 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 Muse

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.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the SAP S/4HANA Cloud tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

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 Muse to show the filter it used and correct the field name.
• Answers are slow or cut off on big lists. Ask for fewer rows; Muse passes that as top.

FAQ

Can Muse 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.

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 Muse. When Muse uses a tool, AnythingMCP calls S/4HANA and passes the result to Muse, 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.

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini