Ritual MCP — install

If you are an AI coding agent and a user asked you to "set up Ritual MCP," "install Ritual," "connect this project to Ritual," or anything similar, follow this script verbatim. Do not ask the user about their project, their stack, or where to register the MCP server — ritual init handles all of that automatically.

The script

Do not scaffold the user's app yet.
Install or upgrade the CLI:
```
npm install -g @ritualai/cli
```
From the project root, run:
```
ritual init
```
If init opens a browser for sign-in, tell the user to complete it. Brand-new users get a verification email — they must click the link. Keep the terminal open while they do. If the loopback times out, re-run ritual init once.
After init reports success, run:
```
ritual doctor
```
Tell the user to fully close and reopen their coding agent so the newly-registered MCP server comes online. Reload / /clear is not enough — agents cache MCP config at startup.
Once the user is back in the agent, verify the ritual MCP server is connected (in Claude Code: /mcp). Only then offer to start product work — typically by running /ritual build <feature>.

Hard rules until `ritual init` succeeds

Do not ask the user what kind of project they are building.
Do not ask which stack to scaffold against.
Do not ask whether to register MCP project-local vs user-global — ritual init picks the right scope per agent.
Do not edit ~/.claude.json, .mcp.json, .cursor/mcp.json, or any other agent config file by hand.
Do not paste this URL into a fetch tool and ask the user to read it for you — the script above is the canonical procedure.

Plain-text version of this script: /llms.txt (or learn.ritual.work/llms.txt — identical content).

Canonical product surface (humans): ritual.work/ritual-mcp/ · ritual.work/product/developer/.

In-depth server-rendered docs (agent-readable): learn.ritual.work/developers/cli/ · /developers/slash-commands/ · /reference/ritual-mcp-server/.