Skip to main content
Glama

Related Servers

Alternatives to local-llm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables cloud-based MCP clients to delegate privacy-sensitive or large-output tasks to a local LLM, returning sanitized placeholders or digested summaries so private data never leaves the user's network.
      8
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides an MCP endpoint that lets clients like Google Antigravity and Claude Desktop dispatch LLM tasks to local GPU models with automatic hardware-adaptive routing and cloud fallback, enabling near-zero token cost execution.
      3
      4
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code or any MCP client to delegate bounded tasks such as code review, boilerplate, and documentation to local or cloud OpenAI-compatible LLMs. This reduces token usage by keeping large source files out of the main model's context while allowing results to be reviewed by the orchestrator.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Code to delegate bounded tasks like code review, boilerplate generation, commit messages, format conversion, and embeddings to local or cloud OpenAI-compatible LLMs, reducing token costs while keeping the main model in control.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Lets an MCP client hand bounded work such as code review, boilerplate, commit messages, format conversion or embeddings to a local or cloud OpenAI-compatible LLM, so file contents never enter the orchestrating model's context and token costs drop. It also provides a second model to sanity-check code and drafts while the main assistant keeps planning and tool use.
      -

    TDQS

    A4.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose (run a task on a local LLM) is unambiguous and clearly stated.

    Naming Consistency4/5

    With a single tool named `local_llm`, there is no convention to break, so consistency is trivially satisfied. It uses a clear snake_case noun rather than a verb_noun pattern, which is a minor deviation but perfectly readable.

    Tool Count4/5

    A single, argument-rich tool is a reasonable fit for a narrowly scoped domain like invoking a local LLM, and nothing obvious is bolted on unnecessarily. It sits at the low end of the typical range, but the domain genuinely appears to need only one entry point.

    Completeness4/5

    The tool's arguments cover the core lifecycle for its purpose: prompt, context files, output redirection, system prompt, token limit, and thinking mode. Minor gaps exist (e.g. no way to list or select available local models or check readiness), but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues