Integration

Fellow integration

Fellow is an AI meeting assistant and meeting notes app. Read meeting notes (title, event, attendees, content), recordings with full transcripts and AI notes, and action items; edit a note's agenda (replace, append, prepend, find and replace) and rename it; complete or archive action items; import recordings from a media URL and follow their import; manage webhooks for AI note and action item events. A key sees what its owner sees in Fellow; a Super Admin key (Enterprise) sees the whole workspace and can delete notes and recordings. Authentication is an API key in the X-API-KEY header, created in Fellow's User settings (Developer API, enabled by a workspace admin); the base URL uses your workspace subdomain.

Connect Fellow How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Fellow.Built from the 23 Fellow tools below, on the connection you add once.

What you can do with Fellow

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Webhook, 5 operations

create_webhookCreate webhookPOSTCreates a webhook: Fellow POSTs the chosen events (ai_note.*, action_item.*) to your url, which must echo Fellow's verification challenge. The signing secret is not passed on, so deliveries cannot be verified.
delete_webhookDelete webhookDELETEDeletes a webhook: Fellow stops sending its events. An account-wide webhook needs a privileged key, else its id reads as not found.
get_webhookGet webhookGETGets one webhook: url, description, status (active or inactive), scope and subscribed events. The secret is not returned again.
list_webhooksList webhooksGETLists the webhooks of the API key's owner (a privileged key lists the account's), 20 per page by default, up to 50. Next page: cursor = page_info.cursor of the previous answer.
update_webhookUpdate webhookPATCHUpdates a webhook's url, events, description or status (active or inactive). Leave a field out to keep it. An account-wide webhook needs a privileged key, else its id reads as not found.

Action item, 4 operations

archive_action_itemArchive action itemPOSTArchives an action item (marks it as won't do). Returns the updated action item.
complete_action_itemComplete action itemPOSTMarks an action item complete (completed true) or back to incomplete (completed false). Returns the updated action item.
get_action_itemGet action itemGETGets one action item: text, status (Done, Archived or Incomplete), due date, assignees (name and email), the note it belongs to, and whether AI detected it.
list_action_itemsList action itemsPOSTLists the action items you can see (a privileged key sees the whole account), newest first, 20 per page by default. Filter by dates, completed, archived or scope; next page: pagination.cursor = page_info.cursor.

Note agenda, 4 operations

append_note_agendaAppend note agendaPOSTAdds Fellow Markdown at the end of a note's agenda, keeping the rest. Returns the note id, title and new agenda content.
find_replace_note_agendaFind replace note agendaPOSTReplaces the one occurrence of find in a note's agenda with Fellow Markdown (an empty string deletes it). find must match exactly once: no match or several is refused (422) and nothing changes.
prepend_note_agendaPrepend note agendaPOSTAdds Fellow Markdown at the start of a note's agenda, keeping the rest. Returns the note id, title and new agenda content.
replace_note_agendaReplace note agendaPOSTReplaces a note's whole agenda with content_fellow_markdown, and/or renames the note with title (give one or both). Use append_note_agenda or prepend_note_agenda to add without replacing.

Recording, 4 operations

delete_recordingDelete recordingDELETEPermanently deletes a recording (its note is kept). Needs a Super Admin (privileged, Enterprise plan) API key. Cannot be undone.
get_recordingGet recordingGETGets one meeting recording: title, times, call URL, note id, full transcript (speaker, text, timestamps), AI notes, and a temporary media_url. Holds what was said in the meeting.
list_recordingsList recordingsPOSTLists the meeting recordings you can see, 20 per page by default. Filter by title, event, dates or channel; add transcript and AI notes with include; next page: pagination.cursor = page_info.cursor.
upload_recordingUpload recordingPOSTImports a meeting recording into Fellow from a media URL you host (title required). Returns recording_id at once; the import runs later: check it with get_upload (status PENDING, SUCCESS or FAILED).

Note, 3 operations

delete_noteDelete noteDELETEPermanently deletes a note and all its recordings. Needs a Super Admin (privileged, Enterprise plan) API key. Cannot be undone.
get_noteGet noteGETGets one meeting note: title, calendar event (guid, start, end, attendees, organizer), recording ids, and its content in Markdown and Fellow Markdown. Holds attendee emails and meeting content.
list_notesList notesPOSTLists the meeting notes you can see (a privileged key sees the account), 20 per page by default. Filter by title, event, dates, channel or attendees; add content with include; next page: pagination.cursor = page_info.cursor.

Upload, 2 operations

get_uploadGet uploadGETGets the import status of one recording uploaded with upload_recording: PENDING, SUCCESS or FAILED, with failure_reason when it failed.
list_uploadsList uploadsPOSTLists the recordings imported with upload_recording and their import status (PENDING, SUCCESS, FAILED, with failure_reason), 20 per page by default; next page: pagination.cursor = page_info.cursor.

User, 1 operation

get_meGet meGETGets the user who owns the API key (id, email, full name) and their workspace (id, name, subdomain). Use it to check the key and the subdomain.

Use Fellow from Claude Code, Cursor or Codex

Connect Fellow in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Fellow operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Fellow

Create your workspace
Sign up free. Nothing to install.
Connect Fellow once
Add your Fellow connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.