How to Use the EventTemple MCP in Cursor

Q: Who can see the booking data pulled into my editor?

The getbooking payloads route directly from the API to your local Cursor instance. Vinkius runs the server in an isolated V8 sandbox that drops the connection immediately after the request finishes. No persistent storage exists.

Give Cursor Agent access to your EventTemple data to write venue integration code using real bookings and invoices.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect EventTemple MCP to Cursor

Create your Vinkius account to connect EventTemple to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup EventTemple with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build EventTemple integrations faster

The EventTemple MCP Server lets Cursor read your actual production or sandbox data while you write code. Instead of guessing the JSON structure of a banquet order, your agent runs `get_booking`. It sees the exact fields and types returned by the API. This eliminates the need for mock data. When you build a custom dashboard for your sales team, Cursor pulls live records using `list_bookings` and `list_events`. The AI writes parsing logic based on real responses.

Auto-generate CRM data models

Writing TypeScript interfaces for complex hospitality CRMs takes hours. Now, you just ask Cursor to run `list_accounts` and `list_contacts`. The AI reads the live schema and generates the exact types you need for your application. If a specific endpoint has weird nested objects, your agent figures it out immediately. It calls `get_contact`, inspects the payload, and writes the extraction functions. You skip the manual documentation hunt entirely.

Test invoice rendering with real numbers

Building financial features requires accurate test data. Your AI client calls `list_invoices` to pull real billing histories into your editor. Cursor uses that data to write PDF generation scripts or payment portal components. The same applies to internal workflows. By running `list_tasks`, the agent sees how your sales team tracks their daily calls. It writes the exact UI code needed to display those tasks in your custom internal tools.

Setup guide

Set up EventTemple MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the EventTemple MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent EventTemple transactions." If the MCP tools are loaded correctly, Cursor will call the EventTemple tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "eventtemple-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by EventTemple. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect EventTemple now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about EventTemple MCP in Cursor

Create a .cursor/mcp.json file in your project root. Paste the EventTemple MCP Server configuration there. Open your chat panel and enable Agent mode to start using the tools.

The current toolset is strictly read-only. Your agent can inspect the schedule with `list_events` or check availability via `list_bookings`. It cannot modify your calendar or delete records.

Yes. Composer can trigger the MCP tools to fetch live venue data while generating multi-file features. Just ask it to pull a sample from `get_event` before it writes your event parsing logic.

Usually, yes. Reloading the Cursor window ensures the agent picks up the new tools. You can verify the connection by asking the chat to list all available EventTemple commands.

The `get_booking` payloads route directly from the API to your local Cursor instance. Vinkius runs the server in an isolated V8 sandbox that drops the connection immediately after the request finishes. No persistent storage exists.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript