Ext Ops Panel
Open dashboard
Comparison

Salt vs Agent-Native Clips

Salt is an MCP server published by saltapp.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Agent-Native Clips is an MCP server published by BuilderIO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
MarketplaceSaltAgent-Native Clips
Official MCP Registry Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 688
Stars (GitHub): 7 525
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 Agent-Native Clips
FactSaltAgent-Native Clips
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)7 525 (better)
Forks (GitHub) (differs)0 (worse)688 (better)
Last release (differs)2026-10-20Not published
Where it runs (differs)Remote server (mcp.saltapp.ai/mcp)Remote server (clips.agent-native.com/mcp)
TransportStreamable HTTPStreamable HTTP
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/builderio/agent-native
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-24Responded 2 days ago, requires a key

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.

Agent-Native Clips

In its own words, on Official MCP Registry:

Screen recording, meeting notes, and voice dictation - all with AI

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

Agent-Native Clips As a remote MCP server

Claude Code
claude mcp add --transport http agent-native-clips https://clips.agent-native.com/mcp

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

Only the endpoint of Agent-Native Clips responded at the last daily 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 Agent-Native Clips publish no settings it asks for, so we do not compare settings.

What it can do: Salt · What it can do: Agent-Native Clips · 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