local-llm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_LLM_MODEL | No | Model name to request from the local server. | first model from /v1/models |
| LOCAL_LLM_API_KEY | No | Optional API key sent as Authorization: Bearer ... if set. | |
| LOCAL_LLM_TIMEOUT | No | Timeout in seconds; the first call may include model loading. | 600 |
| LOCAL_LLM_BASE_URL | No | OpenAI-compatible base URL of the local LLM server. | http://127.0.0.1:8080/v1 |
| LOCAL_LLM_ALLOWED_ROOTS | No | Colon-separated directories that files may be read from and written to. | ~, /tmp, $TMPDIR, and the macOS per-user temp dir |
| LOCAL_LLM_MAX_INPUT_CHARS | No | Limit for prompt + files in characters. | 60000 |
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 |
|---|---|
| local_llmA | Run a task on a local LLM on this machine. Nothing is sent to the cloud. Use it for (1) private data that must not leave the machine: pass file paths in Files must be under the home directory or /tmp and must not be hidden (no path component starting with "."). Args: prompt: The instruction for the local model. Write it self-contained; the model sees nothing else. files: Text files to include after the prompt (UTF-8). Total input is capped (~60k characters). output_path: If set, the answer is written to this new file and only a short notice is returned, so even the answer stays out of the conversation. Existing files are never overwritten. system: Optional system prompt. max_tokens: Maximum tokens to generate. thinking: Enable the model's thinking mode, if it has one (slower, sometimes more accurate). |
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 is no possibility of confusion or misselection between tools. Its purpose (run a task on a local LLM) is unambiguous and clearly stated.
With a single tool named `local_llm`, there is no convention to break, so consistency is trivially satisfied. It uses a clear snake_case noun rather than a verb_noun pattern, which is a minor deviation but perfectly readable.
A single, argument-rich tool is a reasonable fit for a narrowly scoped domain like invoking a local LLM, and nothing obvious is bolted on unnecessarily. It sits at the low end of the typical range, but the domain genuinely appears to need only one entry point.
The tool's arguments cover the core lifecycle for its purpose: prompt, context files, output redirection, system prompt, token limit, and thinking mode. Minor gaps exist (e.g. no way to list or select available local models or check readiness), but agents can work around these.