Llama-Bridge
Related Servers
Alternatives to Llama-Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP 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
- AlicenseAqualityDmaintenanceMCP 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.4MIT
- FlicenseNot gradedqualityAmaintenanceAn MCP server that lets Claude Code or any MCP client hand bounded work — code review, boilerplate, commit messages, format conversion, embeddings — to a local GPU model, an OpenAI-compatible endpoint, a router, or a cheap cloud API, so those files never enter the orchestrator's context window. This cuts token spend and quota use while providing a second model to sanity-check results.-
- AlicenseNot gradedqualityDmaintenanceAn 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.15 npmMIT
- AlicenseAqualityDmaintenanceMCP server that enables Claude Code to delegate tasks to DeepSeek and other LLMs, offering 20 tools for code review, analysis, testing, and code generation.201MIT
- AlicenseNot gradedqualityCmaintenanceA 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.1MIT
TDQS
Scored across 6 tools
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.
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.
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.
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.