There’s a connector inside Claude that most people never turn on, and it takes about a minute to set up. Once you do, Claude can read every meeting you’ve ever had — what was decided, what you committed to, and who owns the follow-up. It’s one of those small setups that quietly changes how you use the tool. Here’s exactly how I configure it, plus the five prompts I paste into Claude to get value from day one.

The One-Minute Setup

In Claude, go to Customize, then Connectors, click the plus button, and browse the connector library. Search for “Fellow,” click Connect, sign in, authorize, and you’re done. No API keys, no developer mode, no configuration files. Two things are worth knowing before you start. If you’re on a team plan, an admin has to enable MCP connectors at the workspace level first — on the Fellow side, that’s a single toggle in admin settings. And the permissions are inherited from Fellow itself, so Claude only ever sees the meetings you already have access to.

What Claude Can (and Can’t) Do

This is a read-only relationship, which is exactly what you want. Claude can pull transcripts, summaries, action items, decisions, and attendees out of Fellow. It cannot write back to Fellow and it cannot delete anything. Fellow does the part Claude can’t: it joins your meetings — Zoom, Meet, Teams, Slack huddles, even in person — and structures everything as it goes. Decisions land in a decisions field, action items are captured with their owners attached, open questions get tagged, and attendees are recorded as people rather than names buried in a wall of transcript. Because that data is already structured, Claude can reason across meetings instead of guessing.

A Note on Security

If your organization is in healthcare, finance, or legal, this part matters. Fellow is built with security and compliance at its core, so IT leaders in regulated industries can set specific policies around data access and permissions. Claude only ever reads what your Fellow permissions already allow — it isn’t joining your meetings live, it’s reading what Fellow has already captured.

The Five Prompts I Actually Use

Once the connector is live, these are the five prompts I lean on. Paste them in, swap the bracketed details for your own, and you’re running.

1. Before a follow-up call. Two minutes before a meeting with someone you’ve talked to before: “I have a call with [person/company] coming up. Pull from Fellow every meeting we’ve had and give me three things: what I committed to, what they committed to, and what’s still open. Use the exact language from the meeting and quote us directly so I don’t paraphrase a commitment I didn’t actually make.”
2. The Friday catch-up. “Look across all my Fellow meetings from this week, find anything I said I would do — every action item or verbal commitment with my name on it — that I haven’t clearly closed out.” This is the one that catches the Monday-morning apology before it happens.
3. Find where a project slipped. “[Project name] is off track. Read every meeting where this project came up in chronological order, find the first meeting where the timeline actually slipped, and tell me what was said about it, who said it, and what was decided or not decided in response.”
4. Settle a factual dispute. “Search my Fellow meetings for where [client] and [topic] were discussed and give me the actual quote: who said what, in which meeting, and on what date. Just the record, not your interpretation.”
5. Draft the recap. “Read the meeting Fellow just captured with [person/company]. Draft a recap email with a short summary of decisions and the action items with owners and dates. Match how I normally write, and save it to my Gmail drafts so I can review and send.”

Once these five are running, you can schedule them or run them on demand. The hour you used to spend digging through transcripts becomes something you find in seconds. If you want to see Fellow’s botless recording in action, check out the video above — and let me know which prompt you’d use first.