Traefik Labs Introduces the Traefik MCP Server, Grounding AI Agents in the Gateway from Day 0 to Day 2
Launched with initial support for Datadog, Grafana Labs, and Dash0, the read-only server gives an agent what's valid, what's running, and what's happening at a Traefik gateway, so it can write configuration that works on the release in use, prove who can reach what, and explain why the gateway did what it did
SAN FRANCISCO, October 22, 2026--Traefik Labs today introduced the Traefik MCP Server, a read-only Model Context Protocol (MCP) server that grounds AI agents in three sources at once: what's valid, from the exact schema of the Traefik release in use; what's running, from the gateway's live configuration; and what's happening, from the traces, metrics, and logs in Datadog, the Grafana stack (Prometheus, Tempo, and Loki), or Dash0. It works in any MCP client engineers already use, from the day a gateway is set up to the years it runs in production.
AI agents can already write configuration and read telemetry, and for simple problems that is enough. However, a configuration that looks right is not the same as one the running release accepts, and a wrong answer that looks right is the one that gets applied. The hard problems live in configuration, which never reaches a telemetry backend. Which route took this request, and why? Which keys and routes exist that nobody has used? Will this fix work before it ships? The same questions now apply to AI traffic: which route lets a caller choose its own model, what one incoming request actually cost, and which guard was in front of it.
From Day 0 Setup to Day 2 Operations
Deploying a gateway takes an afternoon. Running it takes years. On Day 0, the agent writes routes, middlewares, and migrated NGINX annotations against the exact release, and checks which metrics the gateway should emit and which actually reach the team's backend. On Day 1, it proves who can reach what: which routes have no authentication, which keys nobody has used, and which guard stands in front of each AI route. On Day 2, where platform teams spend years, it explains why traffic went where it did and proposes a validated change. Every one of those answers needs telemetry and configuration read together, and today they live apart: the telemetry in an observability backend, the configuration in the gateway. The Traefik MCP Server joins them, so an agent sees what happened and why in one view. What used to mean an engineer combing through configuration becomes a validated answer in minutes.
"Having an MCP server is not the news. What an agent can do with it is," said Sudeep Goswami, CEO of Traefik Labs. "Our customers run their gateways for years, and every question in that time is as much about configuration as about telemetry. This server gives an agent both, from the first route it writes to the incident it explains years later, and because it is read-only, platform teams can finally let an agent near the ingress layer."