Changelog/Connect Your AI Agent with MCP Browser Sign-in
v2.11.0featureimprovementapi

Connect Your AI Agent with MCP Browser Sign-in

LetRetro MCP now uses OAuth browser sign-in. Add the server URL to your AI client, sign in to LetRetro, and approve the boards your agent can work with. You no longer need to create or paste a LetRetro API key.

Connect your agent

The remote MCP server is available at https://mcp.letretro.com/ for clients that support Streamable HTTP and OAuth. Setup instructions are available for Codex, Claude Code, Claude connectors, Cursor, and VS Code in Settings → MCP connections.

For Codex, run:

codex mcp add letretro --url https://mcp.letretro.com/
codex mcp login letretro

Then complete the authorization in your browser:

  1. Sign in to your LetRetro account.
  2. Choose the workspaces or personal boards you want to make available.
  3. Keep the default read-only permission, or approve read and write if your agent needs to make changes.
  4. Approve the connection and return to your client.

Your agent can work within the access you approve. Existing board membership and permissions still apply.

Availability and usage

  • Personal boards require your own Pro subscription.
  • Workspace access requires the workspace owner to have Pro. Free members can connect an eligible workspace they belong to.
  • Pro includes 20,000 MCP requests per billing period, shared across the owner's workspaces and personal boards.
  • View your allowance and purchase additional request packs from Billing.

Manage connections from Settings

Open Settings → MCP connections to copy the server URL, find setup instructions, and review your connected agents. Each connection shows its approved workspaces or personal-board access, permissions, billed requests, last activity, and expiry.

Use Disconnect to revoke an agent's access. To change its workspaces or permissions, reconnect from your client and approve a new connection. Expired connections also require a fresh sign-in.

Already using LetRetro MCP?

The new browser authorization replaces the previous API-key setup. Reconnect your client using the server URL above and approve its access. Your boards and historical usage remain available.