Salesforce MCP and the Yalc Framework
The right MCP when the team already runs Salesforce. For greenfield Yalc setups, HubSpot or Notion is dramatically simpler. Salesforce's complexity is justified only by enterprise scale.
Add Salesforce to Claude Code in one command
claude mcp add salesforce --env SF_USERNAME=user@org.com --env SF_PASSWORD=xxx --env SF_SECURITY_TOKEN=xxx --env SF_INSTANCE_URL=https://yourorg.my.salesforce.com -- npx -y @smn2gnt/mcp-salesforce
Salesforce auth is meaningfully more complex than HubSpot. The simplest path uses username + password + security token (get the token from your Salesforce profile settings). For production deployments, set up an OAuth Connected App and use refresh-token auth. Multiple community MCP packages exist; check maintenance status before committing.
Salesforce, plainly
Community Salesforce MCP servers expose Salesforce objects (Lead, Contact, Account, Opportunity, Case, custom objects) via SOQL queries and standard CRUD operations. Auth setup is the friction: Salesforce's identity model is enterprise-grade, with username + password + security token at minimum, or OAuth Connected Apps for production.
For Yalc operators on Salesforce, the MCP unlocks pipeline reads and writes from Claude Code. Where HubSpot's MCP is plug-and-play, Salesforce's setup takes a couple of hours. Once set up, the surface is comparable: read pipeline state, create leads, update opportunities, log activities.
Position in the GTM operating system
The Salesforce MCP sits at the **route** node when the team is on Salesforce. Most Yalc CRM workflows route through here, with Notion as the workspace layer for briefs and content.
Salesforce's strength is custom objects, complex pipeline stages, and enterprise reporting. The MCP exposes all of that, but the cost is upfront setup work. Don't migrate to Salesforce just to use this MCP; use it because you're already on Salesforce.
Deploying the Salesforce MCP inside Yalc workflows
Workflow position
The CRM layer when Salesforce is the system of record. Yalc reads pipeline, writes records, runs SOQL for ad-hoc queries, and logs activities to the timeline.
Prompt patterns
Copy paste prompts for Claude Code that invoke the Salesforce MCP.
Chaining recommendations
Anti patterns to avoid
Compatibility
Multiple community MCP packages support Salesforce. Coverage varies; verify the specific packages cover the objects and operations your workflows need. Salesforce's API has rate limits per Edition (500-100k+ calls per 24 hours).
Pros, cons, who it's for
Pros
- SOQL exposes the full power of Salesforce reporting from Claude.
- Standard objects (Lead, Contact, Account, Opportunity, Case) covered out of the box.
- Custom objects accessible via the same patterns.
- Multiple maintainers means the ecosystem isn't dependent on one vendor.
- When the team is already on Salesforce, this is the right path.
Cons
- Auth setup is the most complex of any CRM MCP. Plan a couple of hours.
- Salesforce's API rate limits scale with the Edition. Cheaper Editions throttle harder.
- Multiple community MCPs with varying maintenance. Verify before committing.
- SOQL syntax is non-trivial. Yalc workflows need SOQL-aware prompt patterns.
Who it's for
- Enterprise GTM teams already running Salesforce
- Operators who need Salesforce reporting summarized into natural language
- Sales engineering managing complex pipelines with custom objects
The Salesforce ecosystem inside Yalc
MCPs to consider instead
Frequently asked
How do I generate a Salesforce security token?
In Salesforce, go to your profile settings, find "Reset My Security Token", and click reset. Salesforce emails you the new token. Use it alongside your username and password for the MCP.
Can I use OAuth instead of username + password?
Yes. Set up a Connected App in Salesforce, configure OAuth flow with refresh tokens, and use the resulting refresh token in the MCP env. More complex but production-grade.
Will the MCP hit Salesforce's API limits?
Depends on your Edition. Essentials Edition has the lowest limit (around 5k calls per day per user). Enterprise and Unlimited Editions have much higher limits. Yalc workflows should batch reads when possible.
Can the MCP run reports?
Most community MCPs support report metadata reads, but actual report execution requires a separate report endpoint. SOQL is the more reliable path for Yalc workflows.
How is custom object access handled?
Custom objects work the same as standard objects in SOQL (just use the API name, ending in __c). The MCP doesn't need special config for custom objects.
Is the MCP suitable for high-volume writes?
For batch writes (1000+ records), use the Salesforce Bulk API directly, not the MCP. The MCP is for ad-hoc reads and writes during Claude conversations, not ETL pipelines.
Install the Salesforce MCP
Drop it into Claude Code and orchestrate from your next Yalc prompt.
claude mcp add salesforce --env SF_USERNAME=user@org.com --env SF_PASSWORD=xxx --env SF_SECURITY_TOKEN=xxx --env SF_INSTANCE_URL=https://yourorg.my.salesforce.com -- npx -y @smn2gnt/mcp-salesforce