Skip to main content
Glama

Related Servers

Alternatives to local-llm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code and other MCP clients to offload bounded tasks such as code review, test stubs, commit messages, and format conversion to local or cheaper cloud LLMs, cutting token usage while the primary model remains the orchestrator.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other MCP clients to offload bounded work—code review, test stubs, boilerplate, commit messages, format conversion, embeddings—to a local GPU model or a cheaper cloud, OpenAI-compatible endpoint. Source files are read by the server rather than the main model, cutting token spend while the orchestrating model keeps planning and verifying.
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code and Claude Desktop to delegate bounded, disposable tasks to local or cheap cloud models, with model scoring, guardrails, and cost-saved tracking.
      53
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and other MCP clients to hand off bounded work — code review, test stubs, boilerplate, commit messages, docs, format conversion, embeddings — to local or cloud OpenAI-compatible models while the main assistant keeps planning and QA. Keeps large source files out of the orchestrator's context window, cutting token costs and providing a cheap second opinion on code.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other MCP clients to hand bounded work — code review, test stubs, commit messages, docs, format conversion, mock data, embeddings — to a local GPU model or a cheap cloud/OpenAI-compatible endpoint, so file contents are sent straight to that model instead of entering the main AI platform's context window. This cuts token spend dramatically while giving users a second model for reviewing code, with the orchestrating assistant still checking every result.
      MIT

    TDQS

    B3.1/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct aspects (querying, listing, configuration, status). The alias list_models for list_local_models is redundant but clearly documented, causing minor potential confusion.

    Naming Consistency5/5

    Tools consistently follow verb_noun pattern with underscores (e.g., ask_local_model, list_backends, set_backend). The sole exception local_status is descriptive and fits the pattern.

    Tool Count5/5

    9 tools cover the core operations for managing local LLM backends, guards, and queries without being excessive or insufficient.

    Completeness4/5

    The tool set covers CRUD for backends, querying, and configuration. A minor gap is the lack of a dedicated tool for detailed backend info, but list_backends provides status.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues