2,500+ MCP servers ready to use
Vinkius

Whereby MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 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 Whereby 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": {
    "whereby": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Whereby
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 Whereby MCP Server

Connect your Whereby account to any AI agent and manage your video communication infrastructure through natural conversation.

GitHub Copilot Agent mode brings Whereby data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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 Creation — Instantly provision new transient video meeting rooms with specific expiration dates and room modes (normal or group)
  • Meeting Insights — Retrieve full details for any meeting, including the exact join URL and real-time status
  • UI Customization — Update and manage visual room themes, including custom colors and branding, to match your application's look and feel
  • Recording Management — List all cloud recordings stored in your account and retrieve direct MP4 download links and metadata
  • Active Sessions — Monitor currently active or pending meeting rooms and retrieve their unique UUIDs for automated workflows
  • Data Integrity — Safely delete obsolete meeting rooms or cloud recordings to manage your quotas and storage efficiently
  • Room Controls — Configure room security by setting rooms to 'locked' mode, requiring host approval for new participants

The Whereby MCP Server exposes 10 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 Whereby to VS Code Copilot via MCP

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

Ask Copilot: "Using Whereby, help me...". 10 tools available

Why Use VS Code Copilot with the Whereby MCP Server

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

Whereby + VS Code Copilot Use Cases

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

Whereby MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Whereby to VS Code Copilot via MCP:

01

create_meeting_room

Provide an ISO 8601 end date and room mode (normal or group). Creates a new transient video meeting room with a specific end date

02

delete_cloud_recording

This action is irreversible. Permanently deletes a cloud recording file

03

delete_meeting_room

This action is irreversible. Immediately deletes a video meeting room and terminates any active session

04

get_meeting_details

Retrieves details for a specific video meeting, including its join URL and expiration date

05

get_recording_details

Retrieves download links and metadata for a specific cloud recording

06

get_room_theme

Retrieves the visual theme settings (colors, logo) for a specific room name

07

list_active_meetings

Lists all currently active or pending video meeting rooms created via the API

08

list_cloud_recordings

Lists all cloud recordings stored in the Whereby account

09

reset_room_theme

Resets a meeting room theme back to the default Whereby branding

10

update_room_theme

Provide the room name and a hex color code. Updates the primary branding color for a specific meeting room

Example Prompts for Whereby in VS Code Copilot

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

01

"Create a new 'group' meeting room that expires in 2 hours."

02

"List all my past cloud recordings."

03

"Update the 'Support-101' room theme to use hex color #00ff00."

Troubleshooting Whereby MCP Server with VS Code Copilot

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

Whereby + VS Code Copilot FAQ

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

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