CRM
Salesforce MCP server
Connect Salesforce to Claude, ChatGPT, Cursor, and any MCP-compatible AI agent. Live access to your Contacts, Accounts, and the rest of the timeline — through one unified profile per customer.
A direct Salesforce MCP shows your agent Salesforce. Pathbound shows your agent the customer — across Salesforce, Gmail, Intercom, your tracker, Apollo, Calendly, and the rest of your stack — through one unified profile served over the Model Context Protocol.
Gmail threads, Intercom conversations, website page views, Apollo enrichment, Calendly meetings — all stitched onto one timeline per contact. Your agent stops asking "who is this?" on every other tool.
Same person as [email protected] in Salesforce, [email protected] in Gmail, "Jane R." in Intercom — Pathbound resolves to one entity. A direct connector only knows its own IDs.
Token-efficient response shapes (count_only, fields=summary), server-side aggregation, batch tools. Agents get the answer, not raw SOQL dumps. Stays inside the context window.
Salesforce Contact + Account fields land on the same unified profile as the rest of your stack. Most-recent-wins merging keeps fields fresh; you can see which source each field came from.
Connect Salesforce once. Your agent gets identity-resolved profiles and the full activity timeline through one MCP server, alongside Gmail, Intercom, your tracker, and your other sources.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
}…plus more — full MCP tool list, across contacts, companies, events, and conversations.
OAuth one connector. Drop a snippet into your MCP client. Ask a question.
Create an account at pathbound.ai. Free during public alpha.
In the dashboard, go to Integrations → Salesforce → Connect. OAuth via Salesforce's standard OAuth flow in one click; sync runs every 60 minutes and pulls Contacts and Accounts (incremental via LastModifiedDate).
Drop the snippet below into your Claude Desktop config (or in Claude.ai web: Settings → Connected Apps → Add custom MCP → enter https://mcp.pathbound.ai/mcp). The same URL works for ChatGPT, Cursor, Cline, and any MCP client that supports OAuth.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
}Ask the agent: “How many contacts do I have from Salesforce?” The agent calls list_contacts via MCP and returns the count.
Pathbound is an independent platform. We connect to Salesforce via the standard OAuth flow and expose your data through one Model Context Protocol server alongside your other sources. Not affiliated with Salesforce.
REST and SOQL are for backends and scheduled jobs. MCP is for AI agents — it’s the protocol Claude, ChatGPT, and Cursor speak. Pathbound’s MCP also unifies Salesforce with Gmail, Intercom, your website tracker, and other sources into one profile per contact, so the agent doesn’t glue 6 APIs together itself.
Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue — any client that supports the Model Context Protocol with OAuth.
Not in v1. The Salesforce integration is read-only today — Contacts and Accounts flow into the unified profile but updates stay in Pathbound. Write-back is on the roadmap.
Contact and Account today, on a 60-minute incremental schedule using LastModifiedDate. Standard fields (email, name, title, address, industry, website, employees, revenue) plus a few common ones. Custom-field mapping will land alongside the broader mapping UI.
Production orgs (login.salesforce.com) for v1. Sandbox / scratch-org support is on the roadmap.
OAuth 2.0 end to end. You authorize Pathbound against your Salesforce org once; tokens are stored encrypted per tenant and refreshed automatically. Revoke anytime from Salesforce → Connected Apps or from Pathbound Settings.
Same MCP server, same tools — just connect a different source. See the integrations directory.
Sign up. Drop in the tracker snippet. Connect one CRM. Point your MCP client at
mcp.pathbound.ai/mcp.