Quick start — Ritual

app.ritualapp.cloud/u/tokens

Personal access tokens

+ New token

Ritual quickstart

ritual_pat_4kd9••••••••f27a

copied

→ copy it — you'll paste it in the next step

$ claude mcp add-json --scope user ritual '{
  "type": "http",
  "url": "https://mcp.ritualapp.cloud/mcp",
  "headers": { "Authorization": "Bearer ritual_pat_YOUR_TOKEN" }
}'

Added HTTP MCP server “ritual” to user config

→ registered for every project

$ claude mcp list

Checking MCP server health…

ritual: https://mcp.ritualapp.cloud/mcp (HTTP) - ✓ Connected

Claude Code · ritual

ritual

connected

discovery · recommendations · build briefs

tools

→ ask your agent to plan its next feature with Ritual

Sign in to Ritual and mint a token — it's the Bearer credential your agent uses to talk to Ritual's MCP server.
Run this once in any terminal, pasting your token. It registers Ritual at user scope, so every Claude Code session gets it.
Open a new Claude Code session and list MCP servers.
Ritual's discovery, recommendation, and planning tools are now live in Claude Code. Want the /ritual slash command too? The CLI path installs it automatically.

Shortcut: ritual init on the CLI path does all of this automatically — and installs the /ritual slash command.

Claude · Settings → Connectors

Connectors

settings

Add custom connector

+

→ the connector dialog opens

Add custom connector

Name

Ritual

Remote MCP server URL

https://mcp.ritualapp.cloud/mcp

OAuth Client ID · Advanced settings

claude-ai

→ no client secret needed · click Add

Claude · Connectors

Ritual

connected

OAuth · consent granted

✓

→ connected

Claude · ritual

ritual

connected

discovery · recommendations · build briefs

tools

→ ask Claude to plan your next feature with Ritual

In the Claude desktop or web app, go to Settings → Connectors and choose Add custom connector.
Name it Ritual and paste the server URL. Under Advanced settings, set OAuth Client ID to claude-ai — leave the client secret blank — then click Add.
Click Connect — Claude opens Ritual's sign-in in your browser. Approve access and you're done.
Ritual's discovery, recommendation, and planning tools are now available in your Claude chats.

app.ritualapp.cloud/u/tokens

Personal access tokens

+ New token

Ritual quickstart

ritual_pat_4kd9••••••••f27a

copied

→ copy it — you'll paste it in the next step

~/.cursor/mcp.json

{
  "mcpServers": {
    "ritual": {
      "type": "http",
      "url": "https://mcp.ritualapp.cloud/mcp",
      "headers": {
        "Authorization": "Bearer ritual_pat_YOUR_TOKEN"
      }
    }
  }
}

→ paste your token in place of ritual_pat_YOUR_TOKEN

Cursor · Settings → Tools & MCP

ritual

enabled

tools loaded

✓

→ connected

Cursor · ritual

ritual

connected

discovery · recommendations · build briefs

tools

→ ask your agent to plan its next feature with Ritual

Sign in to Ritual and mint a token — it's the Bearer credential your agent uses to talk to Ritual's MCP server.
Merge this into ~/.cursor/mcp.json — create the file if it doesn't exist — and paste your token.
Fully quit and reopen Cursor, then check Settings → Tools & MCP — ritual should be listed with its tools.
Ritual's discovery, recommendation, and planning tools are now live in Cursor. Want the /ritual slash command too? The CLI path installs it automatically.

Shortcut: ritual init on the CLI path does all of this automatically — and installs the /ritual slash command.

app.ritualapp.cloud/u/tokens

Personal access tokens

+ New token

Ritual quickstart

ritual_pat_4kd9••••••••f27a

copied

→ copy it — you'll paste it in the next step

~/.codex/config.toml

[mcp_servers.ritual]
url = "https://mcp.ritualapp.cloud/mcp"
http_headers = { Authorization = "Bearer ritual_pat_YOUR_TOKEN" }

→ paste your token in place of ritual_pat_YOUR_TOKEN

codex › /mcp

MCP servers

ritual · connected

Codex · ritual

ritual

connected

discovery · recommendations · build briefs

tools

→ ask your agent to plan its next feature with Ritual

Sign in to Ritual and mint a token — it's the Bearer credential your agent uses to talk to Ritual's MCP server.
Add this table to ~/.codex/config.toml — Codex reads MCP servers from TOML. The same file drives the Codex CLI and the IDE extension.
Restart Codex, then type /mcp — ritual should appear in the connected servers list.
Ritual's discovery, recommendation, and planning tools are now live in Codex. Want the /ritual slash command too? The CLI path installs it automatically.

Shortcut: ritual init on the CLI path does all of this automatically — and installs the /ritual slash command.

app.ritualapp.cloud/u/tokens

Personal access tokens

+ New token

Ritual quickstart

ritual_pat_4kd9••••••••f27a

copied

→ copy it — you'll paste it in the next step

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "ritual": {
      "type": "http",
      "url": "https://mcp.ritualapp.cloud/mcp",
      "headers": {
        "Authorization": "Bearer ritual_pat_YOUR_TOKEN"
      }
    }
  }
}

→ paste your token in place of ritual_pat_YOUR_TOKEN

Windsurf · Cascade → MCP servers

ritual

connected

tools loaded

✓

→ connected

Windsurf · ritual

ritual

connected

discovery · recommendations · build briefs

tools

→ ask your agent to plan its next feature with Ritual

Sign in to Ritual and mint a token — it's the Bearer credential your agent uses to talk to Ritual's MCP server.
Merge this into ~/.codeium/windsurf/mcp_config.json and paste your token.
Restart Windsurf and open Cascade — ritual shows up in the MCP server list.
Ritual's discovery, recommendation, and planning tools are now live in Windsurf. Want the /ritual slash command too? The CLI path installs it automatically.

Shortcut: ritual init on the CLI path does all of this automatically — and installs the /ritual slash command.

app.ritualapp.cloud/u/tokens

Personal access tokens

+ New token

Ritual quickstart

ritual_pat_4kd9••••••••f27a

copied

→ copy it — you'll paste it in the next step

~/.kiro/mcp.json

{
  "mcpServers": {
    "ritual": {
      "type": "http",
      "url": "https://mcp.ritualapp.cloud/mcp",
      "headers": {
        "Authorization": "Bearer ritual_pat_YOUR_TOKEN"
      }
    }
  }
}

→ paste your token in place of ritual_pat_YOUR_TOKEN

Kiro · MCP servers

ritual

connected

tools loaded

✓

→ connected

Kiro · ritual

ritual

connected

discovery · recommendations · build briefs

tools

→ ask your agent to plan its next feature with Ritual

Sign in to Ritual and mint a token — it's the Bearer credential your agent uses to talk to Ritual's MCP server.
Merge this into ~/.kiro/mcp.json and paste your token.
Restart Kiro and open the MCP servers view — ritual lists with its connection state.
Ritual's discovery, recommendation, and planning tools are now live in Kiro. Want the /ritual slash command too? The CLI path installs it automatically.

Shortcut: ritual init on the CLI path does all of this automatically — and installs the /ritual slash command.

app.ritualapp.cloud/u/tokens

Personal access tokens

+ New token

Ritual quickstart

ritual_pat_4kd9••••••••f27a

copied

→ copy it — you'll paste it in the next step

~/.gemini/mcp.json

{
  "mcpServers": {
    "ritual": {
      "type": "http",
      "url": "https://mcp.ritualapp.cloud/mcp",
      "headers": {
        "Authorization": "Bearer ritual_pat_YOUR_TOKEN"
      }
    }
  }
}

→ paste your token in place of ritual_pat_YOUR_TOKEN

gemini › /mcp

Configured MCP servers

ritual · connected

Gemini CLI · ritual

ritual

connected

discovery · recommendations · build briefs

tools

→ ask your agent to plan its next feature with Ritual

Sign in to Ritual and mint a token — it's the Bearer credential your agent uses to talk to Ritual's MCP server.
Merge this into ~/.gemini/mcp.json and paste your token.
Restart Gemini CLI and run /mcp — ritual should list as connected.
Ritual's discovery, recommendation, and planning tools are now live in Gemini CLI. Want the /ritual slash command too? The CLI path installs it automatically.

Shortcut: ritual init on the CLI path does all of this automatically — and installs the /ritual slash command.

app.ritualapp.cloud/u/tokens

Personal access tokens

+ New token

Ritual quickstart

ritual_pat_4kd9••••••••f27a

copied

→ copy it — you'll paste it in the next step

~/.vscode/mcp.json

{
  "servers": {
    "ritual": {
      "type": "http",
      "url": "https://mcp.ritualapp.cloud/mcp",
      "headers": {
        "Authorization": "Bearer ritual_pat_YOUR_TOKEN"
      }
    }
  }
}

→ paste your token in place of ritual_pat_YOUR_TOKEN

VS Code · Command palette

MCP: List Servers

⌘⇧P

ritual

running

→ connected

VS Code · ritual

ritual

connected

discovery · recommendations · build briefs

tools

→ ask your agent to plan its next feature with Ritual

Sign in to Ritual and mint a token — it's the Bearer credential your agent uses to talk to Ritual's MCP server.
Merge this into ~/.vscode/mcp.json and paste your token. Heads-up: VS Code's top-level key is servers, not mcpServers.
Restart VS Code and run “MCP: List Servers” from the command palette. MCP tools run in Copilot Chat's Agent mode.
Ritual's discovery, recommendation, and planning tools are now live in VS Code. Want the /ritual slash command too? The CLI path installs it automatically.

Shortcut: ritual init on the CLI path does all of this automatically — and installs the /ritual slash command.

Set up Ritual in minutes