MCP connection

Run your events
from Claude

Connect your account, describe the event, and it drafts, prices and publishes on your say-so.

Connect it — takes a minuteYour key never leaves your browser

Claude · exampleconnected

Add a robotics workshop on 12 Sep — 60 seats, ₹250.

create_event

Intro to Robotics

Draft

Date: 12 Sep
Price: ₹250
Seats: 60

Publish it.

publish_event

Describe it, get a draft

Dates, price, seats, venue. Nothing public until you say so.

Whole festivals

Every session with its own date, price and seats.

Ask how it is going

Tickets sold, money taken, who checked in.

Connect it

3 steps

You hand over the key. Everything else is in the guide Claude reads.

Create an API key

In Developer settings. It is shown once — copy it before closing the dialog.

Open settings

Paste it here

It is slotted into the block below. Your key stays in this browser — it is never sent to us.

Hand it to Claude

Paste this into any Claude conversation. It reads our guide and connects itself.

message to claude

Connect me to my Vihaya Events account. Read https://events.vihaya.app/connect.md and follow the setup steps there to add the Vihaya MCP server, then show me my events.

My Vihaya API key is: vihaya_live_sk_YOUR_KEY

Paste your key above and it replaces vihaya_live_sk_YOUR_KEY here.

Then just ask

“Create a workshop called Intro to Robotics on 12 September, 60 seats, ₹250 a ticket.”
“Add the venue and a proper description to my draft, then read it back to me.”
“Set up my fest with four sessions — Excel Arena, Mix Design, Plan Swift and a CTF.”
“Make the CTF 40 seats at ₹200.”
“How many tickets has my fest sold, and how much have I taken?”

What it can and cannot do

New events start as drafts: Nothing reaches the public until you say publish, so it is safe to let it build one and look afterwards.
It only ever sees your account: Every action runs as you. It cannot read or change another organiser’s events, or their attendees.
Publishing still needs organiser access: Exactly as it does on the dashboard. Without it the event simply stays a draft.
Your attendees’ details stay yours to share: Asking for your registration list puts attendees’ names and emails into the chat, and your assistant’s provider stores that conversation. Ask for numbers instead — “how many sold”, “how much have I taken” — and it reads the analytics.
You can revoke it any time: Delete the key in Developer settings and the connection stops working immediately.

Connect me to my Vihaya Events account. Read https://events.vihaya.app/connect.md and follow the setup steps there to add the Vihaya MCP server, then show me my events. My Vihaya API key is: vihaya_live_sk_YOUR_KEY

Then just ask

“Create a workshop called Intro to Robotics on 12 September, 60 seats, ₹250 a ticket.”

“Add the venue and a proper description to my draft, then read it back to me.”

“Set up my fest with four sessions — Excel Arena, Mix Design, Plan Swift and a CTF.”

“Make the CTF 40 seats at ₹200.”

“How many tickets has my fest sold, and how much have I taken?”

What it can and cannot do

New events start as drafts

Nothing reaches the public until you say publish, so it is safe to let it build one and look afterwards.

It only ever sees your account

Every action runs as you. It cannot read or change another organiser’s events, or their attendees.

Publishing still needs organiser access

Exactly as it does on the dashboard. Without it the event simply stays a draft.

Your attendees’ details stay yours to share

Asking for your registration list puts attendees’ names and emails into the chat, and your assistant’s provider stores that conversation. Ask for numbers instead — “how many sold”, “how much have I taken” — and it reads the analytics.

You can revoke it any time

Delete the key in Developer settings and the connection stops working immediately.