A
licenseA
qualityD
maintenanceEnables seamless integration between Ollama's local LLM models and MCP-compatible applications, supporting model management and chat interactions.
13
787 npm
172
AGPL 3.0
MCP Ollama Consult Server
by Atomic-Germ
Related Servers
Alternatives to MCP Ollama Consult Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceIntegrates Ollama's local AI models with MCP clients, enabling listing models, viewing model details, and asking questions to models.3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to offload mechanical, high-token work to local Ollama models through MCP, with role-based model discovery, batch processing, and file-aware inputs.4MIT
- AlicenseBqualityDmaintenanceMCP Ollama server integrates Ollama models with MCP clients, allowing users to list models, get detailed information, and interact with them through questions.334MIT
- AlicenseBqualityDmaintenanceA universal MCP server that integrates with local Ollama instances, enabling AI-powered chat, model management, and text generation from any MCP-compatible IDE or application.676 npm3MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for delegating coding tasks to local Ollama models. Supports listing models and executing tasks with file writing capabilities.787 npmAGPL 3.0
TDQS
B3.4/5.0
Scored across 5 tools
Disambiguation3/5
The purposes of list_ollama_models and remember_context are distinct, but consult_ollama, compare_ollama_responses, and sequential_consultation_chain heavily overlap. All three involve querying models, differing mainly in whether responses are combined or chained, which could lead to agent confusion.
Naming Consistency3/5
Tools mostly follow a snake_case verb_noun pattern (list_ollama_models, remember_context, compare_ollama_responses), but 'sequential_consultation_chain' breaks the verb-first pattern with an adjective-noun structure. Also, 'consult_ollama' is a general verb that overlaps with others, making the naming less distinctive.
Tool Count5/5
With only 5 tools, the server is well-scoped and each tool seems to have its place, though the overlap among core consultation tools slightly reduces the necessity of having three separate ones. Still, it's a small, manageable set that fits the server's purpose.
Completeness4/5
The server covers a typical consultation workflow: listing available models, querying them, comparing responses, chaining consultations, and maintaining context. A minor gap is the lack of a tool to explicitly clear context or manage sessions, which agents might need for long-running interactions.
Maintenance
ActivityInactive
ResponsivenessNo issues