Salesforce Doesn't Have an Official MCP Server (Yet)

Worth stating plainly: Salesforce has not shipped an official, production-grade MCP server comparable to HubSpot's, as of this writing. Coverage of the CRM-and-MCP space specifically notes that Salesforce's broader platform has remained more closed to external builders than competitors, with commentary suggesting pressure will grow for Salesforce to open up as MCP adoption spreads across the CRM category.

The Notable Exception: Slack

This is a genuinely interesting nuance: Salesforce owns Slack, and Slack's own MCP server is real and official, having replaced Anthropic's earlier reference implementation. So Salesforce-the-parent-company does have official MCP presence — just through its Slack acquisition, not through Salesforce's core CRM platform itself.

If You Need Salesforce Data in an AI Workflow Today

Without an official server, the realistic paths are: building a thin custom MCP wrapper around Salesforce's existing REST/SOQL APIs yourself (the same general pattern this site documents for wrapping any production API), or going through a general-purpose connector like Zapier's official MCP server, which already supports Salesforce as one of its 8,000+ connected apps without you needing to build anything Salesforce-specific.

Why This Gap Is Notable

HubSpot moving first and Salesforce not yet following is a real, observable data point about how differently CRM vendors are approaching AI-agent access to their platforms — worth revisiting periodically rather than assuming the current state is permanent, given how quickly this specific landscape (Zapier, Stripe, Shopify, Atlassian, HubSpot all shipping official servers within roughly the same year) has been moving.