Distr MCP Server
Distr also exposes its endpoints via the model context protocol to allow LLM-powered agents to interact with the Distr tools.
Common use cases include:
- Investigate which deployments are failing and why
- Update deployments, for example, as part of n8n workflows
- Interact with the Distr Platform through natural language prompts
Getting Started With the Distr MCP Server
Section titled “Getting Started With the Distr MCP Server”The Distr MCP Server is a separate go command that can be compiled locally.
Build the Distr MCP Server
Section titled “Build the Distr MCP Server”Make sure you have downloaded the Distr source code and have Go installed. Then, you can build the Distr MCP Server with the following command:
make build-mcp-server
After compilation, the MCP server binary will be available in the ./dist/
directory.
Which can be verified with ./dist/mcp-server --help
.
Configure the Distr MCP Server Tools
Section titled “Configure the Distr MCP Server Tools”The Distr MCP Server exposes its executable functions via tools.
If you want to use all tools, you can extend your mcp.json
configuration file in your MCP client:
{ "servers": { "distr": { "command": "dist/mcp-server", "args": ["serve"], "tools": ["*"], "env": { "DISTR_TOKEN": "distr-..." } } }}
You can also configure the optional environment variable DISTR_HOST
to point the MCP server against a different Distr instance.
If configured correctly, your MCP client will list the available tools:

Interact with the Distr MCP Server
Section titled “Interact with the Distr MCP Server”After configuring the Distr MCP Server, you can perform prompts that gather additional information from Distr via the Distr MCP Sever.
Get all deployments and group them by their status
Section titled “Get all deployments and group them by their status”Show me all distr deployments and group them by status.
Here are all distr deployments grouped by status:
Status: Running / OK
- Local: On-Prem LLM App 2 (nginx:1.27.4)
- Local: On-Prem LLM App 2 (1.28.0)
- kcd: Podinfo (6.7.1)
- ACME, Inc.: Hello Distr (0.1.6)
- Compliance Company: Podinfo (6.7.1)
- Edision: Security Agent (0.4.20)
- Gov: Podinfo (6.7.1)
Status: Error
- ACME, Inc.: Hello Distr (0.1.9) — missing environment variable
- Pear, Inc.: On-Prem LLM App 2 (error) — image not found …
Investigate failed deployments
Section titled “Investigate failed deployments”Why do the deployments are in the status error, show the latest log.
Here are the deployments in error status and the reason why, including their latest log:
1. ACME, Inc.: Hello Distr (version 0.1.9)
- Reason: Missing environment variable.
- Latest log: error while interpolating services.postgres.environment.POSTGRES_DB: required variable HELLO_DISTR_DB_NAME is missing a value: error
2. Pear, Inc.: On-Prem LLM App 2 (version error)
- Reason: Image not found.
- Latest log: nginx Pulling nginx Error manifest for nginx:error not found: manifest unknown: manifest unknown Error response from daemon: manifest for nginx:error not found: manifest unknown: manifest unknown
If you need more detailed logs or troubleshooting steps, let me know!