# Traefik Proxy MCP for AI Agents AI Agent Connect > Traefik Proxy lets you manage and monitor your edge router infrastructure through your AI client. Instead of digging through complex dashboards or CLI outputs, you can ask your agent to list active services, check middleware rules, or pull the full runtime configuration. It connects your Traefik instance to your workflow, making it easy to audit network access and routing logic in seconds. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_XR4oOb1z1qkw6S7MhXRdL3nbHzwLVvugJLZ0CnCs/ai-agent-connect - **Tags:** load-balancing, reverse-proxy, infrastructure-monitoring, edge-routing, network-management ## Description Managing a complex load balancer usually means jumping between tabs or running long commands to see if a service is actually live or if a middleware is blocking traffic. This Connector changes that by letting you talk directly to your Traefik Proxy. You can ask your agent to summarize your current setup, find specific web routes, or check the status of your network ports. It makes infrastructure auditing feel like a conversation rather than a chore. Since Vinkius hosts this, you can plug it into your existing setup and get immediate visibility into your edge routing. It's built for anyone who needs to know exactly how traffic is flowing without having to manually parse configuration files or navigate a dense UI. ## Tools ### get_http_middleware Look up the configuration for a specific HTTP middleware. Use this to see how requests are being modified. ### get_entrypoint Get specific details for a single entrypoint. This helps you see exactly what a port is doing. ### list_entrypoints List every entrypoint in your Traefik setup. This gives you a full map of your network's front doors. ### get_http_router Fetch the details of a specific HTTP router. It shows you the rules governing your web traffic. ### get_http_service Retrieve info for a single HTTP service. This is useful for checking service-specific settings. ### get_tcp_middleware Get the configuration for a TCP middleware. Use it to understand non-HTTP traffic processing. ### get_tcp_router View the details of a specific TCP router. This helps you see how raw TCP traffic is routed. ### get_tcp_service Retrieve details for a specific TCP service. It provides clarity on your TCP backend connections. ### list_http_middlewares See all HTTP middlewares currently in use. Use this to audit your security and transformation layers. ### list_http_routers List all active HTTP routers. This is the fastest way to see your entire web routing logic. ### list_http_services List every HTTP service your proxy handles. It helps you verify which backends are currently active. ### list_tcp_middlewares See all TCP middlewares in your configuration. Use this to check non-HTTP processing rules. ### list_tcp_routers List all active TCP routers. This shows you how your proxy handles raw TCP connections. ### list_tcp_services List all TCP services. Use this to see your backend TCP endpoints at a glance. ### list_udp_routers List all UDP routers in your setup. This is helpful for checking your UDP traffic routing. ### list_udp_services List all UDP services. Use this to verify your UDP backend connections. ### get_overview Get a high-level summary of your Traefik state. It shows you the total count of routers and services immediately. ### get_rawdata Access the full runtime configuration. This is your go-to for deep debugging and auditing. ## Prompt Examples **Prompt:** ``` What's the status of my Traefik setup? ``` **Response:** ``` I've pulled the overview for you. You currently have: | Type | Count | | :--- | :--- | | HTTP Routers | 12 | | TCP Routers | 8 | | Services | 15 | Your entrypoints are active on the expected ports. ``` **Prompt:** ``` Show me all the HTTP middlewares. ``` **Response:** ``` Here are the HTTP middlewares currently active: - **AuthMiddleware**: Handles basic authentication. - **RedirectMiddleware**: Sends users to the login page. - **RateLimitMiddleware**: Limits requests per IP. You can see the specific rules for each one if you'd like. ``` **Prompt:** ``` Check the entrypoint for port 443. ``` **Response:** ``` Looking at the 'websecure' entrypoint... - **Address**: :443 - **HTTP/3**: Enabled - **Active Routers**: 5 It is currently handling traffic for your production web services. ``` ## Capabilities ### Get a system overview See your total count of active routers and services at a glance. ### Inspect HTTP middlewares Check how specific requests are being transformed or secured. ### Map network entrypoints View all active entrypoints to troubleshoot connection issues. ### Audit TCP and UDP routers Drill down into specific routing rules for non-HTTP traffic. ### Pull raw configurations Access the full runtime data for deep infrastructure debugging. ## Use Cases ### Troubleshooting a 502 error An engineer asks the agent to check the get_http_service for a specific backend to see if it's correctly registered. ### Security auditing A security lead asks the agent to list all list_http_middlewares to verify that every service has the required auth layers. ### New service deployment A developer asks the agent to list all list_http_routers to confirm their new API route is visible to the proxy. ### Entrypoint verification An SRE asks the agent to describe the get_entrypoint for port 443 to check if HTTP/3 is active. ## Benefits - Faster troubleshooting: Use list_http_routers and list_http_services to see your entire routing logic in one go instead of clicking through menus. - Detailed middleware audits: Check specific transformations with get_http_middleware to ensure your security headers and redirects are working correctly. - Instant system health: Get a quick summary of your infrastructure using get_overview to see how many services and routers are live. - Deep debugging: Pull the full runtime configuration with get_rawdata when you need to see the exact state of the proxy for a complex issue. - Protocol versatility: Inspect HTTP, TCP, and UDP configurations using tools like list_udp_routers to manage diverse traffic types. ## How It Works The bottom line is you get instant, natural language access to your proxy configuration. 1. Subscribe to the Traefik Proxy MCP on Vinkius. 2. Add your Traefik API URL and any Basic Auth credentials to your client. 3. Ask your agent to list your routers or check service status to see live data. ## Frequently Asked Questions **Can I use Traefik Proxy to see my routing rules?** Yes, you can ask your agent to list all HTTP routers to see exactly how your web traffic is being directed. **How does Traefik Proxy help with debugging?** It gives you direct access to the raw runtime configuration and specific service details to find errors quickly. **Can I check my UDP and TCP services too?** Yes, the Connector includes tools to list and inspect UDP and TCP routers and services for non-web traffic. **Is Traefik Proxy good for security audits?** It's great for auditing because you can quickly list all middlewares to see which security rules are active. **Does Traefik Proxy show entrypoint details?** You can get specific details for any entrypoint, including the address it's listening on and the number of routers it handles. **Can I use Traefik Proxy to see my middleware configurations?** Yes, you can inspect the specific details of any HTTP or TCP middleware to see how it transforms requests. **Can I see the full runtime configuration of my Traefik instance?** Yes. Use the `get_rawdata` tool to retrieve the entire runtime configuration, including all providers, routers, services, and middlewares in a single response. **How do I check the status of a specific HTTP service?** You can use `list_http_services` to see all services or `get_http_service` with the specific service name to get detailed health and configuration metrics. **Does this support TCP and UDP routing inspection?** Absolutely. The server includes dedicated tools like `list_tcp_routers`, `list_udp_routers`, and their corresponding service tools to manage non-HTTP traffic.