AgentMail
Give an AI agent its own email inbox: create inboxes, read threads and send mail to anyone.
Pull meeting transcripts, summaries, action items and participants from Fellow.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Fellow MCP server connects a Fellow meeting workspace to Claude, ChatGPT, Cursor and any MCP-compatible agent. It pulls verbatim meeting transcripts, AI summaries, action items and participant lists into the model's context, and — beyond what Anthropic's directory lists — Fellow documents tools that create and edit meeting agendas. Access mirrors your own Fellow permissions.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Read sits over eighteen documented tools, eleven of which write and one of which permanently deletes a template. Review Fellow's tool list, not the listing.search_meetings scope is undocumented. Fellow does not say whether it matches titles, summaries or full transcript text.prompts/list, so we cannot say whether the server serves any.get_meeting_summary.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.
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.
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.
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.
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.
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.
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.
.md suffix) · retrieved 2026-08-19help.fellow.ai/robots.txt disallows only three internal paths and names a sitemap; fellow.ai/robots.txt is a bare Allow: /. Neither host sets a Content-Signal header 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-19Unauthorized with www-authenticate: Bearer realm="Restricted" · retrieved 2026-08-19Connect Fellow.ai once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.