Ext Ops Panel
Open dashboard
Comparison

Close vs sf-intelligence: offline Salesforce MCP server

Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). sf-intelligence: offline Salesforce MCP server is an MCP server published by PranavNagrecha. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceClosesf-intelligence: offline Salesforce MCP server
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.0
Downloads/month (npm): 910
Downloads/week (npm): 296
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Close vs sf-intelligence: offline Salesforce MCP server
FactClosesf-intelligence: offline Salesforce MCP server
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (mcp.close.com/mcp)On your machine (sf-intelligence)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Licence (differs)Apache-2.0SEE LICENSE IN LICENSE
Repository (differs)Not statedgithub.com/pranavnagrecha/salesforce-intelligence
Changes in the last 7 days (differs)07
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 h ago, requires a keyno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Close

In its own words, on Docker MCP Catalog:

Streamline sales processes with integrated calling, email, SMS, and automated workflows for small and scaling businesses.

sf-intelligence: offline Salesforce MCP server

In its own words, on Official MCP Registry:

Ask your AI what breaks before you change Salesforce. Offline, read-only, cited answers.

How to run each

Close As a remote MCP server

Claude Code
claude mcp add --transport http close https://mcp.close.com/mcp

Requires: CLOSE_API_KEY (secret)

sf-intelligence: offline Salesforce MCP server As a local MCP server: npm package

Claude Code
claude mcp add --env "SFI_VAULT=<YOUR_SFI_VAULT>" --transport stdio salesforce-intelligence -- npx -y sf-intelligence mcp

Requires: SFI_VAULT

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Close has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Close asks for

  • CLOSE_API_KEY (secret)

Only sf-intelligence: offline Salesforce MCP server asks for

  • SFI_VAULT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Close · What it can do: sf-intelligence: offline Salesforce MCP server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built