Skip to main content
Glama

Related Servers

Alternatives to ollama-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to delegate coding tasks to local Ollama models, reducing API token usage by up to 98.75% while leveraging local compute resources. Supports code generation, review, refactoring, and file analysis with Claude providing oversight and quality assurance.
      27
      AGPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code to offload mechanical development work—tests, git operations, pull requests, summaries, project search, code review, and browser or screen control—to local Ollama models with optional free cloud fallbacks. It returns concise results to reduce token usage while keeping execution on the user's own machine.
      37
      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

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    The set splits into two clearly distinguishable clusters: model delegation (run_ollama_task, list_ollama_models, summarize_output) and code-index lookup (outline_file, read_symbol, find_symbol, find_references, find_callers, find_callees, hybrid_retrieve). Within the symbol cluster, find_references and find_callers are adjacent concepts, but descriptions clarify that one covers resolved references and the other covers call sites only. summarize_output is essentially a specialisation of run_ollama_task, so mild overlap remains, but the other boundaries are clear.

    Naming Consistency4/5

    Nine of the ten tools use snake_case with an action prefix (run_/list_/summarize_/outline_/read_/find_) and a concrete object. hybrid_retrieve breaks the pattern, because its prefix is an adjective rather than a verb, so it is the one moderate deviation. The naming is otherwise predictable and readable.

    Tool Count5/5

    Ten tools is well within the ideal range and each tool covers a distinct operation across the two capabilities. Nothing looks like junk or a duplicate entry, and the server does not overwhelm the agent with tool choice.

    Completeness4/5

    The symbol-navigation surface (outline, read, find by name, references, callers, callees, hybrid retrieval) is unusually complete for a code-indexing capability. The main gaps are an explicit tool to list or read files from a repository and an index-status or refresh tool; the LLM-delegation side also lacks a model-pull or conversation-continuation operation, but agents can work around these gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data