MCP and tools
Connecting Claude to Salesforce or SAP without a catch-all tool
"We connected Claude to Salesforce" usually means one mega-tool and a security exception. Here is how we ship named MCP verbs that survive a CRM of record.
August 10, 2026/2 min read/Claude Certified Engineers
Connecting Claude to Salesforce or SAP is not an integration trophy. It is a contract: which records Claude may read, which it may draft, and which it may never touch without a person. Most demos skip the contract and expose salesforce_request. Claude will use it. Your CRM admin will find out in the audit log.
We build the named-verb version on MCP and Tool Integration work, using the same schema rules as any other system of record.
Verbs that match how revenue teams work
Salesforce-shaped examples:
get_account(requiredaccount_id, 18-character, starts with001)search_accounts(two or three filters you actually index)draft_opportunity(writes a review record, not the live object)create_opportunity(requireschange_ticket_id)log_call(never invents an account)
SAP-shaped examples follow the same pattern: get by id, search with real filters, draft, post with a human token. Not call_bapi with a freeform payload.
Ids, not names
If the field is account_id, the description must say it is not a name and not a URL. If you accept both, you will get names, and the resolver will hit the wrong record. That is how you brief the wrong customer.
Enums for stage, currency, and ticket priority beat free text. The API will 400 on "in progress" vs "In Progress". The schema should not pretend both are fine.
Pair this with a security review and a review queue for posts that move money or master data. That is the integration that clears enterprise buyers, not the weekend connector.
Questions
- How should Claude talk to Salesforce?
- Through a small set of MCP tools with required Salesforce ids, enums for stage and currency, and a server that validates before it calls the API. Not through a generic REST wrapper.
- Is SAP different?
- The verbs change. The rules do not. Named jobs, constrained accounts, audit logs, and no catch-all RFC or IDoc blaster.
- Can Claude create opportunities in production on day one?
- Draft plus review, then create. Direct create belongs behind an approval id a human minted.