How to Connect SAP Sales Cloud and Service Cloud (C4C) to Claude via MCP

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

SAP Sales Cloud and Service Cloud (C4C) + Claude

Read SAP Sales Cloud and Service Cloud (Cloud for Customer, C4C) through its OData API: accounts, contacts, leads, opportunities, sales quotes, service requests, products and employees, plus generic OData tools for every other entity set. Basic authentication, read-only.

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_C4C_HOST, SAP_C4C_USER, SAP_C4C_PASSWORD

Step 1 — Get credentials

Setting up takes about 10 minutes. You need an SAP Sales Cloud or Service Cloud (Cloud for Customer, C4C) tenant and a user with Basic authentication, ideally a technical integration user.

1. Recommended: a technical integration user. In C4C go to Administrator > Integration > Communication Systems and create a communication system. Then, under Communication Arrangements, create one with the scenario OData Services for Business Objects and authentication User ID and Password, and select the OData services (at least c4codataapi). The arrangement shows the user id; set its password there.
2. Alternatively, use a business user with Basic authentication whose business roles grant read access to the work centers the AI should see.
3. Set SAP_C4C_HOST to the tenant host, e.g. my123456.crm.ondemand.com, without https:// or a path, and fill in SAP_C4C_USER and SAP_C4C_PASSWORD.
4. Install the connector and run sap_c4c_list_accounts with top 1 to check the access.

Read-only: the connector reads the standard OData V2 API of the tenant, https://<tenant>.crm.ondemand.com/sap/c4c/odata/v1/c4codataapi, and never writes. SAP checks the user's authorizations on every call, so the AI sees only what the communication arrangement or the user's business roles allow.

What it reads: corporate accounts (customers and prospects) with role, status, ABC classification, industry, owner, main address, phone and e-mail; contact persons with their account; leads with life cycle status, qualification level, source and owner; opportunities with sales phase, status, probability, expected value and expected close date, for the sales pipeline; sales quotes with net and gross amounts, valid-to date and the opportunity they belong to; service requests (tickets) with customer, contact, status, priority, processor, service category, due dates and SLA times, for the service backlog; products; and employees, to turn owner and processor ids into names. sap_c4c_guide explains the workflow and costs no API call.

Every other entity set: the generic OData tools reach the rest of the service. sap_c4c_list_services shows where the service lives, sap_c4c_describe_service lists all entity sets (a large answer, cached for a day), sap_c4c_describe_entity shows the fields with their labels, sap_c4c_query reads rows and sap_c4c_get_entity reads one record by its ObjectID.

Queries: filters support eq, ne, ge, le, gt, lt, and, startswith and endswith; or works only on one field. Dates are written as datetimeoffset'2026-01-01T00:00:00Z', and EntityLastChangedOn finds what changed since a moment. search is SAP's free-text search. Records are keyed by ObjectID; business ids such as AccountID or ID are separate fields. The AI asks only for the fields it needs with select.

Limits: at most 1000 rows per page (top, then skip); the lists return the total count. expand is slow on large sets.

Common errors: 401 means a wrong user or password, or a locked user. 403 means the communication arrangement or the user's business roles do not cover this business object. 404 on every call usually means a wrong SAP_C4C_HOST. A 400 names a field or filter the API does not accept; sap_c4c_describe_entity shows the right field names.

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

Recommended path: works on claude.ai web without editing any config file.

1. In Claude, open Customize → Connectors.
2. Click +, then Add custom connector.
3. Enter a name, e.g. SAP Sales Cloud and Service Cloud (C4C), and the remote MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Add.
4. Click Connect and sign in to AnythingMCP (OAuth) to allow access.

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

Available tools

Example prompts

• "Show the open opportunities expected to close this quarter, with sales phase, probability and expected value."
• "Find the account Example Industries and list its contacts and its open service requests."
• "Which high-priority service requests are past their due date, and who is processing them?"
• "List the leads created in the last 7 days by source and qualification level."
• "Which sales quotes expire this month, and which opportunities do they belong to?"

FAQ

Does it work with Claude Code as well as Claude Desktop? Yes, point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.

Next steps

• Connector landing page
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse
• Connect to Microsoft Copilot