Signal · Connect

Ask your AI assistant
about your event.

"How many have checked in to Summit so far?" "Find Priya Sharma's seat." "Which sessions are on after lunch?" SignupDesk runs a remote MCP server, the open standard assistants use to call tools. Connect Claude Code, Cursor or any MCP client with one API token and your event data answers in plain language. Read-only by default. Writes only on a token you mark for it.

Claude Code · signupdesk MCP
event_stats
Summit 2026 · read tool
How is check-in going at Summit right now?
1,284 registered, 912 checked in (71%). VIP 118 of 140. Hall A gate has 640 scans, Hall B 272. Seats left: 16 VIP, 216 general.
Check in Priya Sharma, she's at the desk
Found Priya Sharma, seat V-14, not yet checked in. Confirm check-in? → Checked in at 10:42.

Six read tools. Three write tools. Nothing else.

📅
list_events · list_sessions
Your events with dates, venues, status and registration counts. Sessions with times, rooms, tracks, RSVPs and check-ins.
📊
event_stats
Registrations, check-ins, category split, seats left, and check-ins per zone gate. The live-ops question answered in one call.
🔍
find_attendee · get_registration
By email, mobile or name across events, or one registration by pass token. Seat, category, check-in time.
🏆
leaderboard
Top attendees by gamification points, for the stage announcement without opening the admin panel.
✍️
create_registration · check_in · tag_vip
The three writes. Seat allocated and pass emailed on create; double check-in reported, not repeated. Each tool's description tells the assistant to confirm with you first.
🔐
mcp:write ability
Write tools exist only on tokens created with this ability. A plain token's tool list has six entries, so a read-only assistant cannot even be talked into a write.

One token, one line of config.

Create a key under Admin → Workspace → API Keys. Leave abilities empty for read-only, or add mcp:write. Then, in Claude Code:

claude mcp add --transport http signupdesk https://your-domain.in/api/v1/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Cursor and Windsurf take the same URL and header in their MCP settings. The endpoint speaks JSON-RPC 2.0 over Streamable HTTP, request and response only, rate limited to 120 calls a minute per token. Every call updates the token's last-used time so you can see it is in use.

We are straightforward about one gap: the ChatGPT and Claude.ai web apps connect to remote servers through OAuth, not a pasted token. That OAuth layer is not built. Developer tools and custom agents connect today; the chat apps follow when a customer needs them.

Build for the standard, not for one vendor's app store.

Some platforms ship "an app inside ChatGPT". It works in one product, under one vendor's review queue, until that vendor changes the rules. The Model Context Protocol is the open way assistants call tools, and Anthropic, OpenAI, Cursor and the editors all speak it. One server, every client.

It is also the honest size of the feature. The MCP server is a thin layer over the same API and services the admin panel uses: no second copy of your data, no extra process, nothing that costs money per question. If a tool is missing, tell us; adding one is a day, not a quarter.

The other ways in.

🔗
Push events out to other tools. MCP is the pull side: an assistant asking questions.
🤖
The built-in copilot inside the admin panel, for teams who do not run their own assistant.
🔑
API Keys
Scoped, expiring tokens with last-used tracking. Revoke one and the assistant stops that instant.

Questions organisers and developers ask us

Which assistants can connect?
Any MCP client that can send an Authorization header with a bearer token: Claude Code, Cursor, Windsurf, Zed, and custom agents built on the MCP SDKs. Clients that only accept OAuth connectors, such as the ChatGPT and Claude.ai web apps today, need an OAuth flow we have not built yet; it is on the list once a customer asks.
Can the assistant change my data?
Only with a token you created with the mcp:write ability. A plain token sees six read tools and nothing else; write tools do not even appear in its tool list. The write tools are create registration, check in and tag VIP, and their descriptions tell the assistant to confirm with you first.
Is this an extra service I pay for?
No. The MCP endpoint is part of SignupDesk and runs on the same server as your admin panel. The AI assistant you use is yours and billed by its vendor; we charge nothing per call.
Where does my data go?
Only to the assistant you connected, in answer to its requests. We do not send your attendee data to any AI provider ourselves. Treat the token like a password and revoke it under API Keys when you stop using the assistant.
Does it stream?
Not yet. The server answers each JSON-RPC request with one JSON response, which every MCP client accepts. Server-sent event streaming is only needed for long-running tools, and none of ours take more than a second.
Your event, one question away.
Create a token, add the server to Claude Code, ask about your next event. Five minutes.