Bring Remote Meetings
to VS Code Copilot
Learn how to connect GoTo Meeting to VS Code Copilot and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the GoTo Meeting MCP Server?
Connect your GoTo Meeting account to any AI agent and manage your video conferencing workflow through natural conversation.
What you can do
- Meeting Scheduling — Create new meetings with subject, start time, end time, and meeting type (immediate, scheduled, or recurring)
- Upcoming Meetings — List all scheduled meetings with connection links and attendee details
- Meeting Details — Inspect individual meeting configurations, connection URLs, and settings
- Meeting History — Browse past meetings with duration, start times, and attendance records
- Meeting Cancellation — Delete scheduled meetings that are no longer needed
- Organizer Management — List all meeting organizers configured in your organization
How it works
1. Subscribe to this server
2. Enter your GoTo Meeting OAuth Access Token
3. Start managing your meetings from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Executive Assistants — schedule, review, and manage meetings without switching to the GoTo Meeting dashboard
- Team Leads — check upcoming meetings, cancel sessions, and manage organizer accounts
- Operations Teams — audit meeting history, track usage patterns, and manage scheduling through AI
Built-in capabilities (6)
Schedule a new meeting
Delete a meeting
Get details for a specific meeting
List account organizers
List historical meetings
List upcoming GoTo Meeting sessions
Why VS Code Copilot?
GitHub Copilot Agent mode brings GoTo Meeting data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 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
GoTo Meeting in VS Code Copilot
GoTo Meeting and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect GoTo Meeting 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 GoTo Meeting in VS Code Copilot
The GoTo Meeting 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 6 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
GoTo Meeting for VS Code Copilot
Every tool call from VS Code Copilot to the GoTo Meeting MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I schedule a meeting directly through the AI agent?
Yes! The create_meeting action accepts a subject, start time (ISO 8601), end time (ISO 8601), and an optional meeting type ('immediate', 'scheduled', or 'recurring'). It returns the meeting ID, connection URL, and dial-in details. Use list_meetings to verify the meeting appears in your upcoming schedule.
Can I view the history of past meetings including attendance?
Yes. The list_meeting_history tool retrieves all past meetings with start times, durations, and attendance records. Use get_meeting_details with a specific Meeting ID for the complete configuration and connection details of any meeting.
How does GoTo Meeting authentication work?
GoTo Meeting uses OAuth 2.0 with an Access Token sent as a Bearer token. You can generate a Personal Access Token from the GoTo Developer Portal or configure a full OAuth client for production use. The token authenticates against the api.getgo.com/G2M/v3 endpoint.
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.