Compared · salesforce
13 Salesforce MCP servers. Which one to use.
Every Salesforce server we index, with whether its source is still reachable and whether we hold a screening verdict. 1 of 13 have a source repository that is no longer publicly reachable.
Scope: 13 servers, mostly mirrored from the MCP registry as of 2026-08-13. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Salesforce | io.github.wyre-technology | no flag | REVIEW | 95 | docker ghcr.io/wyre-technology/salesforce-mcp:v1.0.2 |
| Cirra AI Salesforce Admin MCP Server | ai.cirra | no flag | REVIEW | 88 | remote endpoint |
| Salesforce | io.github.mindstone | no flag | REVIEW | 85 | npm @mindstone/mcp-server-salesforce |
| io.github.semwalajay83-sem/salesforce-metadata-mcp | io.github.semwalajay83-sem | no flag | REVIEW | 85 | npm salesforce-metadata-mcp |
| Salesforce Cloud | io.github.aaronsb | no flag | REVIEW | 82 | npm @aaronsb/salesforce-cloud-mcp |
| cloud.serpent/salesforce-devops | cloud.serpent | no flag | REVIEW | 80 | remote endpoint |
| Salesforce | io.github.pipeworx-io | no flag | REVIEW | 79 | remote endpoint |
| dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper | dev.workers.selbyventurecap.cf-worker | no flag | REVIEW | 66 | remote endpoint |
| ai.smithery/kodey-ai-salesforce-mcp | ai.smithery | no flag | REVIEW | 64 | remote endpoint |
| ai.smithery/kodey-ai-salesforce-mcp-kodey | ai.smithery | no flag | REVIEW | 64 | remote endpoint |
| ai.smithery/kodey-ai-salesforce-mcp-minimal | ai.smithery | no flag | REVIEW | 64 | remote endpoint |
| ai.smithery/kodey-ai-salesforce-mcp-server | ai.smithery | no flag | REVIEW | 64 | remote endpoint |
| Salesforce Marketing | io.github.ZLeventer | repo unreachable | REVIEW | 84 | npm salesforce-marketing-mcp |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.