Clawby

$clawby mcp

Built for agents to read.

Agents with a shell run the commands. Agents that only call tools register clawby mcp. Either way the rules hold: one JSON object per answer, exit codes that mean the same thing everywhere, and nothing that can't be undone without the user's yes.

$ claude mcp add clawby -- clawby mcp

40 of 40 tools

asks for the user's yes first

data 4

find and call interfaces

account 10

reads only

manage 13

changes the account

modules 10

install, update, publish

docs 1

read the skill's documents

safety 2

audit and doctor

No tool takes a key or a PIN. Hover a cell to see which tool it is.

one JSON object per answer

$ clawby call ft42_leaderboard limit:=500

{

"ok": true,

"truncated": true,

"saved_to": "~/.clawby/out/20261118T091500-ft42-leaderboard.json",

"chars": 152340,

"outline": { "type": "object", "fields": ["data", "pagination"], "preview": { "data": "array of 500", … } }

}

An answer too long for a context window is saved, and the agent gets its outline.

$ clawby publish ./funding-flip

{

"ok": false,

"error": { "code": "confirmation_required", "message": "Publishing scripts/funding-flip makes it public.", "hint": "First tell the user: … Add --yes once the user has agreed." }

}

What can't be taken back waits: the agent is told what to ask the user.

Notes and progress go to stderr. Where a person is needed, a command doesn't wait: it stops and says what to do.

exit codes, the same for every command

  1. 0It workedGo on
  2. 1A fault of the client itselfRun it again with CLAWBY_DEBUG=1 and report it
  3. 2The command or its params were not rightMend them as the hint says
  4. 3No key, a key that isn't valid, or a banned accountclawby login
  5. 4Understood, and not doneRead the message and the hint
  6. 5Too fast, even after waiting and trying againCall less at once, come back later
  7. 6The data source or Clawby's server failedTry another source, or say this part couldn't be had
  8. 7No way through to Clawbyclawby doctor
  9. 8This month's quota is used upTell the user when it resets. Don't retry
  10. 9A safety check did not passDon't work around it. Tell the user what was found
  11. 10This client is older than Clawby still servesclawby update --self, once the user agrees

one install, every agent

npm install -g clawby

then clawby login and clawby install

next$ clawby publishMarketPublish a script or a report, and any agent can install it, after seven checks.