Productivity & Project Management · Fellow.ai MCP + Claude
Fellow.ai MCP with Claude: Turn Meeting Notes into Tracked Action Items
The short answer
Claude connects to Fellow.ai through the Model Context Protocol (MCP), a secure standard that lets Claude read meeting notes and transcripts and carry out approved actions such as creating action items, updating agendas and managing calendar events. Access uses Fellow's supported sign-in method and is limited to the permissions your organisation grants.
What is Fellow.ai MCP?
Fellow.ai is a meeting productivity platform. It holds meeting notes, transcripts, events, agendas and action items in one place, so teams can keep the context of their conversations together. Typical users include managers running regular team meetings, operations leads tracking decisions, and project teams who need a record of who agreed to do what. Fellow helps turn conversations into work that can be followed up.
How Claude connects to Fellow.ai MCP through MCP
The Model Context Protocol is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and the tool. Once Fellow.ai is connected, Claude can work with your meeting information in plain language, without anyone needing to learn a new interface for each request.
Once connected, Claude can typically read meeting notes and transcripts, summarise what was discussed, pull out decisions, create action items, and view or adjust agendas and calendar events. You can ask for a summary of last week's client review and a list of follow-ups, and Claude can prepare them for you.
Permissions and approvals keep people in charge. Access is granted through Fellow's supported sign-in method, and the connection is limited to what your organisation allows. Consequential actions, such as assigning tasks to colleagues or changing a shared calendar, can be set to require a person's approval before they happen, and every action can be logged for review.
What you can automate
Meeting summaries for busy managers
A manager finishes a day of meetings and asks Claude for short summaries of each one. Claude reads the notes and transcripts and produces a concise recap covering key points, decisions and open questions. The manager can review it in minutes instead of rereading full notes, and share the summary with colleagues who could not attend.
Action items captured from every conversation
Commitments made in meetings often get lost. Claude can review a transcript, identify who agreed to do what and by when, and create action items in Fellow for each owner. This gives teams a single, trackable list of follow-ups rather than scattered notes in chat threads and inboxes.
Agenda preparation before recurring meetings
Before a weekly team meeting, a team lead can ask Claude to review the previous meeting's open items and draft a fresh agenda. The draft can be checked and adjusted by the lead before it is shared. This keeps recurring meetings focused and stops unfinished points from being forgotten.
Calendar coordination for project teams
Project coordinators often spend time rescheduling follow-up sessions after a meeting. With Claude, they can describe the next steps in plain English and ask for suitable follow-up events to be set up or updated, with approval required before any invitations are sent. This reduces administrative effort across the team.
Searching institutional memory
When a new team member asks why a decision was made six months ago, finding the answer can take a long time. Claude can search across meeting records and explain the relevant discussion, with links back to the source notes for verification. This helps organisations keep their knowledge without relying on individual memory.
An end-to-end workflow: Weekly client review to project tracker
TriggerA client review meeting ends and its transcript is saved in Fellow.ai.
Claude reads the transcript and generates a summary of decisions and open questions.
Claude identifies each action item, its owner and its due date mentioned in the discussion.
The action items are created in Fellow.ai and listed for the project lead to review.
After approval, the same tasks are added to the project tracker in Microsoft 365 or the team's ticketing system.
A short summary is drafted for the client and held for sign-off before it is sent.
OutcomeFollow-ups reach the right owners the same day, decisions are recorded in one place, and the project lead spends less time on manual admin. Results vary by organisation and workflow.
How we set it up
Free automation audit
We review how your teams use Fellow.ai today and identify the meetings and workflows that would benefit most from Claude, such as summaries, action tracking or agenda preparation.
Secure connection
We connect Claude to Fellow.ai using the supported DCR OAuth sign-in method. Access is set up with least-privilege permissions, so Claude can only reach the meeting data and actions your organisation approves.
Workflow design
We design the end-to-end workflow across Fellow.ai and your other systems, such as Microsoft 365, your CRM or your ticketing tool. We define where people must approve actions before they take effect.
Testing with real meetings
We test the workflow against past meeting records to check the accuracy of summaries and action items, then refine the prompts and permissions based on the results.
Launch, monitoring and training
We launch with monitoring and audit logs, and train your team on how to use Claude with Fellow.ai in daily work, including how to review and approve what Claude prepares.
Who benefits
- Operations director
- Gains a consistent record of decisions and follow-ups across teams, with fewer dropped commitments.
- Team manager
- Receives quick meeting summaries and ready-to-review action items without manual note-taking.
- Project coordinator
- Spends less time on admin such as chasing owners, updating trackers and rescheduling follow-ups.
- IT or department head
- Sees a controlled, auditable connection with clear permissions and approval steps.
Security and control
- Access uses Fellow's supported DCR OAuth sign-in, with least-privilege permissions limited to what your organisation approves.
- Consequential actions such as assigning tasks or changing shared calendars can require human approval before they take effect.
- Audit logs record what Claude reads and does, supporting review and accountability.
- Sensitive meeting content is handled according to your data policies, and we agree on what Claude may and may not access before launch.
- Claude's suggestions, summaries and action items are reviewed by people before they are relied on or shared externally.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can set up the connection to match their internal data handling policies and sector rules. In India, deployments can be configured to align with the Digital Personal Data Protection Act, 2023. Organisations in the UAE and Saudi Arabia can meet local data protection requirements in their region. Custom applications built on Claude can be hosted in India, the United States, the United Kingdom or the European Union, and the hosting region is chosen to meet your legal and compliance requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Fellow.ai MCP server do?
The Fellow.ai MCP server acts as a secure bridge between Fellow and AI tools such as Claude. Through it, Claude can read meeting notes and transcripts, summarise conversations, create action items, and manage calendar events and agendas using natural language. Fellow also offers a direct API for organisations that prefer that route.
Is connecting Claude to Fellow.ai secure?
Security depends on how the connection is configured. Access uses Fellow's supported DCR OAuth sign-in method, and we set permissions with least privilege so Claude only reaches the data your organisation allows. Approvals for consequential actions and audit logs add further control and oversight.
What can Claude do with Fellow.ai once connected?
Typically, Claude can read meeting notes and transcripts, produce summaries, identify decisions and open questions, create action items, and view or update agendas and calendar events. The exact actions available depend on the permissions granted during setup.
How long does setup take?
Timelines vary with the number of workflows and the other systems involved. A focused connection with a single workflow is often quicker than a multi-system programme. We confirm a realistic timeline during the free automation audit.
Which plan or permissions are needed?
Requirements depend on your Fellow.ai account setup and your organisation's policies. In general, the connecting user needs permission to access the meeting data and actions you want Claude to use. We review this with your administrators during the audit so the connection matches what your account allows.