Traefik MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_LEVEL | No | Logging level (default: INFO) | INFO |
| TRAEFIK_API_KEY | No | API key for Bearer token authentication | |
| TRAEFIK_API_URL | Yes | URL of your Traefik API 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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_traefik_overviewB | Get an overview of the Traefik instance configuration |
| list_routersC | List all HTTP routers in Traefik |
| get_router_detailsC | Get detailed configuration for a specific router |
| list_servicesB | List all HTTP services in Traefik |
| get_service_detailsC | Get detailed configuration for a specific service |
| list_middlewaresC | List all HTTP middlewares in Traefik |
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
Every tool has a clearly distinct purpose targeting specific resources in Traefik: three 'get' tools for detailed configuration of routers, services, and the overall instance, and three 'list' tools for enumerating middlewares, routers, and services. There is no overlap or ambiguity in functionality.
All tool names follow a consistent verb_noun pattern with clear and descriptive naming. The verbs 'get' and 'list' are used appropriately, and nouns like 'router_details', 'service_details', and 'traefik_overview' maintain a uniform structure throughout.
With 6 tools, the server is well-scoped for managing a Traefik instance. It provides essential read operations for configuration overview and details, which is appropriate for monitoring and inspection purposes without being overly complex or sparse.
The tool set covers read operations thoroughly for routers, services, middlewares, and overall configuration, but there are notable gaps for write operations like creating, updating, or deleting resources. This limits the server to inspection-only workflows, which may be insufficient for full management.