Vendor: salesforce.com · entry id 06-salesforce-agentforce · source 06-revops-infra.md line 11
The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-24. On 2026-09-04 the recorded URL was a reachable repository or package: a server you install and run on your own machine over stdio. Callable after an install, not a remote endpoint.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://github.com/salesforcecli/mcp (Salesforce DX/CLI MCP server, dev-tooling use case); https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/hosted-mcp-servers-overview.html and https://github.com/forcedotcom/mcp-hosted (Salesforce Hosted MCP Servers, GA April 2026, external AI clients read/act on live org data)
A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.
Install, as the source shows it:
npm install -g @salesforce/cliquoted from https://www.npmjs.com/package/@salesforce/cli on 2026-09-27, via npm
Packages seen, with the version on 2026-09-27:
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.
api_gate, verbatim from the file:
enterprise-only for the MCP-enabled path - Salesforce Hosted MCP Servers require Enterprise Edition or above. Raw REST API access is free on Developer Edition sandboxes; production-tier API pricing/inclusion by edition was not independently confirmed and is marked unknown rather than guessed.
No documentation URL recorded.
727 of 1252 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:
github.com/salesforcecli tied to the vendor by rule 1, account website https://developer.salesforce.com/tools/salesforcecli has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| plugin-trust | plugin or integration | 2 | 2026-09-08 | 4.0.12 | |
| plugin-apex | CLI | Salesforce CLI Plugin that hosts the Apex commands | 5 | 2026-09-08 | 4.1.2 |
| cli | CLI | The `sf` cli. | 180 | 2026-09-08 | 2.151.6 |
| plugin-data-setup-transfer | plugin or integration | 0 | 2026-09-07 | 1.0.2 | |
| plugin-data-code-extension | plugin or integration | 0 | 2026-09-07 | 1.4.1 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.
This page is the canonical home. The listing below is the same product, counted separately in the source markdown.
What that listing says it does: A prebuilt agent within Salesforce's Agentforce platform intended to handle inbound lead engagement and outbound prospecting conversations natively inside Sales Cloud, escalating to a human rep once a prospect is ready.
16 of the 1252 entries are cross listed like this. They are why the entry count is 1252 and the unique product count is 1236. The canonical home is declared in INDEX.md, not chosen by the parser.
5 source URLs. Raw sources field, verbatim:
https://developer.salesforce.com/blogs/2025/06/introducing-mcp-support-across-salesforce, https://developer.salesforce.com/blogs/2026/04/salesforce-hosted-mcp-servers-are-now-generally-available, https://github.com/salesforcecli/mcp, https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/hosted-mcp-servers-overview.html, https://developer.salesforce.com/blogs/2026/07 (Headless 360 MCP Server Beta announcement)
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.