BusinessMCP
S

Salesforce

Official

Salesforce · CRM & Sales

12.4k installs

Connect in 1 click

Connect Salesforce once and let your Sales threads query pipeline state, update opportunities, and log outreach activity automatically. SOQL complexity is hidden behind natural language.

$ npx mcphosting-cli add salesforce

Just say it in a thread

No configs, no docs. Once connected, these are the kinds of messages your agents act on.

"Show me all leads created this week from the webinar campaign, sorted by company size."

"Which of my leads haven't been touched in 14 days? I want to log a follow-up call against each one."

"Move the Acme Corp opportunity to Negotiation and bump the amount to $85,000."

"Log yesterday's discovery call with Northwind Traders against their record, with my notes attached."

"Pull every lead with the title 'VP of Marketing' at companies over 200 employees."

"Update the close date on the Globex renewal opportunity to the end of next quarter."

"After I send this recap email, log it to the contact's activity history."

"Filter my leads to the enterprise segment that came in through the pricing page."

"Mark the stalled Initech deal as Closed Lost and log the reason as a note."

Agent-callable tools

sfdc.query_leads

Query and filter leads

sfdc.update_opportunity

Update stage and amount

sfdc.log_activity

Log calls and emails to records

Your data stays yours

Credentials live in your vault. We route requests — we never store, log, or train on your data.

Works with every AI

Connect once — portable across Claude, GPT, Gemini, and every local agent you run.

Frequently asked questions

Do I need to know SOQL to use this?

No. You ask in plain English — "leads created this week from the webinar campaign" — and the server translates it into the underlying query. Analysts who do know SOQL can be more precise, but it is never required.

Why does the agent get 'insufficient access' errors?

The connection runs as a Salesforce user, and that user's profile, permission sets, and sharing rules govern everything the agent can see or change. If a human logged in as that user could not edit the record, neither can the agent. Fix it in Salesforce by adjusting the connected user's object and field permissions.

Why are some fields missing from query results?

Field-level security hides any field the connected user cannot read, and custom fields must be referenced by an accessible API name. Check field accessibility on the connected user's profile before assuming data is absent.

Can it update records without my approval?

Updates only happen when you explicitly ask for them — the agent never mutates pipeline data on its own. For extra safety, connect a sandbox org first, or scope the connected user to read-mostly permissions and widen them once you trust the workflow.

Does it work against a sandbox org?

Yes — connect a sandbox user and every tool behaves identically, which is the recommended way to trial opportunity updates and activity logging before touching production.

Give your AI team the Salesforce skill

Free forever plan, no credit card. Connected and working in under five minutes.

Connect Salesforce free