# Traefik Proxy MCP > Traefik Proxy provides real-time visibility into your edge router configuration, letting you inspect every service and rule without opening a dashboard. Connect this MCP to query routers, services, middlewares, and entrypoints across HTTP, TCP, and UDP protocols using natural conversation. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Tags:** load-balancing, reverse-proxy, infrastructure-monitoring, edge-routing, network-management ## Description This connector gives your agent direct access to the operational details of your Traefik Proxy instance. Instead of jumping between multiple dashboards—one for routing, another for services, and a third for middleware—you can ask your AI client exactly what's happening at your edge. You can get a high-level summary or deep-dive into raw configuration data instantly. Need to check if traffic is reaching the correct port? Ask about entrypoints. Curious how a specific request is being transformed? Check the middlewares. It’s all available through a conversation, making complex infrastructure auditing simple. This capability becomes a core part of your existing Vinkius catalog tools, turning tedious manual checks into quick queries. ## Tools ### get_entrypoint Retrieves detailed information about a specific network entry point. ### get_http_middleware Fetches the configuration details for a particular HTTP middleware. ### get_http_router Gets specific information about an active HTTP router rule. ### get_http_service Retrieves details for a specified HTTP service endpoint. ### get_tcp_middleware Gets the configuration for a specific TCP middleware. ### get_tcp_router Retrieves details about a particular TCP router rule. ### get_tcp_service Gets information on a specific TCP service endpoint. ### list_entrypoints Provides an exhaustive list of all configured network entry points. ### list_http_middlewares Lists every available HTTP middleware configuration. ### list_http_routers Lists every active HTTP router rule configured in the proxy. ### list_http_services Lists all registered HTTP services endpoints. ### list_tcp_middlewares Lists every available TCP middleware configuration. ### list_tcp_routers Lists all active TCP router rules configured in the proxy. ### list_tcp_services Lists all registered TCP services endpoints. ### list_udp_routers Lists all active UDP router rules configured in the proxy. ### list_udp_services Lists all registered UDP services endpoints. ### get_overview Retrieves a summary count of routers, services, and entrypoints across the proxy. ### get_rawdata Accesses the complete, unparsed runtime configuration data for auditing purposes. ## Prompt Examples **Prompt:** ``` Give me an overview of my Traefik proxy status. ``` **Response:** ``` I've retrieved the overview. You currently have 12 HTTP routers, 8 TCP routers, and 15 services active across 3 entrypoints (web, websecure, and admin). ``` **Prompt:** ``` List all active HTTP routers and their rules. ``` **Response:** ``` Fetching HTTP routers... I found routers like 'api-rule' (Host(`api.example.com`)) and 'dashboard' (Host(`traefik.internal`)). Would you like to inspect the middlewares for any of these? ``` **Prompt:** ``` Show me the details for the entrypoint named 'websecure'. ``` **Response:** ``` Inspecting 'websecure'... This entrypoint is listening on address ':443' and has HTTP/3 enabled. It is currently handling traffic for 5 routers. ``` ## Capabilities ### Audit overall proxy health Get an immediate summary count of all active routers, services, and entrypoints currently running. ### Inspect HTTP routing rules List and get details on specific routers, services, and middlewares configured for standard web traffic (HTTP). ### Examine non-HTTP network connections Query the state of TCP and UDP routers, services, and middlewares used for streaming or specialized protocols. ### View entrypoint status List all configured ingress points (like web or websecure) and check their current operational status. ### Access full configuration data Retrieve the entire runtime configuration of Traefik for deep debugging or compliance auditing. ## Use Cases ### Investigating dropped traffic on a custom port A service is reporting intermittent connection drops. Instead of logging into the proxy UI, you ask your agent to run `list_tcp_routers` and `get_tcp_service`. The agent immediately points out that the specific router needed for the high-port traffic isn't defined, solving the mystery in seconds. ### Validating a new API endpoint deployment A backend developer pushes an updated microservice and needs to ensure it gets routed correctly. They ask their agent to run `list_http_services` followed by `get_http_router`. The response confirms the service is listed and that the required host rule is active. ### Performing a security audit of ingress points The SRE team needs to confirm every exposed port matches policy. They prompt their agent for `list_entrypoints`. The system responds with a list and status, allowing the engineer to validate that only ports 80 and 443 are active. ### Troubleshooting middleware transformation issues Traffic is passing through the proxy but headers are missing. You ask your agent about `get_http_middleware` for the specific router in question, which immediately reveals that the required header modification rule was never applied. ## Benefits - Stop clicking through multiple dashboards. By using this MCP, you can ask one question and get a full summary of the system's health with the `get_overview` tool. - Debugging complex traffic flows is fast. Need to know if an HTTP request hits the right rules? Use `get_http_router` or check specific middlewares with `get_http_middleware`. - It covers more than just web traffic. You can query non-HTTP protocols (TCP/UDP) using tools like `list_tcp_routers` and `list_udp_services`, giving you a full infrastructure view. - Deep debugging is effortless. If the standard views aren't enough, use `get_rawdata` to pull the complete runtime configuration for auditing or compliance checks. - You don't have to remember tool names. Your agent handles the complexity; you just ask what you need—be it checking a specific entrypoint via `get_entrypoint` or listing all services. ## How It Works The bottom line is you ask a question about your network infrastructure, and your agent talks to Traefik to get the specific data back to you. 1. Subscribe to this MCP and provide your Traefik API URL. Ensure the proxy's API is enabled in its configuration. 2. If your API requires it, supply any necessary basic authentication credentials. 3. Start querying the system from your preferred AI client using natural language prompts. ## Frequently Asked Questions **How do I check if a specific entrypoint is working using Traefik Proxy MCP?** Use the `get_entrypoint` tool and provide the name of the entry point you want to inspect. This gives you details on its listening addresses and current status. **Can I use the Traefik Proxy MCP for non-HTTP traffic?** Yes, this MCP handles other protocols too. You can list and check rules for TCP and UDP using tools like `list_tcp_routers` and `list_udp_services`. **What is the difference between `get_http_router` and `list_http_routers` in Traefik Proxy MCP?** The `list_http_routers` tool gives you a full inventory of every router. The `get_http_router` tool lets you drill down into specific details for one router by name. **Where do I find the complete runtime configuration with Traefik Proxy MCP?** Use the `get_rawdata` tool. This pulls the full, unparsed JSON structure of your proxy's current state, which is useful for deep debugging. **Does this MCP help me audit middleware rules in Traefik Proxy?** Yes, you can use `list_http_middlewares` to see all available middlewares. Then, you can use `get_http_middleware` to examine how a specific rule is transforming or securing traffic.