Skip to main content
Glama
Obrais-cloud

ollama-fleet-mcp

by Obrais-cloud

Related Servers

Alternatives to ollama-fleet-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes 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.
      221 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A small MCP server that turns a shared Ollama box into a team resource for Claude Code, providing typed tools and delegated read-only repo exploration using local models.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Unified MCP server for managing local model runtimes (Ollama, LM Studio, etc.), enabling provider-agnostic discovery, lifecycle management, hardware-fit checks, and delegated inference.
      16
      18 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes local Ollama instances as tools for Claude Code, allowing users to offload code generation, text drafting, and embedding tasks to local GPUs. It supports multi-turn conversations and model management through the Model Context Protocol.
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      A minimal Python MCP server that enables Claude Code to call local Ollama models (e.g., gemma3) as a tool, routing low-stakes work off the API and onto a homelab.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables orchestrating multiple AI CLI agents (Codex, Grok, Claude, etc.) via Claude Code, providing tools for dispatching tasks, broadcasting, debating, and managing jobs through a local MCP server.
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation4/5

    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 Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues