Connect an MCP client

MCP is how an agent outside LifeOS — Claude Desktop, Claude Code, or anything else that speaks it — reads your board and leaves notes on it. Connecting one takes an address, a token, and a header. This page has all three, ready to copy, and a button that tries them.

1. The address

MCP endpoint
https://lifeos.boxysean.com/api/mcp

2. The token

The token is the one secret a client needs: it opens your board and nobody else's. Get it from Settings → Your MCP token. It is 43 characters, shown once, re-issued there if you lose it, and it never goes in the address.

3. The header

The token travels in a request header — a labelled line sent with each request, out of sight of the address bar. Either of these works; replace the placeholder with your token, with no quotes around it. If a client sends both, the Authorization one wins. Only headers are read: a ?token= in the address, or a cookie, is ignored.

Most clients
Authorization: Bearer <YOUR_TOKEN_FROM_SETTINGS>
Clients that only take an API key
x-api-key: <YOUR_TOKEN_FROM_SETTINGS>

4. Claude Desktop

Paste this into Claude Desktop's MCP settings (its config file), then swap in your token.

Client config
{ "mcpServers": { "lifeos": { "type": "http", "url": "https://lifeos.boxysean.com/api/mcp", "headers": { "Authorization": "Bearer <YOUR_TOKEN_FROM_SETTINGS>" } } } }

5. Claude Code

Run this once in a terminal, with your token in place of the placeholder.

Command
claude mcp add --transport http lifeos https://lifeos.boxysean.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN_FROM_SETTINGS>"

6. The Accept header

A client also has to say which kinds of answer it can read: both plain JSON and a stream. Claude's apps do this on their own; a hand-written request (with curl, say) has to send it. Without it the server answers 406, “Not Acceptable”.

Accept
Accept: application/json, text/event-stream

7. Try it

This sends the same first message a client sends, from this browser to the endpoint above, and tells you what came back. It reads nothing from your board and changes nothing. The token is used for this one request and then forgotten.

Send it as

If it still fails

404
No account on this deployment holds a token yet. Until one does, the endpoint does not exist.
401
The token or the header is wrong. The response says which, in its hint.
406
The Accept header is missing or incomplete (step 6).
A redirect
The client sent its request to an address that is not the endpoint. Use the one in step 1 exactly.

Once it connects, point the agent at the guide for agents before it starts.