Salesforce MCP Connectivity
Give AI the Salesforce context it needs.
Let agents work with live Salesforce context through scoped, read-only MCP tools. Control the objects and fields they can query, preserve the source access boundary, and review results with their provenance.
Business question
Counts, lists, breakdowns, rankings
Scoped MCP tools
Verified identity and explicit read policies
Live source result
Records, source links, request provenance
Policies apply to the query, not just the displayed fields. Source permissions remain part of every read.
Ask a useful business question
Query account counts, case breakdowns, opportunity lists, or accounts ranked by case volume. Turn a question into a bounded, structured source query.
See where the answer came from
Review source links, the effective Salesforce identity, a timestamp, and policy provenance. Distinguish bounded record previews from aggregate results.
Keep the read boundary explicit
Set object and field allowlists and a row limit. Restrictions cover filtering, sorting, grouping, and aggregate metrics as well as returned columns.
The workflow
A question. A policy. A verifiable result.
Keep model planning separate from the data-access decision. Typed tools and read policies determine which requests can reach Salesforce.
Connect the source identity
Sign in with Salesforce OAuth and establish the user and org. Bind the request to that identity rather than letting a tool argument choose credentials.
Set the read policy
Choose allowed objects and fields and a bounded result size. Apply the policy alongside Salesforce permissions and record sharing.
Plan and execute
Use permitted schema to build a typed plan. Execute approved read tools for schema discovery, records, counts, and supported account/case rankings.
Inspect the result
Review the result and its source references, identity, timestamp, and trace details. Unsupported questions or denied access return an explicit clarification or error.
Technical fit
Built around your operating environment.
Connect the product to your infrastructure, access requirements, and operational responsibilities.
- Identity boundary
- Define the host and operator responsible for the connection. Keep credential selection outside model-controlled arguments and review the identity boundary for your deployment.
- Query controls
- Set object and field policies with a bounded row cap. Policy changes discard stale results, and Salesforce applies live source permissions and sharing.
- Read-only tools
- The query workflow separates context retrieval from actions. Raw SOQL, arbitrary code, general joins, and source writes are outside its tool contract.
- Model data boundary
- The planner receives the question and permitted schema. Returned Salesforce record rows are assembled by the host rather than sent to the planning model.
Follow configuration, operation, and troubleshooting guides for your environment.
Explore the documentationQuestions worth asking.
Understand the scope before deciding how this fits your organisation.
What can the Salesforce MCP tools do?
The read workflow includes schema search and description, bounded record queries, single-record retrieval, and supported account/case rankings. Typed plans and read policies constrain how those tools can be used.
Can an agent update Salesforce?
This query workflow is read-only. It gives agents controlled context without granting record mutation tools. A workflow that changes Salesforce needs a separate action and approval design.
Can agents access archived history too?
Live Salesforce queries and archive retrieval are distinct data paths. Include the archive source, relationships, and archive access policy in the solution design rather than assuming live-source permissions carry over.
Does MCP automatically enforce Salesforce permissions?
The protocol alone does not enforce business permissions. Vivly binds the source identity and applies explicit object and field policies; Salesforce also applies source permissions and record sharing to live reads.
See it with your workflow in mind.
Walk through your Salesforce environment, the records that matter, and the outcome you need. See how the product fits your team’s day-to-day work.