ITK Dev Docker MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| itkdev_list_templatesA | List all available ITK Dev Docker templates with their PHP versions and characteristics |
| itkdev_detect_projectB | Analyze a directory to detect ITK Dev project configuration, template type, PHP version, and framework |
| itkdev_get_template_filesA | List all files that would be installed by a specific template |
| itkdev_compare_projectB | Compare a project's Docker configuration against its template to find missing, outdated, or extra files |
| itkdev_get_template_contentC | Get the content of a specific file from a template |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ITK Dev Docker CLI | CLI tool commands, templates, Traefik setup, and complete setup procedures |
| ITK Dev Docker Compose | Docker Compose patterns, service configurations, and server deployments |
| ITK Dev Taskfile | Taskfile automation patterns for development workflows |
TDQS
Scored across 5 tools
Each tool targets a distinct action: detect inspects a project, list_templates enumerates templates, get_template_files and get_template_content retrieve file listings vs. file bodies, and compare_project diffs configs. The template-listing vs. template-file-content pair is clearly separated by naming and description, so misselection is unlikely.
All five tools share the itkdev_ prefix and a consistent snake_case verb_noun pattern (detect_project, get_template_files, compare_project, get_template_content, list_templates). The convention is uniform and predictable, with no mixing of styles.
Five tools is a tight, well-scoped set that matches the narrow template-inspection domain, with no redundant entries. It sits at the lower end of the range and feels slightly thin given that the server appears to be a scaffolding helper.
The surface is entirely read-only: detection, listing, content retrieval, and diffing are covered, but there is no tool to actually apply/install a template or initialize a project from one. For a Docker scaffolding server that is a notable gap, leaving agents to perform the core write action outside the toolset.