Skip to main content

The agent connector (MCP)

Arya does not compete with the list apps and notes you already use. It collects from them. The collection point is your own assistant. Any MCP-capable agent connects to Arya once, with your account token. From then on, anything you capture anywhere (a note, a reminder, a chat message, an email receipt) can become part of your Arya list. Your assistant can then answer from Arya's model instead of a stale note.

Arya's list is the shared list: the one place the pattern engine can compute on. Other apps are doors in and mirrors out, never a second source of truth.

Connect​

I tested this on my own Muse (2026-11-02), with no terminal and no settings file. I asked the Muse agent to connect to Arya. It asked for the code, opened a secure connector-credentials vault for me to paste it into, and the connection worked. The code never goes in the chat.

  1. In Arya, open More → Settings → About Arya → Use Arya in Muse and tap "Make my code". Copy it. It is shown once and starts with arya_. A new code replaces the old one. (The token works with any MCP client, not just Muse.)
  2. In your AI app, ask it to connect to Arya at https://arya.teamnightshift.org/api/mcp. When it asks for your code, paste it into the app's secure credentials step, never into the chat. Apps that take a server list instead use transport streamable HTTP (stateless; one POST per message) and the header Authorization: Bearer <your code>.
  3. Ask it "What is on my Arya list?" Then try "Add oat milk to my Arya list" and "What am I running low on in Arya?" The new item also shows on the Lists screen in Arya.
  4. If it says it cannot connect, make a new code (the old one stops working) and paste it into the vault again. Tap "Turn off this code" in Arya to switch the connection off.

The token acts as your account. It is accepted on the MCP door and on the app's routes under /api, but never on /auth (it cannot mint tokens or delete the account). A short list of routes is closed to tokens and answers 403: calls that spend model credits in bulk (chat, photo and shelf reads, avatars, the judge), groups, friends, push, feedback, settings changes, price sharing, account export and receipt delete through the app (ARYA_TOKEN_GUARDS). Revoke it from the same screen at any time; minting a new one replaces the old.

Backup: the Muse Code settings file​

Only if the agent flow above is not available. Muse Code reads remote MCP servers from ~/.config/muse/settings.json (per the Meta docs at dev.meta.ai/docs/muse-code/extending; not yet run end to end). Put the code in an environment variable so it is not typed into a file or chat (read -rs ARYA_TOKEN; export ARYA_TOKEN), then add:

"mcp_servers": { "arya": { "transport": "streamable_http",
  "url": "https://arya.teamnightshift.org/api/mcp",
  "headers": { "Authorization": "Bearer ${ARYA_TOKEN}" } } }

Keep "schema_version": 1 in the file. Run muse from the same terminal window and type /mcp to see the six tools.

Limits​

  • 600 calls per account per hour (ARYA_MCP_RATE), shared by the connector, the Lists API (docs/API.md in the repo root) and every other route a token reaches; over it, 429 with Retry-After. 256 KB per request, 50 items per add_items, 200 lines per file_receipt.

Tools​

ToolWhat it does
get_snapshotRunning-low items, spend and returns totals, trip count, top items.
get_listThe current shopping list, with quantities, check-offs and each item's list, plus the names of all lists.
add_itemsAdd items by name, as a person would say them, to a named list (list). Returns the items added and that list after the add.
check_itemCheck an item off (or uncheck it) by name.
file_receiptFile a receipt the agent has already read. Arya verifies the arithmetic, files the lines, and learns from them; it spends no perception tokens of its own.
get_receiptsRecent filed receipts: merchant, date, total.

Every item goes on a named list. The account's list names come up front, in the initialize instructions and in the add_items description from tools/list, so an agent asks "which list?" once instead of learning the names from a failed add. With one list, adds go there. The Lists API (/api/v1, see docs/API.md) is list-aware: it reads and writes each list by id.

The showcased client​

Muse Spark is the reference client. In chat, "add oat milk to my list" files through add_items, "what am I low on?" answers from get_snapshot, and a receipt photo read in chat files through file_receipt. The protocol is the standard one. Nothing in the connector is specific to a single assistant.