2,500+ MCP servers ready to use
Vinkius

Fathom 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 Fathom 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": {
    "fathom": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Fathom
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 Fathom MCP Server

Connect your Fathom.video account to any AI agent and take full control of your meeting intelligence and automated note-taking through natural conversation.

GitHub Copilot Agent mode brings Fathom 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 Orchestration — List recent meetings and search across your entire recording history to retrieve titles, dates, and participant metadata natively
  • AI Transcription — Retrieve full speaker-attributed transcripts with timestamps to review exact discussions and verbal commitments limitlessly
  • Contextual Summarization — Get AI-generated summaries distilling key discussion points, decisions, and overall meeting context into a concise format
  • Action Item Tracking — Extract AI-identified tasks with assigned owners and due dates to automate post-meeting follow-up workflows
  • Recording Management — Access video and audio recording URLs for immediate streaming or download bypassing the web interface
  • Attendee Auditing — List all meeting participants including join/leave times and speaking duration to verify engagement levels synchronously
  • Team Intelligence — Access meetings shared with your Fathom team to monitor cross-functional discussions and organizational knowledge securely
  • Highlight Navigation — Retrieve specific moments flagged as important during calls to focus on critical insights without reviewing entire recordings

The Fathom 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 Fathom to VS Code Copilot via MCP

Follow these steps to integrate the Fathom 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 Fathom

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

Why Use VS Code Copilot with the Fathom MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Fathom 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

Fathom + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Fathom 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

Fathom MCP Tools for VS Code Copilot (12)

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

01

get_action_items

Get AI-identified action items for a meeting

02

get_attendees

Get the list of participants for a meeting

03

get_highlights

Get important moments flagged in a meeting

04

get_me

Get current API token user profile

05

get_meeting

Get details for a specific Fathom meeting

06

get_recording

Get the recording URLs for a meeting

07

get_summary

Get the AI-generated summary for a meeting

08

get_team_meetings

List meetings shared with your team

09

get_transcript

Get the full transcript for a meeting

10

get_webhooks

List configured webhooks

11

list_meetings

List all Fathom meetings

12

search_meetings

Search for meetings by keyword

Example Prompts for Fathom in VS Code Copilot

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

01

"Show me the summary and action items for my last meeting"

02

"Search my meetings for mentions of 'pricing strategy'"

03

"Get the transcript for meeting 'abc-123'"

Troubleshooting Fathom MCP Server with VS Code Copilot

Common issues when connecting Fathom 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.

Fathom + VS Code Copilot FAQ

Common questions about integrating Fathom 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 Fathom to VS Code Copilot

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