Your agent asks humans on Salt and gets answers: messages, tap-to-answer cards, invoices.
Salt is an MCP integration. Your agent asks humans on Salt and gets answers: messages, tap-to-answer cards, invoices.
The registry lists a streamable-http connection at https://mcp.saltapp.ai/mcp. The endpoint declares these request headers: Authorization, X-Salt-Api-Key, X-Salt-App-Id.
The published oci package is ghcr.io/0000f8/salt-mcp:v0.2.7. Its declared MCP transport is stdio.
The package declares HOST (required): Salt API base URL, e.g. https://api.saltapp.ai; SALT_API_KEY (required): The Salt agent's API key. Shown once when the agent is created.; SALT_APP_ID (required): The Salt agent's id (a UUID). Self-registration and the agent's webhook_secret endpoint return it as agent_id.; APP_PUBLIC_KEY (required): The Salt agent's armored PGP public key.; APP_PRIVATE_KEY (required): The Salt agent's armored PGP private key. Never leaves this machine.; PGP_PASSPHRASE: Optional. Only if APP_PRIVATE_KEY is passphrase-protected; Salt-generated keys have none.; WALLET_MASTER_KEY: Optional. Enables the create_wallet tool.; CONCIERGE_AGENT_ID: Optional. Id of this server's configured front-door agent..
This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.2.7 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related payments & commerce MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| HOST | Salt API base URL, e.g. https://api.saltapp.ai | Yes |
| SALT_API_KEY | The Salt agent's API key. Shown once when the agent is created. | Yes |
| SALT_APP_ID | The Salt agent's id (a UUID). Self-registration and the agent's webhook_secret endpoint return it as agent_id. | Yes |
| APP_PUBLIC_KEY | The Salt agent's armored PGP public key. | Yes |
| APP_PRIVATE_KEY | The Salt agent's armored PGP private key. Never leaves this machine. | Yes |
| PGP_PASSPHRASE | Optional. Only if APP_PRIVATE_KEY is passphrase-protected; Salt-generated keys have none. | Optional |
| WALLET_MASTER_KEY | Optional. Enables the create_wallet tool. | Optional |
| CONCIERGE_AGENT_ID | Optional. Id of this server's configured front-door agent. | Optional |
Access Stripe billing and payment tools through its MCP server. Connect with OAuth or a supported agent API key and choose the intended account.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
MCP server for T-Kassa (T-Bank/Tinkoff) payment API — payments, refunds. 5 tools. First MCP for T-K
One MCP for agent commerce: read · pay · publish. Teacher, not butler.
Travel eSIMs for 193 countries. Stripe + Bitcoin checkout. QR by email in 30s. No API key.
Korea payments for AI agents — card, KakaoPay/NaverPay, 가상계좌 via Toss Payments. Never holds funds.