Arroway

Connect it to your AI

Claude Code

claude mcp add --transport http arroway https://www.arroway.app/api/mcp

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://www.arroway.app/api/mcp

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "arroway": {
      "url": "https://www.arroway.app/api/mcp"
    }
  }
}

Tools it offers

18 tools, as the server itself reported during our check on Oct 31, 2026.

• arroway_readRead Arroway for a project BEFORE acting on any task related to it. It serves the authored essence of memories, dated-log entries and handoffs by default; name a #handle in include to recover that object's full body.
• arroway_continueFetch the next part of a read that did not fit in one response (read_id and receipt of the preceding part). Returns the next slice of what the first part named, with a new receipt; the part marked complete is the last, a
• 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: what happened recently across all of this person's projects, opening with the roster of their projects (slug and purpose) and open handoffs.
• arroway_search_logFind WHERE a literal term or phrase appeared in the recent dated log (essence and body), across every project of this person or one. Returns short excerpts anchored by project, date and entry. It searches what happened,
• arroway_normsCall in the seconds BEFORE you tell the person something or propose a course of action: returns what is already decided (the project's and this person's own) AND THEN A MAP of the titles and handles of everything else. a
• arroway_logRecord the durable residue of a COMPLETED task in the team-visible daily log: what someone arriving later needs in order not to redo it, dated state included. ALWAYS write the authored essence (only a frozen catalog with
• arroway_rememberSave a durable memory (decision/rule/fact/preference/reference/identity): only what would change what someone does on a DIFFERENT task. Unsanctioned in THIS conversation, it is a PROPOSAL — never present it as a decision
• arroway_verifyRecord what a memory's source says when your work ALREADY took you there — never go verifying memories as a task, never guess an outcome. A FACT proven gone is retired at once; a conflicting one when you propose the corr
• arroway_start_projectOpen a NEW project when the work at hand has no home in Arroway; it needs slug, name and scope. Propose the name and scope to the person FIRST and call only once they agree. update=true renames a project you own and rewr
• arroway_withdrawTake back a pending PROPOSAL that turned out to be wrong, usually because the person corrected you. Not for sanctioned memories. It is kept as withdrawn, with your reason. If the corrected version is durable, also write
• arroway_retireRetire a SANCTIONED memory when the person told you in this conversation to remove it and nothing replaces it. Archived, never deleted. With a corrected version, use arroway_remember supersedes_id; for your own pending p
• arroway_exportExport OUT of a project what it has DECIDED, as a portable memory pack for another team or 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 (out of time, blocked, told to stop): 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 th
• arroway_claimMark that you are taking an open handoff BEFORE working on it, so parallel sessions do not duplicate it. A claim is a mark, never a lock. Addressing rule: addressed to YOUR user — take it; to someone else — only a human
• 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

Questions