Salt MCP
Connect an MCP client to Salt to work with Pipelines, runs, nodes, data, and models.
Salt MCP gives an external MCP client access to Salt through a remote set of tools. Use it when you want to work with Salt resources from an MCP-compatible application instead of opening each area of Salt directly.
When to use Salt MCP
Use Salt MCP when your MCP client needs to list or build Pipelines, run them, inspect their results, or work with other resources in your Salt account. The tools available to you depend on your account permissions and the OAuth access granted to the client.
Salt MCP is different from two related Salt features:
- Custom agents are conversational assistants that you configure and use in Ask Salt. Use an agent when you want a chat experience within Salt.
- Connectors let a Pipeline interact with an external service. Use a connector when a node needs access to a model provider, data source, messaging service, or other integration.
What you can work with
Salt MCP organizes its tools into broad capability groups:
- Pipelines -- list, create, edit, share, and build Pipelines on the canvas.
- Runs and results -- start Pipeline runs, check their status, and access artifacts.
- Nodes -- browse the node registry and documentation, and author custom nodes.
- Connections and data -- work with credentials, connections, and knowledge bases.
- Models -- work with Model Vault and model deployments.
How access works
Salt MCP is a stateless remote server available at https://salt-api-prod.salt.ai/mcp. MCP clients connect through browser-based OAuth, which grants read access by default. You can enable write access for operations that change Salt.
Your Salt account permissions still apply after authorization. Connecting a client does not give it access to resources or operations that your account cannot use.