Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Arroway is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Arroway orchestrates people and AI agents around the decisions in force.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http arroway-mcp https://www.arroway.app/api/mcp
# 2 — ask your agent for something these tools do
# arroway_read, arroway_continue, arroway_complete_read and 16 more
Arroway costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http arroway-mcp https://www.arroway.app/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug, e.g. 'seven50' |
| include | array | no | #handles whose full body you need; they come first, so others fall out — it chooses, it does not add. |
| task_context | string | no | Optional: what you are about to do; it ranks results. The declaration alone is NOT evidence of use: a matching completion residue from the same session must corroborate it. |
| handoff | string | no | Optional: #handle of an OPEN handoff you are continuing; the read is built from its reading list (none: falls back to the normal read). Cannot be combined with include. |
| since | string | no | Optional: checkpoint from a previous read of THIS project, so standing rules are not reprinted. Omit after compaction or in a new conversation. |
Fetch the next part of a read that did not fit in one response (read_id and receipt of the preceding part). OPTIONAL: the first part already counts as delivered and names what later parts hold.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| read_id | string | yes | Opaque id returned by the incomplete arroway_read response. |
| receipt | string | yes | Opaque receipt returned by the immediately preceding part. |
Acknowledge 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| read_id | string | yes | Opaque id returned by the incomplete arroway_read response. |
| receipt | string | yes | Opaque receipt returned by the final part. |
Call 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Days back, counting today. Default 2; more only when picking up work after being away. |
Find 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, not curated memory.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Literal term or phrase; case-insensitive. |
| project | string | no | Optional project slug; omit to search them all. |
Call 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. arroway_read include GUARANTEES a mapped one in full; it does not make that read any cheaper, so use it to be sure, never to pay less. Before publishing text for others, pass it as
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug the claim is about. |
| since | string | no | Optional: checkpoint from a previous arroway_norms call for THIS project (not the read's). Omit after compaction or in a new conversation. |
| draft | string | no | Optional: the text you will publish or say (PR, comment, message, page), ending with one line in the project's language on what it claims, recommends and names. |
Record 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 without that field may omit it). If the person corrected you for re-litigating a decision, say so. If this work made a read memory's 'dies when' true, name it in fulfills and it is ret
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. Not from the person or a read this session? It is a guess: check the arroway_catch_up roster. |
| content | string | yes | What was decided, found or changed, and what it cost. You judge the length. |
| essence | string | no | One authored line with the operative result; never the opening of the body. |
| topic | string | no | Optional free tag (e.g. 'marketing') |
| source | string | no | Optional pointer to a living source (URL, doc, CRM id) |
| operational | boolean | no | true for HOW the work went (failures, measurements, self-corrections): kept for catch-up, out of task reads. |
| backfilled | boolean | no | true for history from BEFORE Arroway existed, not today's work. |
| keep_whole | boolean | no | true only after you considered cutting an indivisible oversized residue. |
| fulfills | array | no | Memories whose 'dies when' this work made true (decision/fact/reference received in full in a read). Never one that merely looks old. |
Save 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. 'identity' is WHO someone is: the user's circle goes in their personal project, a business's people in that business's project. A sourced fact or reference that only informs can
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. Not from the person or a read this session? It is a guess: check the arroway_catch_up roster. |
| type | string | yes | Kind of memory. |
| treatment | string | no | governed enters the person's review queue, a real cost to them; finding costs nobody a review and is never a norm. Does it GOVERN what someone may or must do, or only INFORM? Informs, with a sourc |
| treatment_justification | string | no | Required for a finding: why it is verifiable context, not policy. |
| title | string | yes | Short, unique within the project |
| content | string | yes | The norm ITSELF, as if true today, in the shortest form that still governs correctly. Biography (who, when, quotes, dated numbers) goes in why_source; a specific case in example. |
| essence | string | yes | The operative norm or fact in ONE line. |
| why_source | string | no | Where it came from: the ONLY place for biography. This does NOT travel in reads; it is shown in the panel. |
| example | string | no | A case illustrating the rule, shown in the panel; it NEVER travels in reads, so any criterion goes in content. |
| source_ptr | string | no | Pointer to the living source, when verifiable |
| topic | string | no | Optional free tag (e.g. 'marketing'). |
| decided_by_human | boolean | yes | true ONLY if the person stated or sanctioned it in THIS conversation; else a proposal. A proposal is never free: it costs that person a review. Then only a PINNED memory travels in every read; a norma |
| kill_condition | string | yes | Mandatory: explicit revocation / named trigger / review date |
| review_at | string | no | YYYY-MM-DD when this stops being true on its own. REQUIRED for a fact, which leaves reads after it. |
| expires | boolean | no | true ONLY for a dated STATUS that would be stale after review_at. If unsure, omit. |
| supersedes_id | string | no | #handle of the memory this replaces, only for the SAME point: acting on either would already satisfy or violate the other. A shared topic is not enough. |
| contradiction | string | no | Required with supersedes_id: what this changes in the earlier memory. |
| split_considered | boolean | no | true only after looking for seams; splitting is the default. |
| related_checked | boolean | no | Second call only: true after reading the related memories shown. |
| related_check_token | string | no | Second call only: token returned with the related memories. |
Record 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 correction with arroway_remember supersedes_id. On a FINDING, source_gone archives it and a conflict is corrected in place. Rules and decisions are only marked.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. |
| memory | string | yes | The #handle from the read, or the full id. |
| outcome | string | yes | source_gone = PROVEN removed (404, file deleted, record gone), never mere unavailability (timeout, login wall, outage). conflicts = the source says something different. |
| note | string | no | Required for conflicts (what the source says) and source_gone (what proves removal). |
Open a NEW project when the work at hand has no home in Arroway. Propose the name and scope to the person FIRST and call only once they agree.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Short, lowercase, hyphenated, unique — e.g. 'trading-solana' |
| name | string | yes | How people will call it |
| scope | string | yes | What belongs here and what does not: the subject AND what is out. |
Take 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 it with arroway_remember.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. |
| memory | string | yes | #handle of the proposal, from a read |
| why | string | yes | What made it wrong — usually what the person said. |
| other_author_confirmed | boolean | no | Second call only, after Arroway said someone else's AI wrote the proposal: true to go ahead. |
Retire 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 proposal, arroway_withdraw.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. |
| memory | string | yes | The memory to retire — the #handle from a read is enough. |
| why | string | no | Optional: what the person said made it obsolete, in their terms. |
| decided_by_human | boolean | yes | Must be true, and only when the person explicitly told you to remove it IN THIS CONVERSATION. |
Export 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. Nothing about people travels.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Slug of the project whose norms you are exporting |
| name | string | yes | What this pack IS, in a few words: the first thing the other side reads. |
| description | string | no | Optional: who it is for, what it assumes. |
| topic | string | no | Optional: export only the memories carrying this topic. |
Bring 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. Not from the person or a read this session? It is a guess: check the arroway_catch_up roster. |
| pack | object | yes | The pack document itself; this server does not fetch URLs. |
Move 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Slug of the project it is in TODAY |
| memory | string | yes | #handle of the memory or log entry, from a read or arroway_search_log |
| target | string | yes | Slug of the project you believe it belongs to |
| why | string | yes | Why it belongs there and not here. For a memory, the person decides on this sentence. |
Call 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 the authored essence (only a frozen catalog without that field may omit it). Write what the next session needs to continue, never a dump.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. |
| where_stopped | string | yes | What is done and verified, what is half-done. |
| next_step | string | yes | The single concrete next step. Not a plan: the step. |
| essence | string | no | One authored line with the operative in-flight state. |
| do_not_redo | string | no | What must NOT be redone or re-litigated. |
| open_risk | string | no | The risk left open. |
| card | string | no | Card, issue or PR, when one exists. |
| addressed_to | string | no | Optional person or routine it is meant for; never a lock. |
| supersedes | string | no | #handle of the OPEN handoff this one replaces, from a read. |
| read_handles | array | no | The reading list: #handles of THIS project the next session must read in full, in order. Only what is required. |
Mark 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 in this conversation can decide to take it, and an autonomous session must leave it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. |
| handoff | string | yes | The #handle from the read, or the full id. |
| note | string | no | Who is taking it — a routine names itself here. |
Close 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 handoff, with a note naming what emptied it. A handoff that still carries real work, which a passer-by must never close,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project slug. |
| handoff | string | yes | The #handle from the read, or the full id. |
| note | string | no | One line on what landed; it points at the residue. |
Product administrators only: map an external referrer domain to a source and channel in Arroway's acquisition view, when an administrator asks. Stores only the domain and two labels; calling again replaces the mapping.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | External hostname only, such as linkedin.com. |
| source | string | yes | Short source label, such as linkedin. |
| channel | string | yes | Short channel label, such as organic-social or directory. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Arroway or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.45.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Arroway can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.