MCP Ollama
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 all downloaded Ollama models |
| show_modelA | Get detailed information about a specific model |
| ask_modelA | Ask a question to a specific Ollama model |
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 3 tools
Each tool has a clearly distinct purpose: listing models, showing model details, and asking a model a question. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern using snake_case: list_models, show_model, ask_model. This is predictable and easy to remember.
With 3 tools, the server is well-scoped for its purpose of interacting with Ollama models. Each tool earns its place, and the count falls within the typical 3-15 range.
The tools cover the core workflow of listing, inspecting, and querying models. Missing pull/delete operations are minor gaps since the server focuses on using existing models rather than managing the full model lifecycle.