"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.
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.
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.
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.