Connect Claude to your Salesforce org. Query any object, update records, create opportunities, and pull reports without writing SOQL or switching between tools.
The Salesforce MCP server gives Claude structured access to your Salesforce CRM through the Model Context Protocol. It translates your natural language requests into Salesforce API calls, letting you query records, update fields, and create new objects without writing SOQL queries or navigating Salesforce's interface.
MCP is an open protocol from Anthropic that standardizes how AI assistants connect to external data sources. The Salesforce MCP server implements this standard to expose your CRM data in a way Claude can read and act on. It authenticates using OAuth 2.0 and respects your existing Salesforce permission model.
This means a sales rep can ask Claude "show me all deals closing this month over $50k" and get the answer from live Salesforce data. An ops lead can say "update the stage on the Acme opportunity to Closed Won" and have it done in seconds. The data stays in Salesforce. Claude just becomes another way to access it.
In Salesforce Setup, go to App Manager and create a new Connected App. Enable OAuth settings and select the scopes you need (typically api, refresh_token, and offline_access). Note your Consumer Key and Consumer Secret.
Install the community Salesforce MCP server:
npm install -g @anthropic/mcp-server-salesforce
Add the Salesforce server to your Claude Desktop configuration:
{
"mcpServers": {
"salesforce": {
"command": "npx",
"args": ["-y", "@anthropic/mcp-server-salesforce"],
"env": {
"SF_INSTANCE_URL": "https://yourorg.my.salesforce.com",
"SF_CLIENT_ID": "your_consumer_key",
"SF_CLIENT_SECRET": "your_consumer_secret",
"SF_USERNAME": "your_username",
"SF_PASSWORD": "your_password",
"SF_SECURITY_TOKEN": "your_security_token"
}
}
}
}
For production use, consider using the OAuth 2.0 JWT bearer flow instead of username/password authentication. This is more secure and does not require storing credentials in plain text.
Restart Claude Desktop. Try asking: "Describe the Account object in Salesforce" to confirm the connection is working. Claude should return the field list from your org.
Instead of building Salesforce reports or exporting to a spreadsheet, ask Claude to show your pipeline by stage, rep, or region. Get totals, averages, and breakdowns from live CRM data in the format you need.
Before a sales call, ask Claude to pull everything Salesforce knows about the account: recent activities, open opportunities, support cases, last touchpoints, and key contacts. Get a briefing document in 10 seconds instead of clicking through Salesforce tabs for 10 minutes.
Need to update the owner on 30 leads? Change the stage on stale opportunities? Describe what needs to change and Claude handles the updates, one record at a time, with confirmation before each batch.
Ask Claude to find contacts missing email addresses, leads without a source, or opportunities with no close date. Identify data quality issues across your org without building custom reports or validation rules.
Yes. The MCP server authenticates as your Salesforce user. Any field-level security, sharing rules, and profile restrictions in your org apply exactly as they would in the Salesforce UI.
Yes. Point the SF_INSTANCE_URL to your sandbox URL (e.g., https://yourorg--sandbox.sandbox.my.salesforce.com) and use sandbox credentials. This is recommended for testing before connecting to production.
Yes. Each SOQL query or record update uses one or more Salesforce API calls. Most Enterprise orgs have plenty of headroom, but monitor your API usage in Setup > System Overview if you are on a lower-tier plan.
Absolutely. Claude can query, create, and update any custom object in your org. Just refer to it by its label or API name (e.g., "Project__c") and Claude will work with it like any standard object.
Custom Integration
We build production-grade Salesforce MCP servers with custom object support, advanced SOQL, and workflow automation tailored to your sales process.
Book a Discovery Call