Cal.com MCP Server for VS Code CopilotGive VS Code Copilot instant access to 12 tools to Cancel Booking, Create New Booking, Get Available Slots, and more
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.
Ask AI about this App Connector for VS Code Copilot
The Cal.com app connector for VS Code Copilot is a standout in the Loved By Devs category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Cal.com and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"calcom-alternative": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 Cal.com MCP Server
Connect your Cal.com account to any AI agent and take full control of your professional scheduling infrastructure and meeting lifecycle through natural conversation.
GitHub Copilot Agent mode brings Cal.com 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 and manage your meeting lifecycle programmatically, including creating new bookings and cancelling or rescheduling existing ones in real-time
- Availability Intelligence — Programmatically find free time slots for specific event types and date ranges to coordinate perfectly timed meetings
- Template Management — Access and monitor your complete directory of event types (templates) to ensure your high-fidelity scheduling options are always current
- Rule & Schedule Monitoring — Access your directory of availability schedules and working hours to oversee your time management programmatically
- Operational Visibility — Access high-fidelity metadata for your user profile and active webhooks directly through your agent for instant reporting
The Cal.com 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.
All 12 Cal.com tools available for VS Code Copilot
When VS Code Copilot connects to Cal.com through Vinkius, your AI agent gets direct access to every tool listed below — spanning meeting-automation, booking-infrastructure, availability-management, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Remove meeting
Schedule a meeting
Find free times
Get meeting info
Get template info
Get user settings
Get event configs
List working hours
List scheduled meetings
List booking templates
Update booking time
Check connection
Connect Cal.com to VS Code Copilot via MCP
Follow these steps to wire Cal.com into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Cal.com
Why Use VS Code Copilot with the Cal.com MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Cal.com through the Model Context Protocol.
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
Cal.com + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Cal.com MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for Cal.com in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Cal.com immediately.
"List all my upcoming bookings for the next 7 days."
"Find available slots for a 'Discovery Call' tomorrow between 9 AM and 12 PM."
"Cancel my booking ID '12345' because of a conflict."
Troubleshooting Cal.com MCP Server with VS Code Copilot
Common issues when connecting Cal.com to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Cal.com + VS Code Copilot FAQ
Common questions about integrating Cal.com MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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.