Local Developer Toolbox MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOOLBOX_LOG_DIRS | No | One or more absolute directories for log search access, separated with the operating system's path separator (`;` on Windows, `:` on macOS and Linux). If unset, the server's current working directory is the only allowed root. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_local_logsA | Search local log files for a regular-expression pattern. Searches only within TOOLBOX_LOG_DIRS, or the server's current working directory when that variable is unset. Very long lines are skipped, and truncated indicates when a safety or result limit stopped the search. |
| inspect_docker_containerA | List local Docker containers and their current status. Running containers are shown by default. |
| format_json_payloadA | Clean up and pretty-print a JSON object or array. Accepts a JSON code fence or surrounding prose and removes trailing commas, while preserving JSON values and reporting cleanup details. |
| git_auto_commitA | Call first without commitMessage to inspect the repository status and a bounded diff preview. Then generate a Conventional Commit message from those changes and call again with commitMessage to stage all non-ignored repository changes and commit them. This tool modifies Git state; only commit after reviewing the preview. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct area: Docker container listing, local log searching, JSON formatting, and Git commit creation. There is no functional overlap between any pair of tools, so an agent can easily select the right one.
Three tools follow a clear verb_noun pattern (inspect_docker_container, search_local_logs, format_json_payload), while git_auto_commit uses a domain-prefixed noun_verb structure. This is a minor deviation but still readable and predictable overall.
Four tools is well-scoped for a local developer toolbox, and each tool earns its place by covering a distinct utility. The count avoids both thinness and bloat.
The surface is functional but notably thin in key areas: the Docker tool only lists containers rather than inspecting details, logs are only searchable, and Git only supports commit (with preview) rather than status/diff separately. These gaps are workable but limit the toolbox's completeness for its stated broad purpose.