Connect Year in Review

Use your trackers from Claude, ChatGPT, Cursor, and other MCP-capable AI tools. Sign in once with your Year in Review account; everything you do via AI syncs back to the app instantly.

Server URL

https://mcp.yearinreviewapp.com/sse

Paste this in any MCP client’s Custom Connector field, or follow the per-client steps below.

Per-client install

Claude Desktop (macOS / Windows)

  1. Open Claude Desktop → Settings → Developer → Edit Config
  2. Add this block (merge with any existing mcpServers):
{
  "mcpServers": {
    "year-in-review": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.yearinreviewapp.com/sse"
      ]
    }
  }
}
  1. Fully quit Claude Desktop (⌘Q) and reopen.
  2. Ask: “List my Year in Review trackers.” Claude will prompt you to sign in.
mcp-remote is a small local bridge that auto-handles OAuth — Claude Desktop doesn’t yet speak HTTP MCP natively.

Official docs ↗

Claude (web / iOS / Android)

  1. Open Claude → Settings → Connectors → Add Custom Connector
  2. Paste the server URL above and follow the OAuth prompts.
  3. Once connected, the connector appears under All connectors on every device signed in to your Claude account.

Official docs ↗

ChatGPT (desktop app)

  1. ChatGPT desktop app → Plugins → MCPs → Add → Add MCP server
  2. Give it any name and set Type to STDIO.
  3. Command to launch: npx
  4. Arguments, one per row: -y, mcp-remote, https://mcp.yearinreviewapp.com/sse
Desktop only — the ChatGPT mobile apps have no MCP settings yet. On a phone, use Claude instead.

Official docs ↗

Cursor / Windsurf / Raycast / other MCP clients

Point any MCP client at the server through mcp-remote, which handles the sign-in for you:

{
  "mcpServers": {
    "year-in-review": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.yearinreviewapp.com/sse"
      ]
    }
  }
}

The first run opens a browser to sign in to your Year in Review account. No API key needed.

Official docs ↗

Available tools

The connector exposes 20 read and write tools for your trackers. A few examples of what the AI can do:

Writes go through your app in real time via cloud sync, so edits from AI show up instantly on your phone.

Troubleshooting

I didn’t get the sign-in email

Check your spam or junk folder — the sender is [email protected]. Supabase rate-limits OTP requests to one every 60 seconds, so wait a minute before re-requesting. If the email still doesn’t arrive after 2–3 minutes, your provider may be filtering it; try a different email address on the sign-in page.

The sign-in link opens an “expired session” page

Magic links expire 10 minutes after they’re issued, and the PKCE session that pairs with them lives for the same window. If you left the email open too long, start the flow over from your MCP client (it will issue a fresh link).

The AI can’t find my trackers after connecting

You’re likely signed in as a different Year in Review account than the one holding your trackers. Sign out of the connector in your MCP client (Claude → Settings → Connectors → Disconnect), then reconnect and choose the sign-in method tied to your actual account.

Tool calls fail with an auth error mid-conversation

Access tokens last one hour and refresh automatically. If the refresh itself fails (e.g. after a long idle period or a password/account change), your client will show an auth error on the next tool call — disconnect and reconnect the connector to issue a new token.

”Rate-limited” error

Per-user limits are 60 tool calls per minute and 500 per day. Normal conversational use stays well under these. If you hit them, wait 60 seconds and retry.

The OAuth consent screen shows the wrong client name

MCP clients self-register on first connect via Dynamic Client Registration, so the name reflects what the client sent to us (e.g. “Claude”, “ChatGPT”, or the client’s default label). This doesn’t affect permissions — you’re still connecting to Year in Review.

How do I revoke access?

Remove the connector in your MCP client — Claude → Settings → Connectors → Disconnect, or the equivalent in whichever client you used. That invalidates the OAuth session on our side too, so access stops immediately.

Something else

Email [email protected] with the client you’re using (Claude Desktop, Claude web, ChatGPT, Cursor, etc.), the step where it broke, and — if possible — a screenshot. We usually reply within a day.

FAQ

What data does the connector access?

Your trackers’ schema, day entries, and user settings (timezone). Nothing outside the app.

Can I revoke access?

Yes. Remove the connector in your MCP client and the OAuth session is invalidated on our side at the same time.

What do you store when I connect?

Your MCP client holds a short-lived access token; we store only the session it refreshes from, never your password. Access tokens last an hour and refresh automatically. Remove the connector and that session is invalidated.

Are there rate limits?

Yes — 60 tool calls per minute and 500 per day per user. Normal conversational use stays well under these.

Does the AI see my notes and entries?

Only the entries the AI explicitly reads in response to your prompt (e.g. when you ask about a streak). We never log the content of your entries or the text of your prompts. We do log tool name, status, and duration for operational debugging.

Questions? [email protected]