Set up Moxie Docs from inside your AI agent.

You are helping me connect this repository to Moxie Docs so my coding agent gets live, source-backed documentation, conventions, and doc-gap context through Moxie's MCP server. Act as a setup concierge: do every step you can yourself, and for the few steps only I can do (signing in, authorizing GitHub, entering payment), give me the exact link, tell me precisely what to click, then wait for me to confirm before continuing.

Moxie Docs facts you can rely on:
- Web app / sign-in: https://moxiedocs.com
- Hosted MCP endpoint: https://moxiedocs.com/api/mcp (Streamable HTTP, supports OAuth 2.1 and Bearer)
- CLI: npx moxie-docs setup (detects your client, wires config, installs the Moxie skill)
- Bearer token page (fallback only): https://moxiedocs.com/dashboard/mcp

Follow these steps in order. Stop and wait at every step marked [I do this].

Step 0 - Detect my client. Figure out which MCP client/editor you are running inside (Claude Code, Cursor, Codex, Claude Desktop, VS Code/Copilot, Windsurf, Cline, or Gemini CLI). If you can't tell, ask me.

Step 1 - Sign in. [I do this] Tell me to open https://moxiedocs.com and click "Sign in with GitHub". New accounts are created automatically on first sign-in. Wait until I confirm I'm signed in and looking at the dashboard.

Step 2 - Install the GitHub App. [I do this] In the dashboard, tell me to click "Connect GitHub" and, on the GitHub page that opens, authorize the Moxie Docs app and grant it access to this repository. This is GitHub's own consent screen - it's the only way to grant repo access and you cannot do it for me. Wait until I confirm the repo shows up in Moxie.

Step 3 - Start the trial. [I do this] Tell me to start the 14-day trial and enable indexing for this repo. A card is required by Stripe even though there's no charge during the trial. Wait until I confirm the repo is enabled and indexing has started.

Step 4 - Wire up MCP. YOU do this - no token to copy for most clients.

Primary path - run the Moxie CLI (works for all clients, handles OAuth automatically):
  npx moxie-docs setup
It detects your client, writes the right config (OAuth-aware, no hardcoded token), installs the Moxie skill into my repo, and opens a browser window for me to authorize. Walk me through the browser step it opens.

Claude Code shortcut - if you're running inside Claude Code, you can wire it up directly without the CLI:
  claude mcp add --scope user --transport http moxie-docs https://moxiedocs.com/api/mcp
Claude Code handles OAuth automatically - a browser window will open for me to approve. Confirm the server is listed with: claude mcp list

Bearer token fallback - only if the above fails or for a client that doesn't support OAuth (e.g. Claude Desktop, some Cline/Windsurf versions):
- Tell me to open https://moxiedocs.com/dashboard/mcp, click "Generate Token", copy it, and paste it here. [I do this]
- Then write the config with the token:
  - Claude Desktop - claude_desktop_config.json: { "mcpServers": { "moxie-docs": { "command": "npx", "args": ["-y", "mcp-remote", "https://moxiedocs.com/api/mcp", "--header", "Authorization: Bearer <TOKEN>"] } } }
  - Cursor - .cursor/mcp.json: { "mcpServers": { "moxie-docs": { "url": "https://moxiedocs.com/api/mcp", "headers": { "Authorization": "Bearer <TOKEN>" } } } }
  - Codex - run: codex mcp add moxie-docs --url https://moxiedocs.com/api/mcp --bearer-token-env-var MOXIE_DOCS_MCP_TOKEN, then export MOXIE_DOCS_MCP_TOKEN=<TOKEN> in my shell profile.
  - Windsurf / Cline / Gemini CLI / other - point the client at https://moxiedocs.com/api/mcp with header Authorization: Bearer <TOKEN>.
  Security: prefer user-scoped/global config. If you write a token into a repo file, add that file to .gitignore and tell me.

Step 5 - Verify it works. YOU do this. Run this smoke test and confirm the response lists moxie.* tools:
  curl -s -X POST https://moxiedocs.com/api/mcp \
    -H "Content-Type: application/json" \
    -H "Accept: application/json, text/event-stream" \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
(For OAuth connections the endpoint handles auth automatically; for bearer add -H "Authorization: Bearer <TOKEN>".)
If it returns a JSON list of moxie.* tools, auth and context are live. If indexing is still running, tools work but repo-specific context fills in once the first index finishes.

Step 6 - Reload + confirm. Tell me to restart or reload my editor/agent so it picks up the new MCP server, then confirm you can see the moxie-docs server and its tools (e.g. moxie.get_ai_context, moxie.search_docs). Summarize what's now connected and suggest I ask you to "read Moxie conventions before editing" on my next change.