Fellow.ai
by Fellow.ai
Pull meeting transcripts, summaries, action items and participants from a Fellow workspace into your AI assistant. Anthropic labels it Read, but Fellow documents agenda and template writes and advertises a write_meeting_agenda scope. Access mirrors what you can already see in Fellow.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Fellow.ai via MCP
https://fellow.app/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Fellow.ai Tools & Capabilities (5)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The directory permissions label understates the surface.
Readsits over eighteen documented tools, eleven of which write and one of which permanently deletes a template. Review Fellow's tool list, not the listing. - We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no schemas and no safety annotations were readable. Read/write classification here is Fellow's documentation, restated.
- The permission claim is Fellow's, not our observation. We did not authenticate, so we could not test what a tool returns when asked for a meeting the user cannot see. Fellow does not document that behaviour either.
search_meetingsscope is undocumented. Fellow does not say whether it matches titles, summaries or full transcript text.- Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, but the gated endpoint blocked our own
prompts/list, so we cannot say whether the server serves any. - Channels widen the corpus. Fellow states channel membership grants access to every recording, summary and transcript published in that channel, and public channels are joinable by any workspace member. Two documented tools read that surface.
- Consent capture is Enterprise and Microsoft-only. Fellow states it is currently available for workspaces on Microsoft 365 Calendar, with Google Calendar support planned.
- Disclosure emails are off by default. Fellow documents the recording disclosure policy as disabled until an admin turns it on, and configurable to reach external invitees only.
- Two recording modes show participants nothing from Fellow. Fellow states that with botless recording the user must notify participants, and that Zoom native capture displays no Fellow bot or Fellow chat message.
- Retention controls are Enterprise, workspace-wide, and irreversible. Fellow documents no user-level override, deletion of existing material within an hour of saving with no prior warning, and no way to undo it.
- AI summaries survive transcript deletion. Fellow states summaries are not subject to automatic deletion, so a workspace that deletes transcripts may still expose their substance through
get_meeting_summary. - Both ends need an admin. A Fellow workspace admin must enable MCP connections, and Claude and ChatGPT deployments need an admin on that side to add the connector first.
- Shared Copilot agents share your data. Fellow warns that sharing a Copilot Studio agent built on your own connection gives recipients access to your recaps, notes and calendar events.
Frequently asked questions
Whose meetings can the Fellow MCP connector read?
Only the meetings you can already open in Fellow yourself. Fellow states the MCP server gives users access solely to data they already have permission to view, and that agenda tools honour the same edit permissions. Fellow's separate access article says notes default to calendar attendees only, and that workspace administrators get no extra note visibility beyond any other user.
Does the Fellow MCP server only read, or can it write?
It writes. Fellow's MCP page documents eleven agenda and template tools, including `write_agenda`, `edit_agenda`, `rename_agenda`, `create_agenda_template`, `edit_agenda_template` and `delete_agenda_template`, which Fellow describes as permanently deleting a saved template. The server's own OAuth descriptor advertises a `write_meeting_agenda` scope alongside four read scopes. Anthropic's directory labels the connector Read.
Can my AI assistant read meetings recorded before I connected it?
Fellow's documentation does not put any time boundary on MCP access, and its use cases invite questions spanning months of history. What limits the reachable history is retention, not the connector: Fellow documents Enterprise auto-deletion policies that permanently remove recordings and transcripts on a schedule set by admins, while AI summaries persist unless explicitly included.
What can search_meetings actually search across?
Fellow does not publish the field-level scope of `search_meetings`, so we cannot say whether it matches titles only or full transcript text. Fellow's own web search interface offers a dedicated Transcripts tab that matches keywords inside transcripts, and the connector's advertised examples ask who said what. Treat full-text reach as likely but undocumented.
Does Fellow notify meeting participants that a meeting is being recorded?
Partly, and it depends on the recording method. Fellow says its Note Taker joins as a visible participant with an in-meeting message once admitted, and Enterprise workspaces can require a consent page before joining. Fellow states plainly that with botless recording it is up to the user to notify participants, and that Zoom native capture shows no Fellow notification.
Do I need an admin to enable the Fellow MCP connector?
Yes, twice over in most setups. Fellow requires a workspace admin to switch on Allow users to create MCP connections under Workspace Settings, Security, before any user can connect. Fellow also notes that Claude and ChatGPT deployments need an admin on that side to add Fellow as a connector first. Individual users then authenticate their own account.
Can a workspace admin block the agenda-writing tools?
Yes, per tool. Fellow documents an Available tools list under Workspace Settings, Security, MCP connection, where each tool has its own switch, so an admin can allow read-only tools and leave agenda editing off. A separate default governs newly released tools. Every toggle is recorded in the workspace audit log with who changed it.
Sources
- Fellow's MCP server — https://help.fellow.ai/en/articles/12622641-fellow-s-mcp-server (fetched 2026-08-19; also read as Markdown via the
.mdsuffix) · retrieved 2026-08-19 - Who can see my meeting notes? — https://help.fellow.ai/en/articles/4073990-who-can-see-my-meeting-notes (fetched 2026-08-19) · retrieved 2026-08-19
- Meeting Compliance with Fellow Note Taker — https://help.fellow.ai/en/articles/9496960-meeting-compliance-with-fellow-note-taker (fetched 2026-08-19) · retrieved 2026-08-19
- Capture Consent for Auto-Recorded Meetings — https://help.fellow.ai/en/articles/15346403-capture-consent-for-auto-recorded-meetings (fetched 2026-08-19) · retrieved 2026-08-19
- Pre-meeting Disclosure — https://help.fellow.ai/en/articles/10715814-pre-meeting-disclosure (fetched 2026-08-19) · retrieved 2026-08-19
- Meeting Recording Auto-Deletion — https://help.fellow.ai/en/articles/8525750-meeting-recording-auto-deletion (fetched 2026-08-19) · retrieved 2026-08-19
- Recording Channels — https://help.fellow.ai/en/articles/9518898-recording-channels (fetched 2026-08-19) · retrieved 2026-08-19
- AI Meeting Transcript — https://help.fellow.ai/en/articles/9824711-ai-meeting-transcript (fetched 2026-08-19) · retrieved 2026-08-19
- Fellow help centre machine index — https://help.fellow.ai/llms.txt (fetched 2026-08-19) · retrieved 2026-08-19
- Fellow marketing machine index — https://fellow.ai/llms.txt (fetched 2026-08-19; source for the Zero-Day Retention description) · retrieved 2026-08-19
help.fellow.ai/robots.txtdisallows only three internal paths and names a sitemap;fellow.ai/robots.txtis a bareAllow: /. Neither host sets aContent-Signalheader or directive, so no axis was expressed on training, search or AI input (fetched 2026-08-19). The help centre blocks plain curl and was fetched with a browser user agent · retrieved 2026-08-19- Live RFC 9728 protected-resource descriptor — https://fellow.app/.well-known/oauth-protected-resource (fetched 2026-08-19; the path-append and path-insert forms both return the application's HTML with a 404) · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://fellow.app/.well-known/oauth-authorization-server (fetched 2026-08-19; same five scopes as the resource descriptor) · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19: a POST to the endpoint returns HTTP 401
Unauthorizedwithwww-authenticate: Bearer realm="Restricted"· retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/069b18da-5c89-4a66-941f-0cb6eae49a8d (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Communication
- Developer
- Fellow.ai
- Tools
- 5
- Domain
- fellow.app
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.