Skip to main content
Glama
shreyashp77

Llama-Bridge

by shreyashp77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Llama-Bridge

No user-submitted related servers found.

    Related Servers

    • mcp-local-llama

      chrishorne74
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that delegates mechanical tasks like summarization, classification, extraction, and drafting to a local Llama.cpp LLM, serving as a cost-optimization layer while Claude handles reasoning and quality control.
      MIT

    • local-llm-mcp

      drangoht
      A
      license
      A
      quality
      C
      maintenance
      MCP server connecting Claude Code to LM Studio, delegating token-expensive tasks to a local model while keeping the cloud model in control. It reduces cloud context usage by reading files locally and returning only the processed results.
      4
      MIT

    • claude-bridge-mcp

      millanrp25-dot
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.
      7 npm
      MIT

    • Apprentice

      m-555
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that delegates coding tasks to local Qwen and cloud Gemini models, enabling orchestrators like Claude Code to offload routine code generation and receive verified results with automatic correction logging.
      1
      MIT

    • local-llm

      pakkio
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets Claude Code delegate trivial, standalone questions to a local Gemma 4 model via llama.cpp, saving paid tokens.
      -
    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.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct workflow: implementation, test generation, refactoring, bug fixing, documentation, and health checking. Descriptions clearly separate concerns, so an agent should be able to select the right tool without confusion.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun snake_case pattern: implement_code, generate_tests, check_local_model_health, refactor_code, fix_code, generate_docs. The naming convention is uniform and predictable.

    Tool Count5/5

    Six tools is a well-scoped set for a local-model code-assistance bridge. Each tool earns its place, covering the main code-generation and modification workflows without redundant or unnecessary additions.

    Completeness4/5

    The toolset covers the core lifecycle of generating, testing, refactoring, fixing, and documenting code, plus a health check. A minor gap is the lack of a general code review or explanation tool, but agents can work around it with the existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources