How to Connect SAP S/4HANA (OData) to Meta Muse via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → SAP S/4HANA (OData), paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

SAP S/4HANA OData + Meta Muse

Let your AI read SAP S/4HANA on-premise or Private Cloud through its OData services: find services in the SAP Gateway catalog, read their fields with SAP's labels, and query journal entries, billing documents, sales orders, business partners, stock and products. Read-only, with a technical SAP user.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

SAP_ODATA_BASE_URL, SAP_CLIENT, SAP_LANGUAGE, SAP_ODATA_USER, SAP_ODATA_PASSWORD

Step 1 — Get credentials

1. With transaction SU01, create a technical user of type System (not Dialog) in the client the AI should read, and give it a productive password.
2. Give it a role (PFCG) with S_SERVICE for the OData services the AI may use and display-only business authorizations (activity 03). To let the AI browse the catalog, also allow the V2 catalog service /IWFND/CATALOGSERVICE and the V4 service catalog.
3. Make sure the services are active: /IWFND/MAINT_SERVICE for V2, /IWFND/V4_ADMIN for V4. The ready tools use SAP's released APIs API_JOURNALENTRYITEMBASIC_SRV, API_BILLING_DOCUMENT_SRV, API_SALES_ORDER_SRV, API_BUSINESS_PARTNER, API_MATERIAL_STOCK_SRV and API_PRODUCT_SRV.
4. Set SAP_ODATA_BASE_URL to the Gateway host with its HTTPS port and no path, e.g. https://s4.example.com:44300. Put the three-digit client into SAP_CLIENT (e.g. 100), the logon language into SAP_LANGUAGE (e.g. EN; field labels come back in this language), and the technical user's name and password into SAP_ODATA_USER and SAP_ODATA_PASSWORD.
5. Install the connector. There is no Authorize with Provider step: the connector signs in with Basic auth as the technical user and sends the client and language with every call.
6. Call s4_guide first (it costs nothing and does not reach SAP), then s4_list_services with a business term such as billing to check that the user reaches the catalog.

Network: the Gateway's HTTPS port is usually reachable only inside the company network. Self-host AnythingMCP in that network or connect it through a VPN, and add the Gateway host to SSRF_ALLOWED_HOSTS, because AnythingMCP refuses private addresses otherwise. AnythingMCP Cloud works only if the Gateway is reachable from the internet.

How the AI finds the data: s4_list_services searches SAP's catalog (V2 and V4) for a business term, s4_describe_service lists a service's entity sets and flags the analytical and parameterised ones, s4_describe_entity gives each field with its SAP label, the currency or unit field of every amount and the filters a set requires, and s4_query and s4_get_entity read rows. Field names are checked against the service's $metadata before the call goes out. For the common cases, s4_journal_entry_items, s4_billing_documents, s4_sales_orders, s4_business_partners, s4_material_stock and s4_products call the released APIs directly with filter, select, orderby, top and skip. The catalog tools also work on ECC or BW with SAP Gateway; the ready tools need S/4HANA.

Permissions and read-only setup: all 12 tools only read. SAP checks the technical user's authorizations on every call, so they are the real boundary: give the role display authorizations only, and only for the company codes, sales organizations and plants the AI may see. To narrow it further, list the service paths the AI may call under Allowed services in the connector's OData settings (* works as a wildcard); other services are refused. Single tools can be disabled on the connector page.

SAP API policy: SAP expects third-party integrations to use its published APIs (the API_* services on the SAP Business Accelerator Hub) or services you built yourself. Prefer those over the internal services behind Fiori apps, and set Allowed services to match.

Basic auth or OAuth: the connector installs with Basic auth. If your Gateway is set up for OAuth 2.0, you can switch the connector's authentication to OAuth 2.0 on the connector page.

Limits: a query returns at most 1,000 rows, the ready tools 100 by default (top). For totals, the AI aggregates on analytical services, or filters by company code, sales organization or plant and by a date or fiscal period, instead of paging through everything. Amounts come with their currency and quantities with their unit; decimals come back as strings so they stay exact.

Common errors: 401 means a wrong user or password, or a user that is locked in that client. 403 Forbidden on a service means the technical user lacks the authorization for it (S_SERVICE or the business role), and 404 means the service is not active in this system. A refused private address means the host is missing from SSRF_ALLOWED_HOSTS. If the rows look like demo data, SAP_CLIENT points to the wrong client.

HANA SQL instead: if the AI should read S/4HANA's tables and CDS views directly with SQL, through a read-only database user instead of SAP's application authorizations, use the SAP S/4HANA (HANA SQL) connector. For any other OData V2 or V4 service, see the OData connector type.

The connector does not write to SAP: it posts nothing and does not create or change orders, documents or master data.

Step 2 — Install the adapter

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 OData 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

Example prompts

• "Which OData services in our SAP catalog deal with billing documents, and which of them are released APIs?"
• "Show last month's net billed sales per sales organization from the billing documents, without cancelled documents, with the currency."
• "How much stock of material FG-100 do we have in plant 1000, per storage location?"
• "List the 20 largest journal entry items posted in company code 1000 last month, with G/L account, amount and currency."

FAQ

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