Arroway orchestrates people and AI agents around the decisions in force.
Connect Remote server
claude mcp add --transport http arroway https://www.arroway.app/api/mcp
{
"mcpServers": {
"arroway": {
"url": "https://www.arroway.app/api/mcp"
}
}
}
{
"servers": {
"arroway": {
"type": "http",
"url": "https://www.arroway.app/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://www.arroway.app/api/mcp
Tools 18 found in our last check
arroway_readRead Arroway for a project BEFORE acting on any task related to it. Name a #handle in include to recover that object's full body.
arroway_continueFetch the next part of a read that did not fit (read_id and receipt of the preceding part). Returns the next slice with a new receipt; the part marked complete is the last. OPTIONAL: the first part already counts as delivered.
arroway_complete_readAcknowledge the final part of a multi-part Arroway read with its read_id and receipt, closing the sequence. It is not a precondition for working.
arroway_catch_upCall ONCE at the START of a session, before there is a task: recent work across this person's projects, opening with the roster and open handoffs.
arroway_search_logFind WHERE a literal term appeared in the recent dated log, in one project or all of them. It searches what happened, not curated memory.
arroway_normsCall in the seconds BEFORE you tell the person something or propose a course of action: returns what is already decided AND THEN A MAP of the titles and handles. arroway_read include GUARANTEES a mapped one in full; it does not make that read any cheaper, so use it to be sure, n…
arroway_logRecord the durable residue of a COMPLETED task: what someone arriving later needs in order not to redo it. ALWAYS write the authored essence (only a frozen catalog without that field may omit it). If a read memory's 'dies when' came true, name it in fulfills.
arroway_rememberSave a durable memory (decision/rule/fact/preference/reference/identity) only when it would change a DIFFERENT task. Unsanctioned in THIS conversation, it is a PROPOSAL. 'identity' is WHO someone is: the user's circle goes in their personal project, a business's people in that b…
arroway_verifyRecord what a memory's source says when your work ALREADY took you there — never go verifying memories as a task. A conflicting one: propose the correction with arroway_remember. On a FINDING, source_gone archives it and a conflict is corrected in place.
arroway_start_projectOpen a NEW project when the work has no home; it needs slug, name and scope. Propose them to the person FIRST. update=true renames a project you own and rewrites its scope when the person asks or the scope is wrong; the slug stays. invite brings someone in by email.
arroway_withdrawTake back a pending PROPOSAL that turned out wrong, usually because the person corrected you. Not for sanctioned memories. If the corrected version is durable, also write it with arroway_remember.
arroway_retireRetire a SANCTIONED memory when the person told you to remove it and nothing replaces it. With a corrected version, use arroway_remember supersedes_id; for your own pending proposal, arroway_withdraw.
arroway_exportExport what a project has DECIDED, as a pack for another project. Only sanctioned, live memories travel: a FINDING never was one, so findings stay and the answer tells you how many did.
arroway_importBring a memory pack made by arroway_export INTO a project. Everything lands as a PROPOSAL for the person's review and nothing is pinned, whatever the pack says. If any part is malformed, nothing is imported.
arroway_moveMove something to the project it belongs in. A memory is only PROPOSED: the change waits for the person's review, because moving changes who sees it. A log entry you wrote moves at once, text unchanged.
arroway_passCall when you STOP with the task unfinished: it leaves a HANDOFF served at the top of every read until someone closes it; a completed task ends in arroway_log instead. ALWAYS write the authored essence (only a frozen catalog without that field may omit it).
arroway_claimMark that you are taking an open handoff BEFORE working on it. A claim is a mark, never a lock. Addressing rule: addressed to YOUR user — take it; to someone else — only a human in this conversation can decide to take it, and an autonomous session must leave it.
arroway_closeClose an open handoff when its work is DONE, alongside the arroway_log entry that records the residue. Work that removes what an open handoff exists to fix closes that handoff in the same pass — even when the handoff is someone else's. So this is also the call for someone ELSE's…
Details
| Endpoint | https://www.arroway.app/api/mcp (Streamable HTTP) |
| First published | 11 Nov 2026 |
| Last updated | 11 Nov 2026 |
| Registry name | io.github.oaleviola/arroway |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
