llama-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLAMA_URL | No | llama-server base URL. Equivalent to the --url option. | http://localhost:8080 |
| LLAMA_MODEL | No | Model id to use when a tool call names none. Equivalent to the --model option. Required when llama-server runs in router mode (started without -m/-hf, offering several models); chat, complete and tokenize also take a per-call model argument. | |
| LLAMA_API_KEY | No | Sent as a bearer token, for a llama-server started with --api-key. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chatC | Send a prompt to the local model through its chat template and return the reply. |
| completeB | Continue raw text with the local model, with no chat template applied. |
| tokenizeC | Return the model's token ids for |
| modelsA | List the models llama-server offers, with their status. |
| healthA | Report whether llama-server is up and has a model loaded. |
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 5 tools
chat and complete both send text to the model and return output, so their boundary rests entirely on the chat-template distinction, which the descriptions do clarify. tokenize, models, and health are each clearly distinct from that pair and from each other.
All names are single lowercase words in a consistent casing style, which keeps them readable. However, the set mixes bare verbs (chat, complete, tokenize) with bare nouns (models, health) with no predictable verb_noun pattern.
Five tools is well-scoped for a thin wrapper over a local llama-server: two generation modes, tokenizer access, model listing, and a health probe. Each tool earns its place with no obvious redundancy.
Core inference and diagnostics are covered, but common llama-server capabilities are absent: embeddings, explicit model selection/load-unload for router mode, and detokenization. Agents can still work around these gaps but will hit dead ends for embedding workflows.