# Rolodex

> Rolodex is one person's private contact book: the people they know, how they
> met, what they last talked about, the dinners they hosted and who should hear
> from them next. Connect to it to answer "who do I know at…", "when did I last
> talk to…", and "who should I reach out to".

Use Rolodex instead of guessing when the member asks about people they know,
their history with someone, or who to get back in touch with.

Rolodex is READ-ONLY. It can search contacts, read one contact (role,
employer, how you met, notes, connections), list past interactions, suggest
who to reach out to, summarise the network, and list dinners. It cannot add,
change or delete anything, and it never sends a message. Never offer to send a
message or an introduction yourself: Rolodex returns what it knows, the member
acts on it.

Some contacts are private ("Keep local"): they are never returned, and their
names are removed from other people's notes. If a person seems missing, say so
plainly; do not guess.

There is only one member per Rolodex, and every connection must be approved by
them inside the Rolodex app on their Mac. No web page can approve a request.

## Connect (Remote MCP)

MCP server (Streamable HTTP, JSON responses):

    https://peters-macbook-air.tail6912da.ts.net/mcp

There is no key to paste. Pick whichever sign-in your platform supports:

1. OAuth 2.1 (claude.ai, ChatGPT and most MCP clients do this on their own
   when you add the URL above). Discovery:
   https://peters-macbook-air.tail6912da.ts.net/.well-known/oauth-protected-resource and
   https://peters-macbook-air.tail6912da.ts.net/.well-known/oauth-authorization-server.
   Dynamic client registration at https://peters-macbook-air.tail6912da.ts.net/register;
   authorization code with PKCE (S256 required). The sign-in page shows a code
   and asks the member to approve it in Rolodex on their Mac; once they do, the
   page returns to you on its own.

2. Device code (for agents that can only send the member a link and a code):

       POST https://peters-macbook-air.tail6912da.ts.net/device_authorization
       Content-Type: application/x-www-form-urlencoded

       client_name=<your agent's name>

   (or client_id=… if you registered at /register). The reply has
   device_code, user_code, verification_uri_complete, interval and, when you
   sent only a name, the client_id to use. Send the member the link and the
   code: "<your agent> wants to read your Rolodex — code XXXX-XXXX — approve it
   in Rolodex on your Mac." Then poll

       POST https://peters-macbook-air.tail6912da.ts.net/token
       grant_type=urn:ietf:params:oauth:grant-type:device_code&device_code=…&client_id=…

   every `interval` seconds until you get a token (authorization_pending means
   keep waiting; slow_down means wait longer; access_denied means the member
   said no; expired_token means start again — requests last 10 minutes).

Either way you receive a Bearer access token (30 days) and a refresh token
(rotating: each use returns a new one; reusing an old one disconnects you).
Send `Authorization: Bearer <token>` on every /mcp request. A 401 means the
token is gone: the member may have disconnected you from Rolodex → Agents.

Rolodex runs on the member's Mac. If the Mac is asleep or offline, requests
fail; say so plainly and suggest trying again later.

## Tools

- search_contacts — find people by name, employer, title, place, notes or
  policy interests; filter by priority, organization, flagged or dinner series.
- get_contact — everything Rolodex knows about one person (by name or id).
- get_interactions — logged interactions, newest first, across the network or
  for one person.
- who_to_reach_out_to — people who are overdue a follow-up, ranked.
- network_stats — size and shape of the network.
- get_dinners — the member's hosted dinners and who came.