local-coder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_CODER_MODEL | No | Model name to use when calling the local model server. Defaults to the model name configured in the example. | default_model |
| LOCAL_CODER_API_KEY | No | API key (if required) for the local model server. Defaults to 'local'. | local |
| LOCAL_CODER_BASE_URL | No | Base URL of the OpenAI-compatible local model server. Defaults to http://127.0.0.1:8080/v1. | http://127.0.0.1:8080/v1 |
| ALLOWED_WORKSPACE_ROOT | No | The directory tree the worker is allowed to edit. Set this or ALLOWED_WORKSPACE_ROOTS so the requested workspace is inside an approved directory. | |
| ALLOWED_WORKSPACE_ROOTS | No | Colon-separated list of directory trees the worker is allowed to edit. Use as an alternative to ALLOWED_WORKSPACE_ROOT for multiple roots (supported on macOS/Linux). | |
| LOCAL_CODER_ENABLE_THINKING | No | Set to 'false' to disable thinking/reasoning output from the model. Useful when the model returns no usable text. | true |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delegate_to_local_coderB | Delegate a coding implementation task to the local Qwen worker. The worker can inspect project files, patch code, create files, run tests, and inspect git diff. Codex should review the result afterwards. |
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 1 tool
There is only one tool, so there are no overlapping purposes or risk of selecting the wrong tool. The tool's purpose is clearly stated and unique within this server.
The single tool name uses a clear, descriptive verb-target structure: delegate_to_local_coder. With no other tools to conflict with, there is no naming inconsistency.
A single tool feels too thin for the broad local-coding scope described, which includes inspecting files, patching code, creating files, running tests, and checking diffs. The entire capability set is buried behind one opaque delegation endpoint.
The delegate tool covers task handoff and appears to return results for review, but there are no separate tools for status, cancellation, or finer-grained control of coding operations. This makes the surface usable for simple flows but incomplete for managing the full lifecycle of delegated work.