best-of-Agent-Harnesses MCP server

Full record for one project by github_id (e.g. "anomalyco/opencode").

Recommend agent harnesses for a use case, ranked from a hand-curated list of 100+. use_case: what you want to do, e.g. "terminal coding agent", "drop-in memory layer", "evaluate agents on coding benchmarks". max_complexity: cap on adoption surface — one of "super simple", "mostly simple", "slightly complex", "complex" (default: no cap). min_autonomy: require at least this designed autonomy regime — one of "step-gated", "checkpoint-gated", "bounded", "headless" (e.g. "bounded" means "must be able to run a whole task unattended"; excludes n/a entries). min_recovery: require at least this failure-recovery tier — one of "none", "retry", "resumable", "durable" (excludes n/a entries). open_source_only: drop projects with restricted or unknown licenses. Returns JSON: ranked picks with a one-line reason each.

Opinionated single recommendation for a need — a decision, not a list. Where pick_harness returns a ranked shortlist, recommend commits: one top pick with the reason, up to two alternatives, any listed harnesses to AVOID for this need (archived, or flagged for star manipulation — with why), and the most relevant decision guide to read next. Use this when an agent or user asks "what should I actually use for X?". need: plain-language description of what you're building, e.g. "an always-on personal assistant in my chat apps" or "evaluate a coding agent on benchmarks". language: optional — restrict to a language/runtime tag (python, javascript, typescript, rust). must_run_unattended: require a harness designed to run a whole task with no human in the loop (autonomy bounded or headless). open_source_only: drop restricted or unknown-license projects. Returns JSON: {recommendation, alternatives, avoid, see_also, source}.

The list's head-to-head decision guides (e.g. "OpenClaw vs Hermes", "How to pick a harness") — slug, title, and summary for each. Fetch the full text of one with get_comparison(slug).

Keyword search across all 100+ projects (name, description, tags, category). Returns JSON: matching projects sorted by relevance then stars.

Full markdown of one decision guide by slug (see list_comparisons). Guides cover architecture trade-offs, field reports, and the post-June-2026 billing reality — use them when a user is choosing between specific harnesses, not just browsing.

The list's 10 categories and 14 curated use-case intents, with project counts.