Fellow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FELLOW_API_KEY | Yes | Your Fellow API key | |
| FELLOW_SUBDOMAIN | Yes | Your Fellow workspace subdomain (the part before .fellow.app in your URL) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_meetingsC | Search for meetings/recordings in Fellow. Can filter by title, date range, or event ID. Returns a list of meetings with basic metadata. |
| get_meeting_transcriptA | Get the full transcript of a meeting recording. Returns diarized (speaker-labeled) and timestamped transcript segments. |
| get_meeting_summaryC | Get the meeting summary/notes content. Returns the structured notes including agenda items, discussion topics, and decisions made. |
| get_action_itemsC | Get action items from a meeting. Extracts action items from the meeting notes content. |
| get_meeting_participantsC | Get the list of participants/attendees for a meeting. Returns email addresses of people who were invited to the calendar event. |
| sync_meetingsA | Sync meetings from Fellow API to local database. By default does incremental sync (only new/updated since last sync). Use force=true for full re-sync. |
| get_all_action_itemsA | Get all action items from the local database. Automatically performs incremental sync first to ensure data is fresh. Can filter by assignee, completion status, or date range. |
| get_meetings_by_participantsC | Find meetings that included specific participants. Searches the local database. |
| search_cached_notesB | Full-text search across all cached meeting notes. Searches titles and content. |
| get_sync_statusB | Get the current sync status and database statistics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have distinct purposes, such as get_action_items for extracting from notes versus get_all_action_items for querying the database, but there is some potential confusion between get_meeting_summary and get_meeting_transcript as both relate to meeting content. The descriptions clarify the differences, but overlap exists in the meeting data domain.
All tool names follow a consistent snake_case pattern with clear verb_noun structure, such as get_action_items, search_meetings, and sync_meetings. This uniformity makes the tool set predictable and easy to navigate for an agent.
With 10 tools, the server is well-scoped for managing meetings and action items in Fellow, covering key operations like retrieval, search, and synchronization. Each tool serves a specific function without redundancy, making the count appropriate for the domain.
The tool set provides comprehensive coverage for reading and searching meeting data, action items, and sync status, but lacks write operations such as creating or updating meetings or action items. This minor gap may require workarounds but does not severely hinder core workflows.