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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable assistants such as Codex and Claude to delegate bounded text work — summaries, structured extraction, classification, rewrites, code drafts and log digestion — to locally hosted Ollama models, with conservative routing that keeps small or sensitive tasks with the caller and private-result artifacts for sensitive output.
      MIT
    • 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
      C
      maintenance
      Enables delegating mechanical or high-volume subtasks to a local LLM through an MCP tool, letting the assistant query the local model without using its own output tokens for content.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients like Claude Code to delegate bounded work — code review, boilerplate, commit messages, format conversion, embeddings — to a local GPU model or a cheaper cloud endpoint, keeping large file contents out of the orchestrator's context window. This cuts token costs dramatically while providing a second model for independent review.
      -

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes—delegate handles text/file analysis, run digests shell output, artifact slices raw material, and status reports state. However, delegate and run both accept commands, and enable vs set_mode both touch activation/mode, creating occasional ambiguity.

    Naming Consistency3/5

    The shared local_llm_ prefix gives the set a strong family resemblance, but the second word is inconsistent: nouns (artifact, disclosure, status), verbs (compact, delegate, enable, run), and one verb-noun (set_mode) are mixed rather than following a single pattern.

    Tool Count5/5

    8 tools is a well-scoped size for a local LLM proxy server. Each tool maps to a distinct part of the workflow—opt-in, mode control, delegation, shell digestion, artifact access, memory compaction, disclosure settings, and status—without redundancy.

    Completeness4/5

    The set covers the full lifecycle: enabling the server, switching modes, delegating over text/files/commands, retrieving raw artifacts, compacting memory, and checking status. Minor gaps like explicit cancellation or artifact list/delete are workable since calls are synchronous digests and status exposes artifact counts.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing