Fellow MCP Server
Connect Fellow to your AI agents with the Fellow MCP server.
Updated
What is Fellow MCP?
The Fellow MCP server is a Model Context Protocol server that connects Fellow to AI agents and assistants as a set of tools. With it connected, an agent can work with Fellow (ai meeting assistant — agendas, notes, transcripts, action items) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Fellow tools become available to the model.
Connect the Fellow MCP server
Connect Fellow MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Fellow MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Fellow tool to confirm the connection is live.
Connect Fellow MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Fellow
Provide the Fellow MCP server URL or command and complete authentication.
- 3
Test
Reference Fellow from chat to confirm Cursor can reach the tools.
Using Fellow MCP with Gamut
On Gamut, the Fellow MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Fellow and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Fellow MCP server?
It is a Model Context Protocol server that exposes Fellow to AI agents as tools so they can work with it (ai meeting assistant — agendas, notes, transcripts, action items).
How do I connect the Fellow MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Fellow MCP server URL and complete authentication (OAuth). See the official documentation for the exact URL and scopes.
Can I use Fellow MCP with Gamut?
Yes — Gamut supports the Fellow MCP server, so your agents can use it as a tool in automated, triggered workflows.