Skip to main content
Glama
LukeLamb

claude-ollama-mcp

by LukeLamb

Related Servers

Alternatives to claude-ollama-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with locally running Ollama models through chat, generation, and model management operations. Supports listing, downloading, and deleting models while maintaining conversation history for interactive sessions.
      358 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A bridge that enables Claude Code to interact with local Ollama instances for text generation, multi-turn chat, and vision-based analysis. It supports model management tasks such as listing, pulling, and showing details, alongside generating text embeddings.
      358 npm
      1
      MIT
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to delegate sub-tasks to a local Ollama model through a single tool that accepts a prompt, optional system prompt, and model name and returns the full generated response. This routes bulk or mechanical work to a free local model so Claude's own tokens are reserved for tasks that need Claude-level reasoning.
      358 npm
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Exposes a local Ollama fleet as MCP tools for Claude Code, enabling model listing, generation, fleet health checks, parallel comparisons, smart host routing, and model pulling across hosts.
      6
      -

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: chat vs generate differentiate by context (with/without history); model management tools (list, pull, delete, show, list_running) are non-overlapping; ollama_status is a standalone health check. No ambiguity in roles.

    Naming Consistency4/5

    Most names follow a verb_noun pattern (e.g., delete_model, list_models, pull_model). 'chat' and 'generate' are single verbs but still actions. 'ollama_status' deviates slightly (noun_noun) but is readable. Overall consistent with minor exceptions.

    Tool Count5/5

    8 tools cover the essential operations for a local Ollama server: model management (list, pull, delete, show, list_running), two inference modes (chat, generate), and a health check. Well-scoped without bloat or deficiency.

    Completeness4/5

    Core CRUD and inference are covered, but streaming support is absent (only non-streaming provided). No tool to adjust model parameters or embeddings. Minor gaps for advanced use, but sufficient for standard workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues