Salesforce MCP server
Inspect Salesforce records and make targeted Account or Opportunity changes through Arc0’s tools. The connected user’s object and field permissions continue to apply. Connect through Arc0 to use the actions your identity is allowed to call.
Working with Salesforce
A request to update a forecast should start with the schema and current records. salesforce.describe_object shows field API names, types, and write permissions. Use that information to build a salesforce.query request that selects only relevant fields, includes Id, and limits the result to at most 200 rows. Stable ordering helps when continuing within the supported offset window.
When the user names a customer rather than a record ID, salesforce.search provides a bounded text search within one object. Follow it with salesforce.get_record for the current values. Search results can lag recent changes, so they are a discovery aid rather than proof that a write failed.
For an approved update, salesforce.update_record changes the supported fields on an Account or Opportunity. salesforce.create_record adds one of those record types. Existing Salesforce automation can notify people when either operation runs. Read the resulting record to verify the change, especially after a lost response. These tools do not expose unrestricted object writes, message sending, or consent changes.
Official MCP reference: Salesforce documentation.
Agent workflows for Salesforce.
Inspect the record schema
Use salesforce.describe_object to identify field API names and write permissions before proposing changes.
Review a bounded pipeline slice
Use salesforce.query for a flat SOQL SELECT with an explicit limit and stable ordering.
Find a named record
Use salesforce.search to discover a record, then salesforce.get_record for its current selected fields.
Maintain an opportunity
Use salesforce.create_record or salesforce.update_record for supported Account and Opportunity fields after reviewing the target.
6 Salesforce actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
4Look things up, subject to your permissions.
- salesforce.queryQuery
Use when reading CRM rows with flat SOQL SELECT including Id and LIMIT 1..200. Use a stable ORDER BY Id and nextOffset to page within the 2,000-offset window; results can change between calls. No subqueries, aggregates, locking or DML.
- salesforce.searchSearch
Use when discovering records using a bounded SOSL text search in one object. Results may lag writes; read by ID to verify. recordId restricts returned results to one consenting subject for live acceptance.
- salesforce.describe_objectDescribe object
Use when discovering an object’s field API names, types, nullability and write permissions before querying or editing records. Names describe schema, not people.
- salesforce.get_recordGet record
Use when reading a known Salesforce record by object API name and ID. Select only fields needed; Id is always included. Use query or search to discover IDs.
write
2Create and change things. Allow, or ask the user first.
- salesforce.create_recordCreate record
Use when creating an Account or Opportunity with curated CRM fields. Org automation may notify configured recipients. Not for sending messages or changing consent. No idempotency: read back before retrying an unknown outcome.
- salesforce.update_recordUpdate record
Use when editing curated Account or Opportunity fields by ID. Org automation may notify configured recipients. Not for consent changes. Success is 204 with no body; read back before retrying an unknown outcome.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to Salesforce.
Connect the intended Salesforce account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- salesforce.create_record: require approval
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Salesforce connects.
Connect Salesforce using OAuth. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- OAuth
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Salesforce with your AI client.
Sign in to Arc0 and connect Salesforce in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Salesforce with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingSalesforce with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSalesforce with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingSalesforce with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSalesforce with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSalesforce with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
Salesforce and Arc0, answered.
Is there an official Salesforce MCP server, and how does Arc0 differ?
Yes. Salesforce documents hosted MCP servers. Arc0’s current Salesforce tools use REST with bounded queries and curated Account and Opportunity writes, rather than exposing the full hosted-server feature set.
Which permissions does Arc0 need for Salesforce?
OAuth requests api, openid and refresh_token. The api grant permits API operations within the user’s existing object and field rights; openid binds identity and refresh_token enables continued access. The connection uses the organization’s configured Salesforce domain.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.
How are credentials stored, refreshed and revoked?
Credentials are encrypted in Arc0’s vault. Arc0 stores OAuth credentials and supports rotating refresh tokens. Disconnect attempts to revoke this connection’s refresh-token grant and related access tokens. If remote cleanup fails, local access still ends; use Salesforce’s OAuth usage controls to verify or remove the remaining grant.
What happens with rate limits or errors?
Salesforce API allowances and organization policy still apply. Arc0 distinguishes authentication, permission, and rate-limit failures. A timed-out create or update may have run; read the record before issuing another write.
What is the availability of these Salesforce tools?
These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.
Plug Salesforce into your agent.
Salesforce MCP server: 6 actions including query, search, describe object. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Salesforce and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Salesforce.