THE SYSTEM Back to the app →
MCP · Model Context Protocol

Let your AI read your roadmap.

The System can hand ChatGPT, Claude or Grok the same record it uses: where you are going, what is on today's list, and whether the plan is working. They read it. They cannot change it.

Three steps

It takes about a minute, and you only do it once per AI.

01

Get your link

In the app: Settings → Connect your AI → Create a link. It looks like this:

https://<your-project>.supabase.co/functions/v1/mcp/<your token>

The link is shown once. Copy it before you leave the screen — the server only keeps a fingerprint of it, so nobody can read it back to you later. Lost it? Make a new one.

02

Paste it into your AI

Open your AI's connector settings and add a custom MCP server:

  1. ChatGPT — Settings → Connectors → Add custom connector
  2. Claude — Settings → Connectors → Add custom connector
  3. Grok — Settings → Connections → Add MCP server

Name it The System and paste the link as the server URL. Menu wording moves around between versions; look for MCP or custom connector.

03

Ask it something

“Look at my roadmap and tell me what to do first today.”

If it answers with your real destination and your real quests, it is connected. If it says it cannot reach the server, the link was mistyped or the token was revoked.

What it can see

Three read-only tools. Nothing else is exposed, and there is no tool that writes.

get_roadmap

Where you are going

The destination, the phase you are in, the percentage through it, the milestones under it, and the goals you marked as the ones that matter.

get_today

What is on the list

Today's quests with their status — done, still open, missed — what each is worth, and how each one gets verified.

get_record

Whether it is working

Level, experience, health, streak, which day of the run you are on, days missed, and your six stats.

Read-only, on purpose. Your phone is the one that owns the run: it syncs the whole state up every time it changes. If an AI marked a quest done from the outside, the next sync from your phone would quietly erase it — and a write that silently fails is worse than no write at all. So there is no write tool until the server owns the quest list.
The link is a key. Anyone holding it can read your roadmap, so treat it like a password: do not post it, do not put it in a shared doc. You can revoke it any time in Settings → Connect your AI, and the connector stops working within seconds. Make a separate link per AI so you can cut one without cutting the rest.

For people who build things

The endpoint speaks JSON-RPC 2.0 over Streamable HTTP, protocol 2025-06-18, POST only. The token goes in the URL because most clients only let you paste one address — send it as Authorization: Bearer <token> instead if your client allows headers. initialize and ping answer without a token; everything else needs one.