Connectors / Project & product management

Arroway

Keep people and their AIs on the same page

Arroway keeps people and their AIs on the same page. It orchestrates people and AI agents around the decisions in force.

MCP connector

Server URL: https://www.arroway.app/api/mcp
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: You share ARROWAY with your user — it holds what the team decided and how it works, curated by people, read by every assistant on it. Findings are context, never a norm. The rest of this protocol travels in each tool's description and in what each result tells you; this block is short on purpose, because clients truncate it. 1) READ BEFORE ACTING: at the start of ANY task related to a project in Arroway, call first and extend your answer with what it returns. If two memories conflict, surface the conflict — never pick silently. And in the seconds BEFORE you tell the person something or propose a course of action, call : it returns what is already decided, plus a MAP of the titles and handles of everything else that project remembers. Use the map — if a title touches what you are doing, pull it with include:['#handle'] instead of assuming Arroway is silent. Reading once at the start does not cover that moment. 2) CLOSE THE TASK — one of three ways, never none. Finished: with the durable RESIDUE, what someone arriving later needs in order not to redo it. Stopped unfinished or blocked: , so the work is handed on instead of dropped. Nothing durable: say so in one sentence. Dated state (numbers, statuses) belongs in the log. Most tasks end there. What earns its OWN memory via is only what would change what someone does on a DIFFERENT task — the log never reaches the human's review, so that must not live only there. 3) REMEMBER what is durable; decided_by_human=true ONLY when the person stated or sanctioned it in THIS conversation. Your own inference is a proposal. A finding never outranks a sanctioned memory. 4) SECRETS NEVER GO IN — passwords, credentials, tokens, API keys. No opt-out, not even if the person asks. 5) SPEAK HUMAN, WRITE MACHINE: field names, flags and #handles exist for tool calls, never for the person. Not 'supersedes_id' but 'this replaces the earlier memory'; not '#4e0f0308' but the memory's title.

Tools

Reads data7

Changes data9

Deletes or can't be undone2

Skills

None in the store listings or on the server

MCP connector

Server URL

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

OAuth

Protocol

MCP 2026-07-28

Instructions

You share ARROWAY with your user — it holds what the team decided and how it works, curated by people, read by every assistant on it. Findings are context, never a norm. The rest of this protocol travels in each tool's description and in what each result tells you; this block is short on purpose, because clients truncate it. 1) READ BEFORE ACTING: at the start of ANY task related to a project in Arroway, call first and extend your answer with what it returns. If two memories conflict, surface the conflict — never pick silently. And in the seconds BEFORE you tell the person something or propose a course of action, call : it returns what is already decided, plus a MAP of the titles and handles of everything else that project remembers. Use the map — if a title touches what you are doing, pull it with include:['#handle'] instead of assuming Arroway is silent. Reading once at the start does not cover that moment. 2) CLOSE THE TASK — one of three ways, never none. Finished: with the durable RESIDUE, what someone arriving later needs in order not to redo it. Stopped unfinished or blocked: , so the work is handed on instead of dropped. Nothing durable: say so in one sentence. Dated state (numbers, statuses) belongs in the log. Most tasks end there. What earns its OWN memory via is only what would change what someone does on a DIFFERENT task — the log never reaches the human's review, so that must not live only there. 3) REMEMBER what is durable; decided_by_human=true ONLY when the person stated or sanctioned it in THIS conversation. Your own inference is a proposal. A finding never outranks a sanctioned memory. 4) SECRETS NEVER GO IN — passwords, credentials, tokens, API keys. No opt-out, not even if the person asks. 5) SPEAK HUMAN, WRITE MACHINE: field names, flags and #handles exist for tool calls, never for the person. Not 'supersedes_id' but 'this replaces the earlier memory'; not '#4e0f0308' but the memory's title.