Tandem MCP
Related Servers
Alternatives to Tandem MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceAn MCP execution layer that lets capable AI models safely control a developer workstation for file edits, terminal and process execution, Git operations, language-server analysis, browser and Windows UI automation, media processing, job/resource control, and checkpointing. It also coordinates durable single- or multi-agent tasks across providers with leases, dependency graphs, evidence logs, repair loops, and separate verification gates.1281ISC
- AlicenseNot gradedqualityBmaintenanceEnables a cloud coding agent to delegate a focused coding task to a local Ollama or OpenAI-compatible model through a bounded workspace, file allowlist, and required external checks. Changes are applied only after verification against the declared scope, with failed post-apply checks rolled back and the rollback itself confirmed.66 PyPI11MIT
- AlicenseNot gradedqualityFmaintenanceEnables a primary coding agent to delegate bounded implementation and repair tasks to a local OpenAI-compatible model that edits a copy of the project, runs configured checks, and returns artifacts for review. Exposes stdio tools for capability discovery, task submission, progress polling, artifact reading, and cancellation.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, permissioned development workflows from compatible AI clients, including filesystem editing, interactive terminals, durable jobs, Git operations, and semantic browser testing.37 npm1Apache 2.0
- AlicenseAqualityBmaintenanceEnables Claude Code to hand off mechanical work — file edits, code lookups, and lint triage — to a local Ollama model that reads and edits files directly, so file contents never enter Claude's context. Returns only a compact receipt, and reports success only after the change passes a deterministic syntax/project gate, rolling back and escalating on failure.4MIT
- AlicenseAqualityBmaintenanceEnables AI agents to delegate complex coding tasks, refactorings, and automated code reviews to OpenAI Codex and Google Antigravity CLIs, running them autonomously in YOLO mode with process supervision.6MIT
TDQS
Scored across 19 tools
The core delegation lifecycle (delegate, delegate_many, job_status/continue/stop/diff/rollback/evidence/feedback) is cleanly separated by verb, and executor_status vs executor_probe are distinguishable. The main blur is in the read/digest cluster: ask, digest_file, digest_many and extract_from_file all route content to the executor, so an agent must parse descriptions to know whether it wants a prose answer, a per-file survey, or schema-bound structured data. lessons vs lesson_add vs job_feedback's lesson parameter also sit close together but stay workable.
Everything is snake_case and grouped by prefix (job_*, digest_*, executor_*), which makes scanning predictable. Minor deviations: bare 'delegate', 'ask' and 'lessons' break the verb_noun pattern, and lesson_add/lessons are an asymmetric create/list pair. Nothing rises to a real inconsistency problem.
19 tools is on the heavy side, but the surface is broad (delegation, job lifecycle, file digests, lessons, executor introspection, ledger) and nearly every tool maps to a distinct operation rather than a convenience wrapper. The weight comes from describing a contract protocol rather than from redundancy, though trimming the digest cluster would be defensible.
The delegation lifecycle is unusually complete: dispatch, batch, poll, continue, stop, diff, rollback, evidence, verdict, plus persistent lessons and usage reporting. The noticeable gap is enumeration: job_status and the job_* tools all require a job_id, but there is no job_list/jobs tool to discover ids after a server restart or in a later session, forcing the agent to remember them.