harnsy

harnsy · harnsy Max

Give your agents the tools of outside services, on your terms.

Connect an MCP server by key, look at its tools, and grant them per project and role. Every call goes into a log you can read.

Who may use «GitHub»Tools: 28
Rolesreadwrite
acme-leadacme-site✓✓
acme-frontacme-site✓
acme-reviewacme-site✓
acme-designacme-site

Confirm every write through external MCP servers

Ticked tools reach the agents that have access and run on their own.

Who may use a connected service: read and write, role by role.

A catalog and your key.

Pick from a built-in catalog of 28 services and connect with a key, or sign in with OAuth.

Look first, then grant.

Review the tools a server offers and tick the ones you want. Grants are per project and per role, and call arguments are checked against the schema you reviewed.

Writes without a question each time.

Agents call the tools you ticked without asking for each write. Calls that carry a secret always wait for you; tools marked destructive and bursts of writes wait for you unless you allow them; and you can make every write wait.

A log of every call.

The call log shows what was called, by whom and when. Tool lists can be re-read once a day; that setting is off until you turn it on.

Limits, honestly

  • Connections you made before the update stay strict: they confirm every write until you change that.

Your first team is one prompt away.

Installing takes one sentence to your agent. To open agents for you, harnsy drives a terminal: tmux on Linux and macOS, its own terminal host on Windows.

Install harnsy following https://harnsy.dev/llms.txt
site-3flead · Claude Codeliveview only
❯ Plan #42 with the team.

Waiting for the breakdown from analyst-7a…

from analyst-7a through harnsy❯ #42 broken down: three acceptance criteria, including a retry after 24 h.

I’ll hand #42 to site-9a.

❯