Guides

AI assistants (MCP)

Connect Claude, ChatGPT, Cursor or any Model Context Protocol client and let it read and change your events with a scoped key.

EventOS is a Model Context Protocol (MCP) server at {{APP_URL}}/api/mcp. It uses the Streamable HTTP transport without sessions, so any MCP client that can send an Authorization header can connect. The assistant gets tools that mirror the public API: list and create events, set dates and venue, add ticket types and promo codes, publish, read orders and attendees, register guests, check people in and record invoice payments.

1. Create a key with the right scopes

Under Settings → API keys create a key. Reading needs events:read, orders:read and attendees:read. Add events:write for creating and editing events, ticket types and promo codes, attendees:write to issue complimentary tickets, checkin:write to check people in and orders:write to record invoice payments or cancel orders. Every tool names the scope it needs; a key without it gets a clear refusal instead of a surprise.

2. Add the server to your assistant

Claude Codebash

claude mcp add --transport http eventos https://eventos.rewardland.sg/api/mcp \
  --header "Authorization: Bearer eos_live_YOUR_KEY"

Claude Desktop, Cursor, Windsurf and other stdio clients (via mcp-remote)json

{
  "mcpServers": {
    "eventos": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://eventos.rewardland.sg/api/mcp", "--header", "Authorization: Bearer eos_live_YOUR_KEY"]
    }
  }
}

claude.ai and ChatGPT custom connectors: add {{APP_URL}}/api/mcp as a remote MCP server and paste the key where the connector asks for an API key or Authorization header.

3. Ask for what you want

“Create a two-day summit at Marina Bay Sands on 20 and 21 November with a S$350 delegate pass and a S$90 student pass, then publish it.”
“How many people have checked in to the trade show so far, and how many delegate passes are left?”
“Add a 15% early-bird code valid until the end of the month.”
“Register our two keynote speakers with complimentary passes.”
“Mark order EO-7KQ2ML as paid by PayNow.”

Under the hood

The same JSON-RPC your assistant sendsbash

curl -X POST https://eventos.rewardland.sg/api/mcp \
  -H "Authorization: Bearer eos_live_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_events","arguments":{"status":"published"}}}'

Tool calls run as the person who created the key, through the same row-level security and audit log as the EventOS interface. Nothing an assistant does is invisible: every change appears in the organisation's audit trail with the key's prefix.