mcp-llama-swap
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLAMA_SWAP_CONFIG | No | Path to configuration JSON file. Overrides default config path. |
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 |
|---|---|
| list_modelsA | List available llama.cpp model configurations and their load status. |
| get_current_modelA | Get the currently loaded llama.cpp model. |
| swap_modelA | Swap to a different llama.cpp model. Unloads any currently loaded model, loads the requested one, and waits for the health endpoint to confirm readiness. Args: model: Alias of the model to load |
| create_model_configA | Generate a new service config for a llama-server model. Creates a launchd plist (macOS) or systemd unit (Linux) that can be used with swap_model. Args: name: Short alias for the model (e.g., "coder", "planner") model_path: Absolute path to the GGUF model file context_size: Context window size (default: 4096) gpu_layers: Number of GPU layers, -1 for all (default: -1) port: Port for llama-server (default: 8000) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| swap-workflow | Guided workflow for planning with a reasoning model, then implementing with a coding model. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| config_resource | Current llama-swap configuration. |
| status_resource | Current model status and health. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct function: creating configs, listing models, getting the current model, and swapping to a different model. No overlap exists.
All tool names follow a consistent verb_noun pattern in snake_case (create_model_config, get_current_model, list_models, swap_model), making them predictable.
Four tools is well-scoped for the server's purpose of managing llama.cpp model configurations and swapping. Each tool serves a necessary role without redundancy.
The set covers the key operations: creating a config, listing models, checking the current model, and swapping. However, there is no tool to delete or update a model config, which is a minor gap.