Traefik MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host IP address, default '0.0.0.0' (for 'http' transport only). | |
| MCP_PORT | No | Host port, default '8080' (for 'http' transport only). | |
| MCP_LOG_LEVEL | No | Logging level (default: INFO). | |
| MCP_TRANSPORT | No | Type of transport, must be 'stdio' or 'http'. | |
| TRAEFIK_API_KEY | No | API key for Bearer token authentication. | |
| TRAEFIK_API_URL | Yes | URL of your Traefik Dashboard endpoint (e.g., http://localhost:8080). | |
| TRAEFIK_BASIC_AUTH_PASSWORD | No | Password for basic authentication. | |
| TRAEFIK_BASIC_AUTH_USERNAME | No | Username for basic authentication. |
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_overviewC | Get an overview of the Traefik instance configuration |
| get_versionA | Get the Traefik API version |
| get_entrypointC | Get informations about entrypoints |
| get_middlewareC | Get information about middlewares |
| get_serviceC | Get information about services |
| get_routerC | Get information about routers |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct Traefik resource (entrypoints, middlewares, services, routers), so boundaries are mostly clear. get_overview and get_version could be confused since overview might include version info, but the descriptions imply different scopes.
All six tools follow a strict get_<noun> pattern with snake_case. The only nit is singular vs. plural resource nouns (get_entrypoint returning a list), but the convention itself is fully uniform.
Six tools is a reasonable, well-scoped surface for a Traefik API read interface. It is slightly thin because the server exposes only one verb across the whole domain.
Core Traefik resources (routers, services, middlewares, entrypoints) are covered, which fits a read-only API. However, obvious gaps remain: no TLS/certificate inspection, no health/ping, and no way to fetch a single resource by name for targeted lookups.