Skip to main content

Fellow's MCP Server

Fellow's Model Context Protocol (MCP) Server allows you to ask your AI Assistant about your meetings

Fellow's MCP server allows you to connect your AI meeting notes, action items, transcripts, calendar events, and more to your favourite AI assistants.

The MCP server is a connector that enables your AI assistants, like Claude or ChatGPT, to securely access and retrieve information from your Fellow workspace, so you can ask questions about your meetings and get answers instantly, without switching between apps.

The MCP Server only gives users access to the data they already have access to within Fellow.

Benefits of the MCP Server

  • Ask anything about your meetings - Get answers to questions like "What were my action items this week?" or "What did we decide in last month's standup?"

  • All your context in one place - Reference meeting context within your AI assistant of choice, alongside your other Connectors and memories

  • Portable across AI Assistants - Fellow’s MCP Connector works with any AI tool that supports connectors, so you're never locked into one platform

  • Secure access - Only accesses data you already have permission to view in Fellow

Enabling the MCP Server for your account

For users to access the Fellow MCP server, an admin must first enable the capability for your workspace by visiting Workspace Settings > Fellow MCP > MCP connection: 

Admins can see every connection under User MCP client connections.


Control which tools your workspace can use

As a workspace admin, you decide which MCP tools your members’ AI assistants can use. This lets you allow read-only tools while keeping agenda-editing tools off, or open everything up, whatever fits your workspace.

You'll find these controls under Workspace Settings > Security > Available tools.

Each tool has its own switch. Turn a tool on to let members’ AI assistants use it, or off to make it unavailable across your workspace.

Set the default for new tools

New tools are allowed automatically while Allow new tools by default is on. Turn it off to keep them unavailable until you turn them on yourself. A tool showing (default) is following this workspace default; once you toggle a tool directly, it keeps your choice regardless of the default.

Tools that depend on other tools

Some tools need another tool to work. Edit agenda and Write agenda both need Read agenda, because they read a note before changing it. If Read agenda is off, those switches are greyed out; turn on Read agenda first, then enable the editing tools.

Review changes in the audit log

Every time a tool is turned on or off, Fellow records it in your Workspace audit log, including who made the change.

Connecting Fellow to your AI Assistant

The process for setting up the Fellow MCP server will vary depending on your AI assistant. Below are instructions for some of the most popular platforms.

Claude

Fellow has an official Connector in Claude's directory. This connector has been verified by Anthropic for quality and security standards, and can be used with the click of a button: no URL configuration or developer mode needed!

Admin setup: These steps must be done by an admin of your Claude account:

  1. Add Fellow as a Claude connection:

    1. In Claude Settings, select Connectors -> Browse connectors

  2. Search for Fellow.ai:


    Click "Add to your team" to make the Connector available to your organization.

Once the above admin setup steps are complete:

  1. Each user can enable the Fellow connector by clicking the Connectors icon in Claude and

    1. Toggling on the Fellow MCP connector

    2. Authenticating their user

  2. From there, you can ask anything about your Fellow meetings!

ChatGPT

These steps must be done by each individual user who wants to connect with ChatGPT:

  1. Navigate to ChatGPT Plugins and search for Fellow.
    ​

  2. Select the Fellow.ai plugin and then click on Install

  3. Follow the process to log into your Fellow account and grant the access permissions ChatGPT needs.

Cursor

  1. Once the MCP server is enabled for your workspace, users can visit User Settings -> Apps and Integrations and click the Cursor tile.

  1. Clicking the tile will open Cursor Settings, with an option to install the Fellow MCP Server.

  2. Follow the prompts in Cursor to authorize Cursor to connect to Fellow.

MS Copilot

You can connect Fellow to Microsoft Copilot in two ways. Which one you use depends on your Microsoft license.

Copilot Cowork

Copilot Cowork requires a Microsoft Copilot license. If you don't have one, you can still connect Fellow through Copilot Studio.

Fellow for Copilot is a built-in plugin for Copilot Cowork. You don't need a server URL or a custom agent. Just sign in to your Fellow account, and it's ready to use. Copilot can then use your meeting notes, transcripts, and action items alongside your emails and Teams chats. Fellow for Copilot currently has read-only access. It can search and read your meeting data, but it can't create or edit agendas.

To add Fellow to Copilot Cowork:

  1. In Copilot Cowork, go to Settings → Chat settings → Sources.

  2. Search for Fellow.

  3. Select Fellow.ai for Copilot and sign in to your Fellow account to authorize the connection.

You can also add Fellow from the Microsoft Marketplace.

Copilot Studio

Copilot Studio works for all Fellow customers and gives your agent access to every MCP tool your workspace allows. These steps must be done by a Microsoft admin with access to Copilot Studio:
​
Go to copilotstudio.microsoft.com and create a new agent.

  1. Open the Tools tab and click Add tool.

  2. Select Model Context Protocol.

  3. Fill in the New Connector details with:

    • Name: Fellow

    • Description: Use context from your meetings, action items, and AI notes

    • MCP Server URL: https://fellow.app/mcp

    • Authentication: OAuth 2.0 > Dynamic Discovery

  4. Click on 'Create'

  5. Click Create new connection and log into your Fellow account to authorize the connection.

  6. Once connected, click Add and configure.

⚠️ Before sharing your agent: Fellow uses per-user connections to the MCP server to protect privacy. If you share your Copilot agent with others, they will have access to your Fellow data, including meeting recaps, notes, and calendar events. To preserve privacy, each person should connect their own Fellow account rather than sharing a single agent connection.


Managing MCP Connections

In User Settings > API & MCP Connections, users can:

  • View active connections

  • Delete unwanted connections

In Workspace Settings > Fellow MCP, admins can:

  • Disable MCP access for the entire account

  • View active connections

  • Delete unwanted MCP connections


Use Cases and Examples

With the Fellow MCP server connected, you can use your AI assistant to:

Analyze & Summarize Across All Meetings

  • "What challenges have been brought up consistently in our stand-ups this month?"

  • "Summarize the positive and constructive feedback I provided Jake in our 1-on-1s last month."

Recall a Specific Detail

  • "Who said we needed to move the launch date to July?"

  • "What were my action items from the strategy meeting last week?"

Faster Meeting Prep

  • "What did we discuss in the last marketing team meeting?"

  • "What talking points should I raise based on last week's project check-in?"

Keep Yourself Accountable

  • "What are my open action items from this week’s meetings?"

  • "Confirm the next steps from our roadmap review."

Use meeting context alongside other Connectors

  • Fellow + Linear:

    • “Based on my meetings this week, which Linear issues should I prioritize?"

    • "What blockers were mentioned in my standups that relate to my open Linear tickets?"

    • "Compare the project timeline discussed in our planning meeting to the current status of tickets in Linear."

  • Fellow + Google Drive:

    • "What decisions from yesterday's meeting relate to the Q4 strategy doc in my Drive?”

    • "Summarize action items from my 1-on-1s and find the relevant project docs I need to update."

  • Fellow + Gmail:

    • “Find my last emails with each of the clients discussed on today’s call.”

    • “Send a follow-up email based on the sales call I just finished, and our previous email conversations.”

Frequently Asked Questions

What is an MCP server and how does it work with my meeting notes?

An MCP (Model Context Protocol) server is a secure connector that allows AI assistants like Claude or ChatGPT to access your meeting information. Fellow's MCP server enables your AI assistant to retrieve meeting notes, transcripts, action items, and calendar events directly from your Fellow workspace, so you can ask questions and get instant answers without switching between apps.

Is the Fellow MCP server secure?

Yes, Fellow's MCP server is built with security as a priority. It uses OAuth authentication to ensure secure connections, only provides access to data you already have permission to view in Fellow, and gives workspace admins full control over whether users can create MCP connections. All connections are logged in your workspace security settings for complete visibility.

Which AI assistants work with Fellow's MCP server?

Fellow's MCP server works with any AI assistant that supports the Model Context Protocol, including Claude, ChatGPT, and Cursor. This means you're not locked into a single platform and can use your preferred AI tool while maintaining access to all your meeting data.

Do I need admin permissions to connect Fellow to my AI assistant?

For individual users to connect Fellow to their AI assistant, a workspace admin must first enable MCP connections in Fellow's Workspace Settings under Security. Additionally, some AI platforms like Claude and ChatGPT require an admin to add Fellow as a connector before individual users can authenticate and use it.

What meeting information can I access through the MCP server?

Through Fellow's MCP server, you can access all the meeting data you already have permission to view in Fellow, including AI-generated meeting summaries, transcripts, action items, talking points, decisions, calendar event details, and meeting attendees. This allows you to ask questions like "What were my action items this week?" or "What did we discuss in last month's standup?"

What's the difference between Fellow in Copilot Cowork and connecting through Copilot Studio?

Both connect Copilot to Fellow's MCP server. Fellow for Copilot is a built-in plugin for Copilot Cowork, so there's nothing to configure: you sign in to Fellow, and it's ready to go. It requires a Microsoft Copilot license and currently has read-only access. Copilot Studio requires a Microsoft admin to build an agent, but it's available to all customers and can use every MCP tool your workspace allows, including the agenda tools.

Can I control who has access to the MCP server in my organization?

Yes, workspace admins have complete control over MCP access. Admins can enable or disable MCP connections for the entire workspace, view all active connections, and delete specific connections as needed through Workspace Settings -> Security. Individual users can also manage their own connections in User Settings -> API & MCP Connections.

What tools are available through the MCP server?

Fellow’s MCP server offers tools for reading your meeting data and for working with your agendas. Which tools your AI assistant can use depends on your workspace settings — see Control which tools your workspace can use above.

Read your meeting data

  • get_action_items (Get action items)

  • get_meeting_participants (Get meeting participants)

  • get_meeting_summary (Get meeting summary)

  • get_meeting_transcript (Get meeting transcript)

  • search_meetings (Search meetings)

  • list_channels (List channels)

  • get_channel_details (Get channel details)

Read and edit your agendas

  • read_agenda (Read agenda): read a note’s current contents.

  • write_agenda (Write agenda): create an agenda for a meeting, or replace an existing agenda’s contents.

  • edit_agenda (Edit agenda): make a targeted change, such as adding a talking point or an action item, without rewriting the whole note.

  • rename_agenda (Rename agenda): change a note’s title without changing its contents.

Work with your agenda templates

  • search_agenda_templates (Search agenda templates): find saved templates by title, or list the most recently updated ones.

  • get_agenda_template (Get agenda template): read one template's contents, or read the template a meeting series starts each of its notes from.

  • create_agenda_template (Create agenda template): save a new template. New templates are personal unless you ask for a workspace-wide one.

  • edit_agenda_template (Edit agenda template): change a template's contents, title, or description.

  • delete_agenda_template (Delete agenda template): permanently delete a saved template.

  • apply_agenda_template (Apply agenda template): put a template's contents into one meeting's agenda.

  • set_default_agenda_template (Set default agenda template): fmake a template the default for a whole series, so every future note in that series starts from it.

The agenda tools respect your existing permissions: your AI assistant can only edit notes you have permission to edit, and notes you can only view stay read-only.

Did this answer your question?