GitHub
by github
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud★ 34,245MITUpdated 3 days ago
Install
Agent Harnesses
Overview
Description from the maker (original English)
Agent-harness picks, decision guides, setup templates, and skills; live GitHub/HN discovery.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agent-harnesses": {
"command": "uvx",
"args": [
"agent-harnesses-mcp"
]
}
}
}Run this in your terminal
claude mcp add agent-harnesses -- uvx agent-harnesses-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-harnesses": {
"command": "uvx",
"args": [
"agent-harnesses-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"agent-harnesses": {
"type": "stdio",
"command": "uvx",
"args": [
"agent-harnesses-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account RyanAlberts, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 1394 servers in this category
- Published to the registry more recently than 76% of the other 1394 servers in this category
- Basic checks equal to or better than 100% of the other 1394 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Agent Harnesses safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.8.0) reached the registry 14 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
Runs on your computer★ 10,225MITUpdated 16 days ago
Install
Cloudflare MCP
by cloudflare
Cloudflare MCP servers
Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Best of Agent Harnesses and Harness Techniques
🏆 Curated list of AI agent harnesses, orchestration frameworks, and harness techniques for reliable agentic systems.
🌐 Browse the searchable site — one page per harness, filter by capability, autonomy & recovery.
📰 This week : new harnesses and the biggest star gains, every Sunday. To get it as a GitHub notification, click Watch, then Custom, then Releases.
🧰 Templates and Playbooks : copy-paste setup files and step-by-step guides for the harnesses in this list.
🧩 Skills : 10 installable skills that check your own agent setup, including what it can reach, what it claims, and what it spends.
🤖 Agents can query this list — an MCP server ( recommend , pick_harness , …), llms.txt & JSON , so your agent recommends harnesses too.
What is an agent harness?
A model answers; an agent acts. An agent harness is the runtime that turns one into the other: the model thinks, the harness decides what that thinking is allowed to touch.
Simon Willison's definition of the agent itself is the cleanest: "an LLM agent runs tools in a loop to achieve a goal." The harness is everything around that loop: which tools exist, what needs approval, what the model sees each turn, what survives a crash. Andrej Karpathy named the architecture back in 2023: the model is "the kernel process of a new Operating System", and the harness is the rest of that OS, its scheduler, permissions, and memory. The SWE-agent paper proved the stakes by coining the *agent-computer interface*: how tools and feedback are presented changes what a model can do, independent of the model. The field's advice has since converged on investing here rather than in framework plumbing, from Anthropic's build-simple guidance to Jerry Liu's argument that the framework era is over and the layers that matter now are skills, tools, and context quality. Those are the layers this list catalogs.
Why harnesses matter
Better models make harnesses more important: more capabilities mean more failure modes, and production needs retry logic, fallbacks, and validation. Harness quality, not just model quality, determines whether agents actually ship. This list ranks projects by relevance to harness concerns (environment, orchestration, lifecycle, guardrails) and by stars/activity.
The benchmark data now backs this up. On SWE-bench Pro, "swapping the agent harness changed pass@1 more than many model upgrades do" (AINews, Aug 8 2026, citing analysis by @joelniklaus). Same model, different harness: 23% to 52% pass@1 on GLM-5.2, and 15% to 36% on Gemma 4 26B. Harness rankings barely transfer across models (rank correlation -0.05), so a small model in the right harness can approach a much larger model in the wrong one.
The gap is widest on long-horizon work. A bare frontier model was verified at about 30% on ARC-AGI-3; Prime Agent's harness took Opus 5 to 95.5%, and the YC Paper Club talk on why the harness matters more than the model (September 2026) walks through how. The gains come from a new class of self-improving harnesses, not from piling on scaffolding: the best of them stay thin and expose only what the model cannot do for itself. And because rankings barely transfer across models, the harness choice is a pairing that must be re-asked whenever the model changes. Who says so, what they measured, and what the claim does not mean is its own page.
That is the problem the MCP server in this repo solves. Point your agent at it and it can call recommend or pick_harness to choose a harness matched to your model and task, instead of inheriting whichever harness someone else benchmarked.
The landscape at a glance
_Every project in the list, plotted by adoption surface area (the simplicity ↔ capability axis) against GitHub stars. Colors are categories; the largest projects in each tier are labeled._
_The same projects placed by how much unsupervised rope they're designed to give (autonomy) and what happens when a run dies (recovery). In the tables below, ★ marks headless-ready projects and ✱ marks durable ones. Both charts regenerate from the list data on every refresh._
How to Pick a Harness
_Start with the guide, then the head-to-head decision pages — grounded in the same data as the tables below:_
- Why the harness matters more than the model: the measurements (ARC-AGI-3 30% to 95.5% on the same weights), who says so, and what the claim does not mean
- How to pick a harness: six questions that turn this list into a decision, plus the chart to internalize first (the harness moves scores more than the model)
- How to test-drive a harness: the two-week trial protocol, with a fair setup, tasks from your own repos, seven measurements, and the walk-away test
- The best AI agent harnesses in 2026, ranked by category: the top three per category from this week's data, regenerated on every refresh
- OpenClaw vs Hermes — the always-on personal-agent debate: presence vs discipline, plus what the field reports actually say
- Managed vs self-hosted always-on agents: Grok Bot, Claude Managed Agents, QM, OpenClaw, Hermes, and OpenJarvis; who owns the computer and who pays for idle time
- Terminal coding agents — opencode vs Codex vs Gemini CLI vs crush vs goose
- Multi-agent orchestration — OpenAI Agents SDK vs CrewAI vs AutoGen vs LangGraph
- Agent memory layers — Mem0 vs Letta vs claude-mem
- Agent sandboxing: what it is, the key concepts, and the field (E2B vs Daytona vs Modal and more)
- Agent evals (SWE-bench vs inspect_ai vs Terminal-Bench)
- Eval and observability platforms (Langfuse vs LangSmith vs Braintrust vs Phoenix)
- Browser agents (browser-use vs Stagehand vs Playwright MCP vs chrome-devtools-mcp)
- Browser infrastructure (Browserbase vs Steel vs Hyperbrowser)
- Claude Code skill packs (superpowers vs GStack vs get-shit-done vs Anthropic Skills)
- Context files for agents (AGENTS.md vs CLAUDE.md vs skills vs MCP tool search)
Templates and Playbooks
_The list tells you which harness to use. These tell you how to set it up. Templates are files you copy into your project; Playbooks walk you through one task, step by step._
Templates
- One AGENTS.md for every coding agent: One briefing file that Codex, Claude Code, Cursor, OpenCode, GitHub Copilot, Gemini CLI, and Aider all read, so you write your build commands, conventions, and hard rules once instead of once per tool.
- Safe Claude Code settings: permissions and a guard hook: Project settings that stop Claude Code from force-pushing, wiping work, reading secrets, or piping downloads into a shell, while leaving everyday commands alone. Two files, copy and commit.
- Minimal agent harness in Python: A working coding-agent harness in about 180 lines of Python: the loop, three tools, a permission gate, a context file, a turn budget, and a transcript you can resume after a crash. Copy it to learn how harnesses work, or as the start of your own.
Playbooks
- Build your own agent harness: Build a working coding agent in about an hour: a loop, three tools, permissions, a context file, a budget, and crash recovery, in one Python file you fully understand. You finish with the minimal harness template running on your own repo.
- Write one AGENTS.md for every coding agent: Write one briefing file that Codex, Claude Code, Cursor, OpenCode, Copilot, Gemini CLI, and Aider all read, test that each tool actually loaded it, and keep it short enough to help instead of hurt. You finish with the AGENTS.md template filled in for your repo.
Skills
_A skill is a folder your agent loads when a task calls for it. Each one below runs a script on your own setup and hands back a result you can check: what your agent can reach, which of its claims had no proof, where your tokens went. They run on your machine, and anything that changes a file or spends money waits for your yes._
Pick a harness
- Test-drive coding agents on tasks from your own repo: Runs Claude Code, Codex, and Gemini CLI on tasks taken from your own git history, scores each one with your repository's tests, and reports how many tasks each passed, the dollars per pass, the minutes, and the size of each change.
Set it up
- Check which instruction files your coding agents load: See which instruction files Claude Code, Codex, Gemini CLI, OpenCode, Cursor, GitHub Copilot, and Aider load from your repo, what each one cuts or skips, and whether the commands in those files still work.
- Grade your MCP tools the way a model reads them: Point it at an MCP server or a saved tool list to grade each tool's purpose, parameters, annotations, and token size, or let it find th
Only the beginning is shown; read the rest in the repo