spillway-mcp
Related Servers
Alternatives to spillway-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides an MCP endpoint that lets clients like Google Antigravity and Claude Desktop dispatch LLM tasks to local GPU models with automatic hardware-adaptive routing and cloud fallback, enabling near-zero token cost execution.34MIT
- 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.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to dispatch queries to the most suitable model among 70+ LLMs by scoring intent, budget, cost, and latency, returning structured routing decisions with execution telemetry. It runs as a zero-dependency Python MCP server that plugs into Claude Desktop, Cursor, and other MCP-compatible clients.8-
- AlicenseAqualityDmaintenanceOne MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.234MIT
- AlicenseNot gradedqualityCmaintenancePrivacy-first local MCP hub for coordinating multiple AI providers from Claude Code, supporting local Ollama seats and cloud providers with safety routing.MIT
- AlicenseNot gradedqualityAmaintenanceLets Claude Code or any MCP client hand bounded work such as code review, boilerplate generation, commit messages, and format conversion to a local GPU model, an OpenAI-compatible cloud API, or a LiteLLM/OpenRouter router, so those files never enter the orchestrator's context window. This cuts token cost by roughly 93% on read-heavy tasks and provides a second model for reviewing code, while the main AI platform keeps the planning and judgement calls.MIT
TDQS
Scored across 16 tools
The prefix scheme separates three backends (codex_, agy_, local_), but each backend exposes near-parallel operations — codex_research vs agy_delegate_research, codex_followup vs agy_session_followup, codex_status vs agy_status, codex_cancel vs agy_cancel — so an agent must read the routing rules to pick correctly. Descriptions do a lot of work with explicit 'DO NOT USE FOR' clauses, but the overlapping research/scout/draft/edit triad (local_file_scout vs agy_delegate_research vs local_draft_leaf_code vs agy_delegate_edit) remains genuinely easy to misselect.
A consistent three-prefix scheme (codex_/agy_/local_) groups tools predictably, which is a real strength. Within groups, however, conventions are mixed: verb_noun (agy_delegate_edit, agy_spawn_swarm) sits beside noun-phrase tools (agy_status, agy_job_result, codex_job_result) and odd forms like local_file_scout (noun_verb) and local_exec_and_triage.
Sixteen tools is at the borderline of heavy, and the cost is amplified because the surface duplicates the same lifecycle (research, follow-up, status, cancel, job-result) across two agent backends plus a local tier. Each tool is justified individually, but the aggregate feels larger than the underlying domain requires.
Coverage is broad: research, editing, multi-file delegation, drafting, command execution, session follow-up, job retrieval, cancellation, status, and workspace configuration are all present, so most workflows have a path forward. Minor gaps include no generic file read/list or job-listing operation independent of the status tools, and Codex offers no edit path at all.