ConnectionWorks with ALTARACRM

Salesforce with ALTARA and your AI

Salesforce is on ALTARA's list of CRMs, and the ALTARA team connects it on request, starting with read access. Until then, your pipeline lives in the ALTARA CRM, with nothing to set up. Salesforce's own hosted MCP servers let your own AI read the same records, so ALTARA and your assistant work from one pipeline.

ALTARAConnected on request
ALTARAafter your yes
SalesforceCRM
MCPread-only first
Your AIClaude, ChatGPT, Claude Code, Codex, Cursor

How ALTARA works with Salesforce

ALTARA works in one pipeline per company, shared by the whole team, and each seller has their own chat with it. It starts on the ALTARA CRM. When your company runs on Salesforce, the connection goes like this:

  1. Tell the ALTARA team you use Salesforce.
  2. The team books a 20-minute call.
  3. You grant read access only. Write access comes only when it is needed.
  4. Once an admin confirms, the team moves your accounts from the ALTARA CRM into Salesforce.

Whatever CRM holds the pipeline, ALTARA never writes to it without your yes, and every change is recorded. On the call, ask the team what ALTARA will read and change in your org.

Messages to send ALTARA:

  • "What's my plan for the week?"
  • "Tell me about Summit Ag Supply before the meeting."
  • "Which leads are in Proposal?"

Connect it to your AI

Salesforce Hosted MCP Servers are generally available since April 2026 for Enterprise Edition orgs and above, for customers with Flex Credits; Salesforce says server usage may be billed. Your AI acts as the signed-in user, so field-level security, object permissions and sharing rules apply. Servers are off by default: an admin turns each one on in Setup > MCP Servers (under API Catalog), which takes up to 2 minutes. Each client needs an External Client App (Connected Apps are not supported) with the mcp_api and refresh_token scopes and JWT-based access tokens; a new app can take up to 30 minutes to work. Sandbox and scratch orgs use /v1/sandbox/ in the URL.

  1. Ask your admin for an External Client App with callback https://claude.ai/api/mcp/auth_callback and its consumer key.
  2. Open Customize > Connectors, select Add > Add custom connector and paste the server URL.
  3. Under OAuth client, choose Use your own OAuth client and paste the consumer key.
  4. Select Connect and sign in to Salesforce. On Team and Enterprise, an Owner adds it in Organization settings > Connectors.

Start read-only

Activate only platform/sobject-reads first: it describes objects, runs SOQL and SOSL and reads related records, but cannot create, update or delete. Keep SObject Deletes and SObject All off. Salesforce also suggests a permission set on the External Client App and a refresh token valid 30 days or less. To revoke access, remove the connector in your AI tool; with single logout turned on, ending your Salesforce session ends the MCP session too.

Prompts to try

Pipeline snapshot
Using Salesforce, list my open opportunities closing this quarter: name, account, stage, amount, close date and last activity date. Flag any with no activity in 14 days. Read only.
Account brief
Find everything about [account] in Salesforce: contacts with titles, open opportunities, recent tasks and notes, and cases opened in the last 30 days. Summarize it in eight lines for a meeting tomorrow.
Stale stages
Find opportunities that have been in the same stage for more than 30 days. Group them by owner and give the last activity on each.
Prepare the ALTARA call
Describe the Opportunity object in my org: the stages in use, the record types and the custom fields that have values. Return a short list I can share before connecting a new tool.

If it does not work

  • Sign-in works but no tools appear: an admin turns the server on in Setup > MCP Servers.
  • Authorization fails right after setup: a new External Client App can take up to 30 minutes to work.
  • Redirect error: the callback URL in the External Client App must match your client's exactly.
  • Your org blocks login.salesforce.com or test.salesforce.com: use the My Domain server URL format from Salesforce's guide.
  • Query timeouts: ask for a WHERE clause and a LIMIT, and filter on indexed fields.

Sources

  1. ALTARA help center: Integrations, read on November 20, 2026
  2. ALTARA help center: Pipeline and CRM, read on November 20, 2026
  3. ALTARA help center: The agent, read on November 20, 2026
  4. Salesforce Developers: Hosted MCP Servers, Get Started, read on November 20, 2026
  5. Salesforce Developers Blog: Salesforce Hosted MCP Servers Are Now Generally Available, read on November 20, 2026
  6. Salesforce Developers: Activate MCP Servers, read on November 20, 2026
  7. Salesforce Developers: Create an External Client App, read on November 20, 2026
  8. Salesforce Developers: Connecting an MCP Client, read on November 20, 2026
  9. Salesforce Developers: Standard MCP Servers Reference, read on November 20, 2026
  10. Salesforce Developers: SObject Reads MCP Server, read on November 20, 2026
  11. Salesforce Developers: Configure Claude, read on November 20, 2026
  12. Salesforce Developers: Configure ChatGPT, read on November 20, 2026
  13. Claude Help Center: Get started with custom connectors using remote MCP, read on November 20, 2026
  14. OpenAI Help Center: Connecting custom MCP servers in ChatGPT, read on November 20, 2026
  15. Claude Code: Connect Claude Code to tools via MCP, read on November 20, 2026
  16. OpenAI: Codex Model Context Protocol, read on November 20, 2026
  17. Cursor: Model Context Protocol, read on November 20, 2026

Put it to work with ALTARA