Bring Meeting Management
to Claude Code
Learn how to connect Fellow to Claude Code and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Fellow MCP Server?
Connect your Fellow workspace to any AI agent and manage your entire meeting workflow through natural conversation.
What you can do
- Meetings — List and inspect meetings with titles, participants, dates, and agendas.
- Notes — Access structured meeting notes and AI-generated summaries.
- Action Items — Create, track, and complete action items with assignees and due dates.
- Streams — Browse recurring meeting series and their schedules.
- Users — List all workspace members and their roles.
How it works
1. Subscribe to this server
2. Enter your Fellow API key (User Settings > Developer Tools)
3. Start managing meetings from Claude, Cursor, or any MCP client
Who is this for?
- Team Leads — review meeting notes and action items without opening Fellow.
- Project Managers — track follow-up tasks and ensure accountability.
- Remote Teams — stay aligned on meeting outcomes and decisions.
Built-in capabilities (12)
Verify Fellow API connectivity
Mark an action item as completed
Optionally link it to a meeting, assign to a user by email, and set a due date. Create a new action item from a meeting
Get details of a specific action item
Get full details of a specific meeting
Get full content of a specific note
Get details of a specific meeting stream
Optionally filter by status: "pending", "completed", or "archived". List action items from meetings
List recent meetings from Fellow
Optionally filter by a specific meeting ID to get notes for that meeting only. List meeting notes
List all meeting streams (recurring series)
List all users in the Fellow workspace
Why Claude Code?
Claude Code registers Fellow as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Fellow data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Fellow tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Fellow in Claude Code
Fellow and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Fellow to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Fellow in Claude Code
The Fellow MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Fellow for Claude Code
Every tool call from Claude Code to the Fellow MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create an action item and assign it to a team member?
Yes! Use create_action_item with the title, assignee email, and optional due date. You can also link it to a specific meeting.
How do I get the notes from a specific meeting?
Use list_notes with the meeting ID to get all notes linked to that meeting, or get_note with a specific note ID for full content.
Can I mark action items as completed via the AI agent?
Absolutely. Use complete_action_item with the action item ID to mark it as done.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable