F
licenseNot graded
qualityC
maintenanceEnables AI agents to access a codebase context, select relevant files, and route queries to the appropriate AI model based on complexity, all through an MCP interface.
-
Model-Shunt
Related Servers
Alternatives to Model-Shunt
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that reduces token consumption in AI coding assistants by up to 90% via structural reads, PreToolUse hooks, and tp-\* subagents.25189 npm5MIT
- AlicenseNot gradedqualityDmaintenanceServes structured code context via MCP, enabling AI agents to understand codebases with dependency graphs and significantly reduce token usage.13 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that reduces AI agent token usage by up to 90% through intelligent context compression. Enables efficient code exploration, multi-file refactoring, and debugging by providing tools for smart reading, searching, and managing code context.4MIT
- AlicenseAqualityDmaintenanceAn MCP server that offloads bulk coding tasks to local LLMs, allowing Claude Code to delegate repetitive work like boilerplate generation and code polishing while preserving its context for complex reasoning.101MIT
- AlicenseAqualityCmaintenanceMCP 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
TDQS
A3.8/5.0
Scored across 3 tools
Disambiguation4/5
The three tools have distinct purposes: bulk_read handles file reading and summarization, code_write handles code generation, and get_available_models handles model discovery. There is minor potential confusion between bulk_read and code_write since both involve file operations, but their core functions are clearly separated.
Naming Consistency3/5
Tool names use a mix of conventions: bulk_read and code_write follow a noun_verb pattern, while get_available_models follows a verb_adjective_noun pattern. The naming is readable and descriptive, but the inconsistent verb placement (bulk_read vs get_available_models) creates minor inconsistency.
Tool Count3/5
Three tools is on the low end but appropriate for a focused utility server that handles delegated reading, writing, and model selection. The count feels slightly thin for a server that could benefit from additional tools like a direct file write or model configuration tool, but it is not unreasonable.
Completeness3/5
The server covers the core workflow of reading files, generating code, and selecting models, but there are notable gaps. There is no tool for direct file writing (code_write writes to disk but only for boilerplate), no tool for updating existing code, and no way to configure or manage the worker provider beyond model discovery.
Maintenance
ActivityMaintained
ResponsivenessNo issues