CRM
Salesforce MCP connector
Salesforce brings 154 AI tools to Elaichi, covering accounts, contacts, leads and opportunities. Connect the org once, then Claude, ChatGPT, Cursor or any MCP client works inside the profile and sharing rules each person already has.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Salesforce to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Salesforce once
-
Open Connections, choose Add connection, and pick Salesforce.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Salesforce. Salesforce's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Salesforce to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Salesforce to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Salesforce to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Salesforce to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Salesforce through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Ask pipeline questions inside your own visibility
The profiles and sharing rules you spent years tuning still apply under every question. Two reps asking the same thing get different answers, correctly.
-
Sales Ops
Pull a report without building one
The awkward one-off questions that never justified their own report. Ask, get the answer, move on.
-
Sales
Turn a conversation into follow-ups
Tasks, contacts and meetings written back after a call, so the CRM reflects the week without anyone doing data entry on a Friday.
-
Support
Give Support case context, not the pipeline
Cases and contacts, and no opportunities. Support sees the customer and their history, and the pipeline stays where it belongs.
-
Sales Ops
Make merges a deliberate decision
Merging two accounts cannot be stepped back the way a wrong field value can, and bulk deletion does not ask twice. Both belong to the team that owns the data, or to nobody.
-
Administrators
Keep org configuration off limits
Salesforce admin controls reach how the org works, not just what is in it. Keep them with the people who administer it and away from everyone else.
Try asking
- “Which accounts have no contact activity this quarter?”
- “Create a contact on the Northwind Traders account.”
- “List opportunities closing this month by owner.”
AI tools
Salesforce tools for your AI agents
154 tools are ready to call through Elaichi's MCP endpoint the moment you connect Salesforce, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Salesforce gets you
6 screens from the product, each doing one job for your Salesforce account.
The agent
Ask about accounts, get answers back.
Plain language questions run against live Salesforce accounts, contacts and opportunities.
- accounts
- contacts
- leads
- opportunities
Ask Elaichi to work across your apps.
Which accounts have no contact activity this quarter?
Create a contact on the Northwind Traders account.
List opportunities closing this month by owner.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Every client reaches Salesforce over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
154 Salesforce tools are ready to call.
Accounts, contacts, leads and opportunities are covered without writing custom code.
- List all Salesforce accounts
- Get single Salesforce account by ID
- Update a Salesforce account by ID
- Delete a Salesforce account by ID
Toolboxes
Each team gets its own Salesforce toolbox.
Curate one toolbox per team so Sales, Support and Finance see different tools.
- Sales
- Sales Ops
- Marketing
- Customer Success
Shared connections
Teammates use Salesforce without seeing credentials.
Each connection shows who connected it and which teams and members it reaches.
- Sales EMEA
- Sales AMER
- Marketing
- Customer Success
Audit log
Every Salesforce call is written down.
When, who, what happened, type and resource, appended for each account or contact touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts the pipeline digest.
Opportunities are fetched, grouped, drafted by an agent, approved by a person, posted to Salesforce.
Salesforce digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch accounts
Salesforce
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Salesforce
Queued
Collections and dashboards
Salesforce numbers arrive before anyone asks.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Salesforce health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales AMER 27%
Marketing 21%
Customer Success 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Salesforce to Claude?
Two steps. In Elaichi, add Salesforce and sign in, choosing production or sandbox on Salesforce's own login screen. Then in Claude open Customize, then Connectors, press Add, and paste https://api.elaichi.ai/mcp as the MCP server URL. There is no connected app to create and no client secret to store.
Does Salesforce work with ChatGPT and Cursor as well as Claude?
Yes. The same endpoint, https://api.elaichi.ai/mcp, reaches Salesforce from Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. Connect the org once in Elaichi and every client reaches it, each person signed in as themselves.
What can an AI agent actually do with my Salesforce data?
Read and update Salesforce accounts, contacts, leads, opportunities and cases, log tasks, events and emails against a record, run reports on the pipeline, and merge duplicates. The everyday version is asking it to catch a record up after a call, or to tell you what changed on an account this week.
Does an AI agent bypass our Salesforce sharing rules?
No. Every call runs as the person who signed in, so their profile, permission sets and sharing rules decide what comes back, exactly as if they had opened Salesforce themselves. Two colleagues asking the same question get different answers, because they have different access. Elaichi can narrow that further, never widen it.
Can I keep an agent away from our Salesforce setup and configuration?
Yes. The Salesforce org configuration tools, the ones covering custom fields, profiles and page layouts, can be blocked for everyone except your admins. A blocked tool is never advertised to the AI client, so it cannot be invoked by a prompt, however it is worded.
Why does my AI client stop showing the Salesforce tool names?
Past 30 tools most clients switch to a search-and-run pair instead of listing each one, and Salesforce alone brings 154. Nothing is lost, but the client now finds tools by searching, and that search matches words rather than meaning. Short, concrete asks like "update opportunity" or "list open cases" work; a long sentence about your goal does not.
Who can see which Salesforce records an agent touched?
Every Salesforce call lands in Elaichi's append-only audit log: who asked, which tool ran, and the id of the record it touched. Admins can read it, and it can be streamed to your own logging destination. It survives the connection being removed, which is what makes it useful during a review.
Put Salesforce in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.