Luma MCP Server for VS Code CopilotGive VS Code Copilot instant access to 6 tools to Add Guests To Event, Create Event, List Calendar Subscribers, 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 Luma app connector for VS Code Copilot is a standout in the Industry Titans category — giving your AI agent 6 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 Luma and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"luma": {
"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 Luma MCP Server
Connect your Luma (lu.ma) account to any AI agent and take full control of your event orchestration and community engagement through natural conversation. Luma provides a robust platform for managing calendars and events, and this integration allows you to retrieve event metadata, manage guest lists, and create new activities directly from your chat interface.
GitHub Copilot Agent mode brings Luma 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.
What you can do
- Event & Calendar Orchestration — List all managed events and retrieve detailed metadata programmatically to ensure your community roadmap is always synchronized.
- Guest Lifecycle Management — Access and monitor guest lists and add new attendees directly from the AI interface to maintain high-fidelity event engagement.
- Communication & Update Control — List hosts and organizers linked to a calendar via natural language to drive better team alignment.
- Organization Oversight — Access organizational events and monitor system webhooks using simple AI commands.
- Operational Monitoring — Track system responses and manage event metadata to ensure your community workflows are always optimized.
The Luma MCP Server exposes 6 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 6 Luma tools available for VS Code Copilot
When VS Code Copilot connects to Luma through Vinkius, your AI agent gets direct access to every tool listed below — spanning event-registration, community-engagement, attendee-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.
Manually add guests to an event
Create a new Luma event
List subscribers to your calendar
List guests for an event
List your Luma events
List all events in your organization
Connect Luma to VS Code Copilot via MCP
Follow these steps to wire Luma 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 Luma
Why Use VS Code Copilot with the Luma MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Luma 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
Luma + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Luma 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 Luma in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Luma immediately.
"List all my upcoming events in Luma."
"Show me the guest list for the 'Product Launch' event."
"Add 'sarah@example.com' to the workshop guest list."
Troubleshooting Luma MCP Server with VS Code Copilot
Common issues when connecting Luma to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Luma + VS Code Copilot FAQ
Common questions about integrating Luma 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.