Two paths to MCP on Salesforce.
The platform decides which one ages well.
Why the platform path tends to age better
Not about specific use cases — about what each path inherits from the runtime underneath it. Eight axes where Apex and Flow exposed through Hosted MCP get something for free that a self-hosted REST-wrapping MCP has to build, monitor, and own forever.
Where the broader MCP tooling layer is heading
The MCP server-generation layer just consolidated. Worth framing where the Salesforce-hosted path sits inside that picture.
Where each path is materially stronger
No either-or. A mature system almost certainly runs both, with the split below.
Three concrete patterns, lowest risk first
What we want to learn, and the questions that get us there
Grouped by goal. Each goal lists the open questions; we use these to drive the conversation, not to interrogate.
Likely questions about the platform — with documented answers
Each answer is sourced directly from Salesforce documentation or developer blog. Use as a reference; share the source links if asked.
Ask anything else
Grounded in the same Salesforce documentation and MCP landscape research. Useful live in the call for anything not covered above.