local-executor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_LLM_BASE_URL | No | Base URL of the local LLM backend (e.g., http://10.0.0.42:8080/v1) | |
| LOCAL_LLM_MODEL_FAST | No | Model name for the fast tier (e.g., qwen3.5-4b-q8_0) | |
| LOCAL_LLM_MODEL_QUALITY | No | Model name for the quality tier (e.g., qwen3.6-35b-a3b-q8_0) |
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 |
|---|---|
| delegate_codeA | Delegate a self-contained, mechanical code-generation subtask to a local LLM to save frontier-model tokens. GOOD for: boilerplate, scaffolding, repetitive CRUD, test stubs, format/data transformations, bulk edits with a clear rule, Odoo models/views/manifests. NOT for: subtle logic, debugging, cross-file reasoning, or security-sensitive code (do those yourself). Provide a precise spec plus any context the worker needs; it returns ONLY the generated artifact. You, the planner, verify and integrate it. |
| list_local_modelsA | List the model IDs currently available on the local llama-swap endpoint. Use it to pick a model or to confirm the backend is reachable. |
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 2 tools
The two tools have completely distinct purposes: delegate_code handles code generation subtasks, while list_local_models checks available models. There is zero overlap or ambiguity.
Both tool names follow a clean verb_noun pattern (delegate_code, list_local_models), using snake_case consistently. The naming is predictable and easy to understand.
With only 2 tools, the server feels minimal. However, the narrow scope of 'local execution' justifies a small surface; it is borderline but not excessive.
For its stated purpose, the server covers the core delegation flow and model discovery. A status or cancel tool would be a minor enhancement, but no critical gaps exist.