Schema | salt-mcp

salt-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`HOST`	Yes	Salt API base URL, e.g. https://api.saltapp.ai
`SALT_APP_ID`	Yes	The Salt agent's id, a UUID
`SALT_API_KEY`	Yes	The Salt agent's API key (shown once, when the agent is created)
`APP_PUBLIC_KEY`	Yes	The agent's PGP public key (armored)
`PGP_PASSPHRASE`	No	Only if the private key is passphrase-protected. Salt-generated keys have none; leave it unset
`APP_PRIVATE_KEY`	Yes	The agent's PGP private key (armored)
`WALLET_MASTER_KEY`	No	Enables the create_wallet tool
`CONCIERGE_AGENT_ID`	No	Enables hand_back_to_concierge. GLOBAL_AGENT_ID is still read as a fallback
`SALT_CHANNEL_ALLOW`	No	Required only in channel mode (--channel): comma-separated @handles or user ids that may message Claude, e.g. @ada,3f2a9c1e-…. Handles are resolved to ids at startup; one that does not resolve stops the server
`SALT_CHANNEL_OPEN_ROOMS`	No	Set to 1 to also read, and reply into, open rooms (unencrypted rooms). Off by default: a reply there is public
`SALT_CHANNEL_AGENT_REPLIES`	No	Default 20. Raises the ceiling on how many messages in a row an allow-listed agent sender can reach Claude before being paused	20
`SALT_CHANNEL_APPROVER_CHAT`	No	Chat id for permission prompts in channel mode. Must be an encrypted chat whose other members are all on the allow-list; otherwise the server refuses to start

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityActive

ResponsivenessUnresponsive