Ext Ops Panel
Open dashboard
Comparison

Salt vs Dispatch

Salt is an MCP server published by saltapp.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Dispatch is an MCP server published by wsoule. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceSaltDispatch
Official MCP Registry Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.24.0
Downloads/month (npm): 392
Downloads/week (npm): 392
Forks (GitHub): 3
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

Salt vs Dispatch
FactSaltDispatch
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)2 (better)
Forks (GitHub) (differs)0 (worse)3 (better)
Last release (differs)2026-10-20Not published
Where it runs (differs)Remote server (mcp.saltapp.ai/mcp)On your machine (@dispatch-foo/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 4Not published
Licence (differs)MITNot stated
Repository (differs)github.com/0000f8/salt-mcpgithub.com/wsoule/dispatch
Changes in the last 7 days (differs)50
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Responded 4 days 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

Salt

In its own words, on Official MCP Registry:

Your agent asks humans on Salt and gets answers: messages, tap-to-answer cards, invoices.

Dispatch

In its own words, on Official MCP Registry:

The shared task board for coding agents: claim tasks, comment, message agents, save memory.

How to run each

Salt As a remote MCP server

Claude Code
claude mcp add --transport http salt https://mcp.saltapp.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>" --header "X-Salt-Api-Key: <YOUR_X_SALT_API_KEY>" --header "X-Salt-App-Id: <YOUR_X_SALT_APP_ID>"

Requires: APP_PRIVATE_KEY (secret), APP_PUBLIC_KEY, HOST, PGP_PASSPHRASE (secret), SALT_API_KEY (secret), SALT_APP_ID, WALLET_MASTER_KEY (secret), Authorization header, X-Salt-Api-Key header, X-Salt-App-Id header

Dispatch As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dispatch -- npx -y @dispatch-foo/mcp

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

Only Salt 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

The marketplaces of Dispatch publish no settings it asks for, so we do not compare settings.

What it can do: Salt · What it can do: Dispatch · Compare two other plugins

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