Skip to main content
Glama
Rikiza89

ollama-mcp-delegate

by Rikiza89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ollama-mcp-delegate

No user-submitted related servers found.

    Related Servers

    • Ollama MCP Server

      Jadael
      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.
      330 npm
      24
      AGPL 3.0

    • claude-token-saver-mcp

      BlackFoil
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to offload routine code generation and text processing tasks to a local Ollama LLM, saving Cloud API tokens and costs with automatic model selection and security features.
      11
      77 npm
      4
      Apache 2.0

    • ollama-mcp-server

      Shahriar-Hossein
      A
      license
      Not graded
      quality
      C
      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.
      330 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: edit (write), explain (read-only query), verify (gate runner), and status (health check). The descriptions explicitly delineate when to use each and even contrast them against native Read/Edit/Bash, leaving no meaningful overlap.

    Naming Consistency5/5

    All four tools follow a strict local_<verb> pattern (local_edit, local_explain, local_verify, local_status). The convention is predictable and unambiguous throughout.

    Tool Count5/5

    Four tools is well-scoped for a delegation server, and each one earns its place covering a distinct phase of the delegate workflow. No redundancy or filler.

    Completeness4/5

    The surface covers the core delegation lifecycle: availability check, read-only queries, edits, and verification. Minor gaps exist (e.g. no explicit undo/rollback or batch-edit operation), but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources