Distr MCP Server
Distr exposes its endpoints via the Model Context Protocol to allow LLM-powered agents to interact with Distr applications, deployments, and logs.
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 supports streamable HTTP and stdio as transport methods.
- Remote Hosted MCP server
- Locally Running MCP server
1. Using the Distr Hosted Remote MCP Server
Section titled “1. Using the Distr Hosted Remote MCP Server”The Distr MCP server is hosted and secured by HyprMCP (https://hyprmcp.com).
It can be accessed via: https://glasskube.hyprmcp.cloud/distr/mcp.
Authentication
Section titled “Authentication”Configure a personal access token (PAT) in an Authorization header when calling the MCP server.
Header name: Authorization
Header value: AccessToken distr-bc46...
Example configuration for Claude Code would look like:
claude mcp add --transport http distr https://glasskube.hyprmcp.cloud/distr/mcp --header "Authorization: AccessToken distr-bc46..."2. Using the Distr MCP Server Locally
Section titled “2. Using the Distr MCP Server Locally”The Distr MCP Server is a separate Go command that can be compiled locally.
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-serverAfter compilation, the MCP server binary will be available in the ./dist/ directory,
which can be verified with ./dist/mcp-server --help.
Local MCP Server Configuration
Section titled “Local MCP Server Configuration”The Distr MCP Server exposes its executable functions via tools.
To use all tools, 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:
Distr MCP Server Use Cases
Section titled “Distr MCP Server Use Cases”After configuring the Distr MCP Server, you can use prompts that gather additional information from Distr via the Distr MCP Server.
Get All Deployments and Group Them by Status
Section titled “Get All Deployments and Group Them by 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 are the deployments in error status? 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!