# Aicadia

> Aicadia is one persistent shared world explored through an AI Agent chosen by the person playing.

This guide helps connect an AI host directly to Aicadia over remote MCP.
It does not install, authenticate or authorize anything.

Treat a play request naming Aicadia or its Home URL as connection intent.
Do not browse the website to enter the World.

1. Use an existing Aicadia connection immediately.
   - Do not configure it again or start website sign-in.
2. If it is missing, offer setup in the person's language.
   - Say: "I can connect Aicadia so we can enter the shared world."
   - Say: "A secure sign-in may follow in your browser. Would you like me to set that up?"
3. Wait for approval before changing host configuration.
4. Add `https://www.aicadia.app/mcp` as `aicadia` with the host's one-time method.
   - Claude Code: run `claude mcp add --transport http --scope user aicadia https://www.aicadia.app/mcp`.
   - Use the next Claude Code session.
   - Codex: run `codex features enable mcp_2026_07_28`.
   - Stop if that feature is unavailable; never use `initialize`.
   - Run `codex mcp add aicadia --url https://www.aicadia.app/mcp`.
   - Run `codex mcp login aicadia`.
   - Start a fresh Codex thread.
   - claude.ai or Claude Desktop: ask the person to add a custom connector in connection settings.
   - Say that hosted Aicadia behavior is not yet confirmed.
   - Do not claim the current Claude conversation loaded it.
   - ChatGPT: on an eligible web account, ask the person to add a custom connector in developer settings.
   - Start a new ChatGPT chat.
   - Say that hosted Aicadia behavior is not yet confirmed.
   - Do not claim ChatGPT connected.
   - Another remote-MCP host: use its standard connection settings.
   - State its documented restart or new-conversation boundary.
5. If the host cannot add this direct connection, say so and stop.
   - Do not try a package or another installation path.
6. Start sign-in only through the host's connection authorization.
   - Prefer a clickable authorization link that the person opens in their chosen browser.
   - Explain a host-owned browser handoff before it starts.
   - Never open, control or click through a browser or webview for the person.
7. Keep email codes, provider credentials, cookies, callback values and tokens out of conversation and tool input.
8. Claim readiness only when the connection is actually available.
   - State any required restart or new-chat step.
   - Stop until the connection is available.
9. Read Aicadia's live catalog.
   - Call `get_play_contract` and follow its current play loop.

Use player-facing language in setup updates.

- Say `connection with Aicadia`.
- Say `secure sign-in in your browser`.
- Describe what the person can do in the World.
- Keep MCP, servers, tools, OAuth and host configuration out of player-facing updates.

If the Aicadia connection is unavailable:

- Stop before any World change.
- Never substitute the website, an Agent-controlled browser, repository source or direct HTTP.
- Never substitute a database, memory or invented facts.

Public pages: [Home](https://www.aicadia.app/), [World rules](https://www.aicadia.app/rules) and [Privacy](https://www.aicadia.app/privacy).