ollama-fleet-mcp
Related Servers
Alternatives to ollama-fleet-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes local Ollama as an MCP server so Claude can delegate drafting, summarization, translation, code review, error explanation, model listing, health checks, and file reading to local models via stdio or HTTP.430 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients such as Claude Desktop and Cline to manage and interact with local or cloud-hosted Ollama models via tools for model administration, chat, text generation, embeddings, and web search/fetch.882 npmAGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to manage, run, and interact with local or cloud LLM models through exposed tools for listing, pulling, generating, chatting, embeddings, and web search/fetch. Supports Claude Desktop, Cline, and hybrid local/cloud setups.882 npmAGPL 3.0
- AlicenseNot gradedqualityAmaintenanceExposes the complete Ollama SDK as MCP tools, enabling MCP-compatible clients such as Claude Desktop and Cline to list, pull, create, and delete models, run chat and text generation, produce embeddings, and perform web search and fetch against local or cloud Ollama instances. It supports hybrid local-plus-cloud configurations with API-key authentication, automatic retries, and type-safe validation.882 npmAGPL 3.0
- AlicenseNot gradedqualityAmaintenanceExposes the complete Ollama SDK as MCP tools so compatible AI assistants can manage models, generate text, chat, create embeddings, and use cloud web search/fetch. Supports local, cloud, and hybrid deployments for integrating local LLMs with applications like Claude Desktop and Cline.882 npmAGPL 3.0
- AlicenseNot gradedqualityAmaintenanceExposes the complete Ollama SDK as MCP tools, letting MCP-compatible clients manage, run, and chat with local or cloud-hosted LLM models, generate embeddings, and perform web search and page fetching. Supports model listing, pulling, creating, and deletion, plus hybrid local-and-cloud configurations.882 npmAGPL 3.0
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: list_models for inventory, fleet_health for status, pull_model for downloading, compare_models for side-by-side comparison. However, generate and smart_generate both perform text generation and differ only in routing logic (explicit host vs auto-route), which could cause misselection.
Naming conventions are mixed: list_models and pull_model use verb_noun, generate is a bare verb, fleet_health is a noun phrase, smart_generate is adjective_verb. The names are readable but do not follow a single consistent pattern.
Six tools is a well-scoped set for an Ollama fleet management server, covering the essential operations of listing models, generating responses, checking health, comparing models, and pulling models without unnecessary bloat.
The tool surface covers the core workflows: inventory (list_models), generation (generate, smart_generate), comparison (compare_models), health monitoring (fleet_health), and model acquisition (pull_model). Missing operations like delete_model or model detail inspection are minor gaps that agents can work around.