Bring Meeting Management
to VS Code Copilot
Learn how to connect Fellow to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Fellow data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Fellow in VS Code Copilot
Fellow and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Fellow to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.