local-coder-mcp
Related Servers
Alternatives to local-coder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to delegate coding tasks to local Ollama models, reducing API token usage by up to 98.75% while leveraging local compute resources. Supports code generation, review, refactoring, and file analysis with Claude providing oversight and quality assurance.358 npm25AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceA bridge that enables Claude Code to interact with local Ollama instances for text generation, multi-turn chat, and vision-based analysis. It supports model management tasks such as listing, pulling, and showing details, alongside generating text embeddings.358 npm1MIT
- AlicenseAqualityCmaintenanceEnables Claude Code to offload routine code generation and text processing tasks to a local Ollama LLM, saving Cloud API tokens and costs with automatic model selection and security features.1135 npm4Apache 2.0
- AlicenseAqualityBmaintenanceEnables Claude Code to offload small coding tasks to local Ollama machines and free or paid AI providers, choosing the cheapest available option while enforcing quotas, budgets, and Claude's final review.11MIT
- AlicenseNot gradedqualityDmaintenanceExposes local Ollama instances as tools for Claude Code, allowing users to offload code generation, text drafting, and embedding tasks to local GPUs. It supports multi-turn conversations and model management through the Model Context Protocol.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to delegate sub-tasks to a local Ollama model through a single tool that accepts a prompt, optional system prompt, and model name and returns the full generated response. This routes bulk or mechanical work to a free local model so Claude's own tokens are reserved for tasks that need Claude-level reasoning.358 npmMIT
TDQS
Scored across 12 tools
Multiple execution tools overlap heavily: delegate_code_task, execute_local_code_task, execute_local_code_task_compact, execute_local_code_plan, and execute_local_code_plan_compact all route work to a local model, and the differences between compatibility and preferred variants are not crisp. Other tools like health, search, classify, context, and telemetry are distinct.
Most tools use snake_case verb_noun patterns like execute_local_code_task and get_local_run, but local_coder_health and local_coder_telemetry break the verb pattern and mix 'coder' with the 'code' used elsewhere. The compact/compat suffixes are consistent but add clutter.
Twelve tools is a reasonable count for an Ollama-backed coding assistant, and most cover distinct functions. However, several are compatibility or preferred duplicates that could be consolidated, making the set slightly less clean than ideal.
The set covers health, routing classification, workspace discovery/search, context preparation, task/plan execution, result retrieval, and telemetry, so the main workflows have no dead ends. Gaps like cancellation or listing of stored runs are minor and workaroundable.