PlugWiki
Harness logo

Autonomous Harness MCP Server: Let Your Assistant Start and Watch Other Coding Agents

OfficialLocal
Getnpm@autonomous-ai/harness-mcpautonomous-ai/openharness

Lets Claude Code, Codex, Cursor and other assistants start more coding agents in Harness, wait for them and read their answers.

Harness is a native app from Autonomous that runs coding agents in sessions you can watch. Its MCP server lets one assistant start those agents, wait for them, read their answers and close them. An assistant can only close or give work to agents it started itself.

It needs Harness installed first, on macOS or Linux. The npm package only finds your harness command and runs harness mcp. If Harness is missing, it offers a single setup tool that explains how to install it.

Good for

  • Developers who want a second opinion from another coding agent
  • People running parallel agent tasks across their own machines
  • Teams already using the Harness app to watch agents

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install Harness MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Harness MCP server to Claude Code. Run this command:
    
    claude mcp add harness -- npx -y @autonomous-ai/harness-mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Harness installed (macOS or Linux), Node.js 18+.

Read-only mode: No read-only mode.

Install Harness first with curl -fsSL https://harness.autonomous.ai/cli/install.sh | bash, then run harness start. The npm package only runs harness mcp from that install, or from the path in HARNESS_BIN. Without Harness it offers one setup tool. On Linux the installer uses apt-get to add tmux and curl, which asks for your password.

From the project README. Source.

Tools

  • Shows who you are to Harness

    Says which agent is calling, on which machine, whether it may start harnesses now, how many it has open and how many starts are left. It is meant to be called first.

    Try: “Check whether you can start Harness agents.”

    Read · harness_whoami

  • Lists running agents

    Lists the harnesses on a machine with each one's agent, state, who started it, last activity, folder and topic. It can include ones stopped in the last week.

    Try: “List my Harness agents on the GPU box.”

    Read · harness_list

  • Searches past conversations

    Searches every turn of every live or stopped harness on this computer for words, so you can find what was already said or decided before starting new work.

    Try: “Search Harness for what we decided about the database.”

    Read · harness_search

  • Lists your machines

    Lists the machines on your Harness account with their status, so a harness can be started on another one.

    Try: “Which of my machines are online?”

    Network · harness_machines

  • Starts a coding agent

    Starts an agent such as Claude Code, Codex or OpenCode on a task, in a new project folder Harness makes or in an existing folder, here or on another machine. You can watch it in the Harness app.

    Try: “Start a Codex agent named reviewer to review the auth module.”

    Runs code · harness_start

  • Waits for agents

    Waits until the named harnesses stop working and reports each one's state. After the timeout it says they are still working so you can call it again.

    Try: “Wait for the reviewer agent.”

    Read · harness_wait

  • Reads an agent answer

    Returns a harness's state and its last turn: what it was asked and what it answered.

    Try: “Show me the reviewer's answer.”

    Read · harness_read

  • Shows or changes agent permissions

    Lists what agents may do in Harness. With a name it turns a setting on or off. Turning one on is meant to follow your yes.

    Try: “Show which agent settings are on in Harness.”

    Write · harness_settings

  • Closes an agent you started

    Closes a harness this assistant started once it is done. The conversation is kept and you can resume it. It refuses while the agent works unless told to close now.

    Try: “Close the reviewer agent.”

    Write · harness_close

Read from the source code

Permissions

high risk · 5 things to watch

High risk

An assistant using this can start other coding agents that edit files and run commands, here or on your other machines, and each one spends your agent plan. Leave the "Agents can start other agents" setting off unless you want that.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It starts agents that run code on your machines

    harness_start launches Claude Code, Codex or another agent on a task, here or on another machine. Those agents can edit files and run commands, so rely on their own permission prompts. github.com

  • Every agent it starts spends your tokens

    Started agents use your own agent plans. The server tells the assistant to start one only for work that runs in parallel or needs another view, and allows at most 4 at once. github.com

  • harness_settings can widen what agents may do

    An agent turns a setting on by passing a flag that says you agreed. That flag comes from the assistant, so make sure it asks you first. github.com

  • Setup pipes a remote script into your shell

    The Harness install command is curl ... | bash. The script (cli/scripts/install.sh) downloads a checksum-verified Node runtime into ~/.harness/runtime, adds ~/.local/bin to your shell startup file, and on Linux uses apt-get, which asks for your password. Read the script first if you do not trust the host. github.com

  • Starting needs a setting you turn on

    The setup text says agents may start others only after you turn on "Agents can start other agents" in Harness settings. Leave it off if you do not want that. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Talks toOther machines on your Harness account when you start or list harnesses there
Sign-in and keysHarnesses on this computer need no account. Running on other machines needs you to sign in with harness login in a browser.

Questions

Is the Harness MCP server official?

Yes. Autonomous makes the Harness app and ships this server from the same repo, autonomous-ai/openharness. It is also listed in the official MCP Registry.

Do I need to install Harness first?

Yes. The npm package only runs the harness mcp command from an installed Harness. Without it, you get one tool that explains how to install Harness.

Does it work on Windows?

Not directly. Harness runs on macOS and Linux. On Windows the README says to install it inside WSL and run the server from there.

Do I need an account?

Not for agents on this computer. To run agents on your other machines you sign in with harness login.

Can the assistant control agents I started myself?

No. It can list and read what it can see, but it only gives work to and closes the harnesses it started.

How many agents can it start?

At most 4 at once for one assistant, and an agent that another agent started may not start more. The first call, harness_whoami, tells it how many starts are left.

Does it have more tools than the README lists?

Yes. The README lists 8. The code also has harness_settings, and two messaging tools that only appear when the assistant itself runs inside a Harness pane.

Information

updated Nov 2, 2026

Publisher
Official
Package
@autonomous-ai/harness-mcp
Registry
npm
Transport
stdio
Version
0.4.20
License
MIT
Last commit
Oct 31, 2026
Open issues
25
Listed in
Official MCP registry

WebsiteGitHubnpmOfficial MCP RegistryChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 4
  1. README.md · github.com
  2. mcp.ts · github.com
  3. index.mjs · github.com
  4. package.json · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.