2,500+ MCP servers ready to use
Vinkius

Fellow MCP Server for VS Code Copilot 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Fellow and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "fellow": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Fellow
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Fellow MCP Server

Connect your Fellow.app account to any AI agent and take full control of your meeting management, collaborative agendas, and action item tracking through natural conversation.

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.

What you can do

  • Meeting Note Orchestration — List all meeting notes and retrieve full structured content including agenda items, discussion points, and decision metadata natively
  • Action Item Auditing — List and filter all tasks across meetings to track descriptions, assignees, and due dates for cross-meeting accountability flawlessly
  • Recording Management — Browse meeting recordings and retrieve video/audio details including time-limited download or stream URLs securely
  • AI Transcription Retrieval — Fetch full transcripts with speaker attribution and timestamps to review critical discussions or extract specific insights limitlessly
  • Task Lifecycle Control — Mark action items as complete or archive them to manage your active workspace and notify relevant stakeholders synchronously
  • Identity Oversight — Retrieve the authenticated profile identity including name, email, and workspace contexts to verify permission limits natively
  • Data Invalidation — Irreversibly vaporize specific meeting notes or recordings findable by ID to manage your organizational records strictly

The Fellow MCP Server exposes 12 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fellow to VS Code Copilot via MCP

Follow these steps to integrate the Fellow MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Fellow

Ask Copilot: "Using Fellow, help me...". 12 tools available

Why Use VS Code Copilot with the Fellow MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Fellow through the Model Context Protocol.

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Fellow + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Fellow MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Fellow MCP Tools for VS Code Copilot (12)

These 12 tools become available when you connect Fellow to VS Code Copilot via MCP:

01

archive_action_item

Archive an action item, removing it from active views without deleting it

02

complete_action_item

Use when a task has been finished. Mark an action item as complete

03

delete_note

Confirm with the user before executing — this cannot be undone. Permanently delete a meeting note by ID

04

delete_recording

Confirm with the user before executing. Permanently delete a meeting recording by ID

05

get_action_item

Use to inspect a single task. Retrieve details of a specific action item by ID

06

get_current_user

Use to verify which account is connected. Retrieve the authenticated Fellow user profile

07

get_note

Essential for reviewing a specific meeting. Retrieve the full content and metadata of a specific meeting note by ID

08

get_recording

Use to access a specific recording. Retrieve details of a specific meeting recording

09

get_transcript

Use for detailed review, compliance documentation, or extracting specific discussion points. Retrieve the full transcript of a meeting recording

10

list_action_items

Use for cross-meeting task tracking and accountability. List all action items across all meetings

11

list_notes

Use as the primary entry point to browse all meeting documentation. List all meeting notes in the Fellow workspace

12

list_recordings

Use to browse all recorded meetings. List all meeting recordings captured by Fellow

Example Prompts for Fellow in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Fellow immediately.

01

"Show me all my pending action items"

02

"Get the notes for the meeting 'Product Sync' from last Tuesday"

03

"List the last 3 meeting recordings"

Troubleshooting Fellow MCP Server with VS Code Copilot

Common issues when connecting Fellow to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Fellow + VS Code Copilot FAQ

Common questions about integrating Fellow MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Connect Fellow to VS Code Copilot

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.