Fellow.ai

Put a saved agenda template's content into one meeting's agenda. This replaces that agenda's current contents and affects only that one note — it does not change the template, and it does not change what future meetings in the series look like (use set_default_agenda_template for that). Identify the agenda by note_id or meeting_id, and the template by template_id from search_agenda_templates.

apply_agenda_template

Archive a Fellow action item the user no longer plans to do, or pass archived=false to restore it. Get the item's id from get_action_items first. If more than one item could be the one the user means, list them with their meeting and date and ask which one. Never pick between them yourself. When exactly one item matches, archive it without asking for confirmation; it can be restored. The response shows the item's status after the change; report what it says. IMPORTANT: This tool is currently unavailable because the user has not granted the required permission (write_action_items). Do not call this tool; the call will be rejected. The user can enable it by disconnecting and reconnecting the Fellow MCP server, which asks for the permission again. When this tool would be relevant to the conversation, tell the user it exists and recommend reconnecting Fellow to enable it.

archive_action_item

Mark a Fellow action item complete, or pass completed=false to mark it incomplete again. Get the item's id from get_action_items first: search with the user's own words and only_ongoing_action_items=true when completing. If more than one item could be the one the user means, list them with their meeting and date and ask which one. Never pick between them yourself. When exactly one item matches, make the change without asking for confirmation. On an item every assignee has to complete, this marks only the user's own part; to mark another assignee's part, pass their email as assignee_email, and only when the user asks for that person. The response shows the item's status and each assignee's status after the change; report what it says. IMPORTANT: This tool is currently unavailable because the user has not granted the required permission (write_action_items). Do not call this tool; the call will be rejected. The user can enable it by disconnecting and reconnecting the Fellow MCP server, which asks for the permission again. When this tool would be relevant to the conversation, tell the user it exists and recommend reconnecting Fellow to enable it.

complete_action_item

Create a Fellow action item. By default it goes on the user's own action items list, assigned to the user. To add it to a meeting note instead, pass the note's id as note_id; the user must be able to edit that note. Get the id from search_meetings and never guess one. If more than one meeting could be the one the user means, list them with their date and ask which one. If the user names no meeting, leave note_id empty. To assign other people, pass their emails as assignee_emails, and include the user's own email to keep them assigned too. Only set a due date or assignees the user asked for. The response is the item that was created; report what it says. IMPORTANT: This tool is currently unavailable because the user has not granted the required permission (write_action_items). Do not call this tool; the call will be rejected. The user can enable it by disconnecting and reconnecting the Fellow MCP server, which asks for the permission again. When this tool would be relevant to the conversation, tell the user it exists and recommend reconnecting Fellow to enable it.

create_action_item

Create a new saved agenda template from Fellow Markdown. Agenda templates are the named templates in the Fellow template library that a user picks from when starting a meeting note; this does not create an AI note/recap template, and it does not change any existing agenda. Creates a personal template unless the user explicitly asks for a workspace-wide one. Read fellow://docs/fellow-markdown-syntax before composing the markdown content. How to write a good agenda template. A template is the reusable skeleton of a meeting, not a filled-in agenda. Anything that is only true of one occurrence of the meeting belongs in that meeting's agenda instead, so keep it out of the template. - Sections are headings, and the heading carries the guidance. Give the section a short name (one to three words) and put the question it answers on the same heading block after `<br>`, for example `# Blockers<br>What is in the way right now?`. Most sections in Fellow's built-in templates carry that second line and about half phrase it as a question; it is what tells whoever runs the meeting what to put there. - Leave the placeholders empty. Under each section put ONE empty talking point (`- ( )`) and nothing else, so there is a spot to type into. Do not pre-write talking points about a particular project, person, week, or number. - Do not write out action items. When a meeting always ends with next steps, the convention is a closing `# Action Items` section holding one empty `- [ ]`. The tasks themselves get captured live in the agenda while the meeting happens. - No assignees, due dates, mentions, or calendar dates anywhere in a template. The same template is reused every time the meeting runs, so nothing in it can point at one person or one occurrence. - Keep it short. Four to six sections is normal and a finished template runs about a dozen blocks. A template that reads like a completed agenda has too much in it. - The one exception is a standing question list: questions asked word for word every time the template is used, such as an onboarding interview or a recurring checklist. Those can be written out as talking points, because the wording does not change between occurrences. A typical template looks like this in full: ``` # Wins<br>What went well since we last met? - ( ) # Blockers<br>What is in the way right now? - ( ) # Action Items<br>What came out of this meeting? - [ ] ```

create_agenda_template

Permanently delete a saved agenda template. This cannot be undone: the template is removed from the library, and every series that used it as their default template is left with none, so new notes there start blank until another template is set. Confirm with the user before calling this, and say how many series will be affected if you know. Agendas the template was already applied to keep their content. Only the template's own owner (or a workspace admin, for a workspace template) can delete it, and Fellow's built-in templates cannot be deleted. Takes a template_id from search_agenda_templates, never a note or meeting: deleting 'the template this meeting uses' would remove a template other series may also point at.

delete_agenda_template

Display meeting search results in an interactive visual widget optimized for browsing and selection. This tool renders meeting search results in a rich, interactive widget interface that enables users to: - Visually scan and browse meeting results with rich formatting - See meeting metadata, participants, and summaries at a glance - Select and interact with individual meetings - Navigate through collections of meetings efficiently Use this tool when the user wants to SEE, BROWSE, or IDENTIFY meetings visually. The widget format is ideal for scenarios where the user needs to visually explore a collection of meetings rather than extract specific information or generate synthesized content. Example use cases: - "What meetings did I have with John?" - "Show me my meetings from last week" - "Which meetings mention 'HIPPAA'?" - "Display meetings where Sarah was present" - "List all meetings about the budget" The widget provides an enhanced visual experience for meeting discovery and selection, making it easier for users to find and identify the meetings they're looking for. IMPORTANT: This tool is only supported by ChatGPT (OpenAI) clients. Other MCP clients do not support interactive widgets and will not be able to render the visual output.

display_meetings

Apply one targeted edit to an existing Fellow agenda using its markdown representation, without rewriting the whole agenda. Modes: - append: Add content at the end of the agenda. - prepend: Add content at the beginning of the agenda. Append and prepend add whole blocks: the content starts its own block, so do not add a leading or trailing newline to separate it from the neighbouring block. A leading or trailing blank line renders as an empty paragraph, so include one only when you deliberately want an empty paragraph there. - find_replace: Replace the sole occurrence of `find` with content. Copy `find` exactly from the agenda body returned by read_agenda; it may be part of a line or span several lines. When it starts at the beginning of an indented line, include the leading spaces, or the edit shifts that item's indentation. Content replaces exactly that text, so keep the line breaks and blank lines between the lines you copied, indent each new line of content to the level it should sit at, and add no blank line at the start or end: one blank line separates blocks, and a second one beside it renders as an empty paragraph. To delete a whole item or block, pass empty content ("") and put its full line or lines in `find` with the line break after them (before them, for the agenda's last line). If the block has a blank line on both sides, include one of those blank lines too. Deleting only the text would leave an empty item behind. Call read_agenda first. Use find_replace to change or delete existing content, including positional or structural edits such as "the first item": copy those lines into `find`. If that text appears more than once, extend `find` with a neighbouring line until it is unique, and repeat that line, and the line break or blank line between them, unchanged in content. Pass the base_version from the read_agenda call you copied `find` from: `find` is then matched against that version, and the edit is applied on top of any changes made since. Read fellow://docs/fellow-markdown-syntax before writing new Fellow Markdown content.

edit_agenda

Update a saved agenda template. `content` replaces the whole template body, so call get_agenda_template first and send back the full text with your changes applied; title, summary, tags and visibility are changed only when supplied. Editing a template does not change any agenda it was previously applied to. Fellow's built-in (GLOBAL) templates cannot be edited. When you add a section to an existing template, match the shape of the sections already in it rather than imposing a new one. Read fellow://docs/fellow-markdown-syntax before composing the markdown content. How to write a good agenda template. A template is the reusable skeleton of a meeting, not a filled-in agenda. Anything that is only true of one occurrence of the meeting belongs in that meeting's agenda instead, so keep it out of the template. - Sections are headings, and the heading carries the guidance. Give the section a short name (one to three words) and put the question it answers on the same heading block after `<br>`, for example `# Blockers<br>What is in the way right now?`. Most sections in Fellow's built-in templates carry that second line and about half phrase it as a question; it is what tells whoever runs the meeting what to put there. - Leave the placeholders empty. Under each section put ONE empty talking point (`- ( )`) and nothing else, so there is a spot to type into. Do not pre-write talking points about a particular project, person, week, or number. - Do not write out action items. When a meeting always ends with next steps, the convention is a closing `# Action Items` section holding one empty `- [ ]`. The tasks themselves get captured live in the agenda while the meeting happens. - No assignees, due dates, mentions, or calendar dates anywhere in a template. The same template is reused every time the meeting runs, so nothing in it can point at one person or one occurrence. - Keep it short. Four to six sections is normal and a finished template runs about a dozen blocks. A template that reads like a completed agenda has too much in it. - The one exception is a standing question list: questions asked word for word every time the template is used, such as an onboarding interview or a recurring checklist. Those can be written out as talking points, because the wording does not change between occurrences. A typical template looks like this in full: ``` # Wins<br>What went well since we last met? - ( ) # Blockers<br>What is in the way right now? - ( ) # Action Items<br>What came out of this meeting? - [ ] ```

edit_agenda_template

Search action items. By default returns only action items assigned to the requesting user. Pass search to find items by their wording: it is a keyword search over the item text, the meetings the items were written in, and the meeting series name. Reach for it whenever the user quotes or names an item, giving it their own words. topic is the semantic alternative and searches the summaries of the meetings the items came from; the two can be combined. When meeting_ids are provided, defaults to returning ALL action items from those meetings (not just the ones assigned to the user) — pass only_mine=true to override this. Can also filter by date range, status, or assignee scope. Note that from_date and to_date filter on when an item was last updated, not on when its meeting took place. Every item comes back with the meeting it was written in and that meeting's start time. When the user quotes an action item and asks what it refers to, look it up here before you search for meetings. Then read any relative date in the item, such as "Monday's call", against the start time of the meeting the item belongs to rather than against today, since the item may have been written weeks ago. AI-detected items the user has not accepted yet are included and carry ai_suggested=true. Treat those as suggestions rather than things the user has committed to, and pass include_ai_suggested=false to leave them out. get_meeting_summary returns the same suggestions for a single meeting when you already have its id. If a quoted item is not found here at all, search_meetings matches action item text through its note parameter.

get_action_items