Bring Appointment Booking
to VS Code Copilot
Learn how to connect Calenso to VS Code Copilot and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Calenso MCP Server?
Connect your AI agent to Calenso to natively manage appointment scheduling, track customer bookings, and query staff availability via natural language.
What you can do
- Appointment Management — List upcoming appointments, fetch specific details, or cancel bookings effortlessly.
- Customer Directory — Query existing customers or automatically add new customer profiles directly from a chat conversation.
- Service & Staff Availability — List available bookable services, branches, and staff members dynamically.
How it works
1. Retrieve your API Key from the Calenso portal.
2. Provide the key to this integration.
3. Ask your AI agent to list all appointments for today or add a new customer.
Who is this for?
- Consultants & Clinics — Manage your schedule and client list natively within your AI workflow.
- Service Businesses — Rapidly check branch availability or cancel an appointment via prompt.
- Developers — Hook native booking endpoints directly into external workflows.
Built-in capabilities (8)
Cancel an appointment
Create a new customer
Get appointment details
List all appointments
List branches/locations
List all customers
List available services
List staff members
Why VS Code Copilot?
GitHub Copilot Agent mode brings Calenso data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 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
Calenso in VS Code Copilot
Calenso and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Calenso 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 Calenso in VS Code Copilot
The Calenso 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 8 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
Calenso for VS Code Copilot
Every tool call from VS Code Copilot to the Calenso MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I cancel a booking directly from the chat?
Yes. Provide the Appointment ID to the 'cancel_calenso_appointment' tool, and the AI agent will remove it from your schedule.
How do I add a new customer profile?
Invoke the 'create_calenso_customer' tool with a JSON object containing the customer's details (like name and email).
Is it possible to query available staff members?
Yes, just use the 'list_calenso_staff' tool to pull the active roster of your bookable employees.
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.