Skip to main content

Resources

The Traefik MCP Server provides MCP Resources for real-time data streams. Resources are read-only — they provide context for AI agents to make informed decisions before using state-changing tools.

Available Resources​

Resource URIDescription
traefik://traffic/routes/listAll TraefikServices across the cluster
traefik://traffic/<namespace>/<route_name>/distributionLive weights, middleware state, and match rules for a route
traefik://metrics/<namespace>/<service>/summaryError rate bounds and P99 latency via Prometheus
traefik://metrics/prometheus/statusPrometheus backend connectivity check
traefik://anomalies/detectedCurrently detected traffic anomalies
traefik://anomalies/history/<namespace>Historical anomaly audit log for a namespace
traefik://migration/nginx-to-traefikNGINX migration status overview
traefik://migration/nginx-to-traefik/<phase>Per-phase migration analytics (e.g., phase1, phase3)
traefik://migration/nginx-ingress-scanLive Ingress inventory with paths and annotations
traefik://migration/nginx-ingress-scan/<namespace>Ingress inventory scoped to one namespace
traefik://migration/nginx-ingress-analyzeFull NGINX→Traefik compatibility analysis (cluster-wide)
traefik://migration/nginx-ingress-analyze/<namespace>Compatibility analysis scoped to one namespace

traefik://traffic/routes/list​

Cluster-wide listing of all TraefikServices. Use to discover existing routes before linking to deployments.

Use Case:

"List all Traefik services across all namespaces."
"Show me all TraefikService resources — I need to find which one to link to my rollout."

traefik://traffic/<namespace>/<route_name>/distribution​

Live traffic distribution for a specific route — weights, percentages, attached middlewares, match rules, and entrypoints.

URI Example: traefik://traffic/production/api-service-route/distribution

Use Case:

"What is the current traffic split for 'api-service-route' in 'production'?"
"Show me how traffic is distributed and what middlewares are on 'frontend-route' in 'staging'."

traefik://metrics/<namespace>/<service>/summary​

Prometheus-backed metrics summary: 5xx/4xx error bounds and P99 latency.

URI Example: traefik://metrics/production/api-service/summary

Use Case:

"Show performance metrics for 'api-service' in 'production'."
"What are the error rates and latency for 'frontend' in 'staging'?"

traefik://metrics/prometheus/status​

Verify Prometheus backend is reachable and collecting metrics.

Use Case:

"Is Prometheus connected and working for metrics collection?"

traefik://anomalies/detected​

Real-time traffic anomalies detected across the cluster — connection errors, unusual error patterns.

Use Case:

"Show me all currently detected traffic anomalies in the cluster."
"Are there any routing issues right now?"

traefik://anomalies/history/<namespace>​

Historical anomaly audit log for a specific namespace.

URI Example: traefik://anomalies/history/production

Use Case:

"Show anomaly history for the 'production' namespace."
"Were there any traffic issues in 'staging' over the last hour?"

traefik://migration/nginx-to-traefik​

Overview of active NGINX-to-Traefik proxy migrations.

Use Case:

"Show me the full NGINX to Traefik migration guide."
"What's the current state of our migration?"

traefik://migration/nginx-to-traefik/<phase>​

Phase-specific migration analytics.

URI Example: traefik://migration/nginx-to-traefik/phase2

Use Case:

"Show me Phase 2 of the NGINX to Traefik migration guide."
"What are the Phase 4 steps for the NGINX to Traefik migration?"

traefik://migration/nginx-ingress-scan​

Live inventory of all NGINX Ingress resources — paths, annotations, and metadata. Use before running the migration tool to understand what will be converted.

Use Case:

"Scan all NGINX Ingress resources in the cluster."
"Show me what NGINX Ingresses exist in the 'production' namespace."

traefik://migration/nginx-ingress-analyze​

Full compatibility analysis comparing NGINX annotations against Traefik equivalents. Identifies supported, unsupported, and breaking annotations before migration.

Use Case:

"Analyze NGINX Ingress compatibility for migration to Traefik."
"Which NGINX annotations will need manual fixes during migration?"

Using Resources​

Resources are accessed via the MCP protocol using their URI. AI agents subscribe to resources for context before making tool calls.

Client: What is the current traffic split for api-service-route in production?
Agent: [Reads traefik://traffic/production/api-service-route/distribution]
       [Returns weights, middlewares, match rules]
Client: Are there any issues with our migration?
Agent: [Reads traefik://migration/nginx-ingress-analyze]
       [Returns compatibility analysis with flagged annotations]

Next Steps​