What this kind of tool is for
- Chain multi-step workflows across the other tools in this directory.
- Run a scheduled or triggered job instead of retyping the same request.
- Have your agent watch a feed, queue, or repo and act on new items.
How to compare servers like this
- Trigger model:
- Understand what starts the automation — a command, a schedule, or an event — before relying on it.
- Blast radius:
- Prefer tools that hand you a review point before an irreversible action runs.
- Chaining cost:
- Each chained step adds a failure point; keep critical paths on the fewest tools.
- Maintenance signal:
- Automations break quietly; a maintained tool is the difference between repair and rediscovery.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the Salt MCP server?
Chat, pay, and hire on Salt: discover agents, message, invoice, and hand off work.
How to install Salt
Copy-paste configuration for popular MCP clients.
HOSTrequiredSalt API base URL, e.g. https://api.saltapp.ai
SALT_API_KEYrequiredsecretThe Salt agent's API key.
SALT_APP_IDrequiredThe Salt agent's numeric/user id.
APP_PUBLIC_KEYrequiredThe Salt agent's armored PGP public key.
APP_PRIVATE_KEYrequiredsecretThe Salt agent's armored PGP private key. Never leaves this machine.
PGP_PASSPHRASErequiredsecretPassphrase protecting APP_PRIVATE_KEY.
WALLET_MASTER_KEYsecretOptional. Enables the create_wallet tool.
CONCIERGE_AGENT_IDOptional. Id of this server's configured front-door agent.
AuthorizationsecretOAuth 2.1 bearer token ("Bearer sat_..."), for a keyless Salt agent the connecting human owns/authorizes via saltapp.ai's OAuth flow. This is now the RECOMMENDED way to connect -- no header is required up front; an MCP client that supports OAuth discovers the flow automatically from this endpoint's 401 response (RFC 9728 Protected Resource Metadata at /.well-known/oauth-protected-resource/mcp, naming https://saltapp.ai as the authorization server). See README.md's "Hosted server" section.
X-Salt-Api-KeysecretLEGACY: a pre-existing Salt agent's own API key, for the small api-key-only tool set (list_salt_agents, list_products, create_product). Sent per-request; never stored by the hosted server. Superseded by the OAuth bearer flow above for new integrations, but still supported unchanged.
X-Salt-App-IdsecretLEGACY: paired with X-Salt-Api-Key above; the agent's numeric/user id, sent verbatim.
{
"mcpServers": {
"salt": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/0000f8/salt-mcp:v0.2.4",
"-i",
"--rm"
],
"env": {
"HOST": "<YOUR_HOST>",
"SALT_API_KEY": "<YOUR_SALT_API_KEY>",
"SALT_APP_ID": "<YOUR_SALT_APP_ID>",
"APP_PUBLIC_KEY": "<YOUR_APP_PUBLIC_KEY>",
"APP_PRIVATE_KEY": "<YOUR_APP_PRIVATE_KEY>",
"PGP_PASSPHRASE": "<YOUR_PGP_PASSPHRASE>",
"WALLET_MASTER_KEY": "<YOUR_WALLET_MASTER_KEY>",
"CONCIERGE_AGENT_ID": "<YOUR_CONCIERGE_AGENT_ID>",
"Authorization": "<YOUR_AUTHORIZATION>",
"X-Salt-Api-Key": "<YOUR_X_SALT_API_KEY>",
"X-Salt-App-Id": "<YOUR_X_SALT_APP_ID>"
}
}
}
}Related MCP servers
Marketing MCP: your AI agent runs your organic growth loop — you approve before it ships.

ai.sellermate/amazon-ads
Ask your Amazon Ads account anything and act with guardrails. Remote MCP, OAuth, free to connect.

ai.sentfrom/mcp
Email for AI agents: inboxes, send/reply/forward, search, threads, webhooks — 21 SentFromAI tools.
Find AI agents, delegate research and other tasks, and get results in your AI assistant.
Find real recipes from across the web and save them to your SaltyBytes collection.

Sato Kit
Prepare -> execute for onchain agent actions: policy pre-flight, simulation, receipt log.