Salesforce REST MCP integration

The Salesforce REST connection is designed for REST-based, company-context Salesforce CRM access through a self-hosted connection. Serves Salesforce REST access from your own mcp-host infrastructure. That means an assistant uses the permitted live-system context instead of guessing from a document. The result still depends on the freshness of the source system and the permissions granted to the connection.

A useful request makes clear which record is needed for which team. For this connection, a reliable flow is identifying the account, contact or opportunity question, then reviewing the CRM result alongside access and sharing rules. This makes filters and source records easier to inspect than asking for a broad list to be summarised.

tools that create, update or delete records require single-use confirmation; access is bounded by Salesforce permissions and KobiGPT department grants. This is more than a technical detail: an incorrect action in a financial, customer, production or legal record can have real consequences. Reading a result and changing an external system are not the same level of authority.

Before rollout, decide which assistants and departments can see this data. If a result is unexpectedly broad, reduce the access scope; if data is absent, do not let the assistant invent the missing record. The underlying system record and the accountable owner remain the final check for every consequential result.

runs on your own mcp-host with bearer authentication and differs from the hosted Salesforce MCP option in its data path. At setup, use a separate connection identity with least privilege so the accessible data does not exceed the operational need. For OAuth connections review the consent screen; for bearer connections review token scope, storage and ownership with the responsible team.

self-hosted bearer connection and 0.1 Kobi Credits per call. This statement comes from the catalog or tool definition; no extra count is invented for a vendor-managed changing surface. During a pilot, observe real questions, returned records, confirmation steps and unnecessary calls. That evidence makes cost visible and exposes over-broad permissions early.