Bring Event Registration
to Cursor
Learn how to connect Luma to Cursor 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 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.
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.
How it works
1. Subscribe to this server
2. Enter your Luma API Key (requires Luma Plus) from your calendar settings
3. Start managing your events from Claude, Cursor, or any MCP-compatible client
No more manual logging into the dashboard for quick guest checks. Your AI acts as a dedicated event coordinator or community assistant.
Who is this for?
- Event Planners & Hosts — quickly retrieve guest summaries and monitor event health without switching apps.
- Community Managers — automate the retrieval of attendee metadata and track community growth via natural conversation.
- Growth Teams — streamline the ingestion of new guests and monitor organizational activity directly within the chat.
Built-in capabilities (6)
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
Why Cursor?
Cursor's Agent mode turns Luma into an in-editor superpower. Ask Cursor to generate code using live data from Luma and it fetches, processes, and writes. all in a single agentic loop. 6 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Luma in Cursor
Luma and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Luma to Cursor 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 Luma in Cursor
The Luma 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 Cursor 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
Luma for Cursor
Every tool call from Cursor to the Luma MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the details for a specific event by its ID?
Yes! While the list_events tool retrieves all entries, you can use the event metadata to filter and focus on specific records. Your agent will respond with complete metadata for the record in seconds.
How do I find my Luma API Key?
Log in to your Luma account, select your calendar, navigate to Settings > Developer, and you will find your unique secret token there. Note: You must have Luma Plus.
Can I add guests to an event via the AI?
Absolutely. Use the add_guests tool. Provide the event ID and an array of guest objects (email and name), and the agent will register them to your event immediately.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.