Skip to main content
Glama
fredericsuretat

Docker Forge MCP

add_traefik

Generate Traefik v3 labels for Docker services with TLS, HTTP-to-HTTPS redirect, and optional middleware like rate limiting or authentication.

Instructions

Generate Traefik v3 labels for a Docker service. Produces ready-to-paste labels for docker-compose.yml and a networks section. Supports TLS (Let's Encrypt), HTTP→HTTPS redirect, and optional middleware presets: rate-limit, security-headers, auth-basic, compress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tlsNoEnable TLS with certresolver (default: true)
portYesInternal port the service listens on (e.g. 3000, 8000, 80)
domainYesPublic domain, e.g. "myapp.example.com"
networkNoExternal Traefik network name (default: "proxy")proxy
middlewaresNoOptional middleware presets to enable
certresolverNoTraefik certresolver name (default: "letsencrypt")letsencrypt
service_nameYesName of the Docker service (used as router/service name in Traefik)
include_http_redirectNoAdd HTTP→HTTPS redirect router (default: true)
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Describes outputs (labels, networks section) and supported features (TLS, redirect, middleware presets) without annotations. Does not mention potential side effects, but as a label generator, mutation is unlikely.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with the action and resource, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers generation of labels and main options. Lacks output format details, but no output schema exists. Adequate for a simple generation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all parameters. Description adds no new parameter-specific details beyond summarizing features like TLS and middlewares, keeping score at baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States 'Generate Traefik v3 labels for a Docker service' with a specific verb and resource. Distinguishes from siblings like generate_dockerfile and generate_env.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage by describing output for docker-compose.yml, but no explicit when-to-use or when-not-to-use vs alternatives like audit_compose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredericsuretat/docker-forge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server