ARCY MCP
Connect Claude Code, Cursor, Codex or Antigravity to the ARCY MCP with an Agent token, run one prompt to set the Product up surface by surface, and accept what it proposes.
The ARCY MCP is the server your coding agent talks to. It sets your Product up from your repository, surface by surface; everything it writes waits for your Accept. You connect it on Settings > ARCY MCP; Hand it to your agent with the ARCY MCP on a surface's page opens this page at its entry.
Before you start
- Only an Admin mints or revokes an Agent token, and each person holds one active token per Product: every developer who runs the agent mints their own. A Member sees the tokens and the steps. See Team.
- Run it against a local or staging copy of your Product, never production: a flow preview clicks, fills and calls your API. Flows need Playwright.
- A token reads and proposes; it cannot publish, delete or accept.
Setting it up
Agent tokens. Give the token a Name, then Mint token. Already holding one here? A sentence names it in place of the form until you revoke it. A minted token is shown once; ARCY keeps only a hash. Snippets carry it until Done, then show <your Agent token>.
Connect your agent. Pick your agent. The steps add the config, https://api.arcyai.com/mcp with the token as a bearer header: a shell line for Claude Code, a file for the other three. The Cursor file holds your token: keep it out of the repository.
What your agent can do. Nine entries, each with its run line and a one-paste button per agent. Set up ARCY end to end is marked Start here: it reads what is done, asks which surfaces to run, and runs them in order. The other eight run one surface each: Install arcy.js, Declare attributes, Catalogue endpoints, Write the Persona, Add training sources, Match the brand, Draft flows from a list and Suggest the limits. Each shows one status word: Not started, Proposed (waiting for you), Accepted (configured, not reaching visitors) or Live.
Answer the cards. The agent asks only what your code and ARCY cannot answer, as decision cards: what it found, its suggestion, the options with the recommended one in bold. Nothing is asked twice; when a repository lacks a surface's material, one card sends you to the one that has it.
What it changes
Every write outside a flow draft is a proposal. Proposals waiting lists each with Open the page; its page (Attributes, Endpoints, Persona, Train, Customization or, for an Admin, Limits) shows it as Proposed by your agent beside the current value. Accept applies it through that page's own checks; Discard removes it. A second proposal from the same token replaces its first. Revoke discards the token's open proposals; accepted ones stay named for 30 days. Flows land as drafts on Flows; a draft may bind a proposed attribute or endpoint, and Publish waits until it is accepted.
Install arcy.js owns four names in your env files: ARCY_TOKEN, ARCY_SECRET, ARCY_DEV_TOKEN, ARCY_DEV_SECRET. The agent reads both Tokens from ARCY and writes or renames them; a Secret never travels, and a missing one is one card pointing to Identity verification.
Not on the MCP: file uploads, the header logo, identity signing and the Bridge check, and Accept itself.
When it goes wrong
- The agent gets 401. The token was revoked or mistyped; mint a new one.
- Mint token is refused. You already hold an active token for this Product: revoke it first.
- A proposal is refused on Accept. The page's own message says why, such as a name taken since; discard it and rerun the surface.