Grofomo API
Browse the docs

MCP server

Add the public event directory to Claude, ChatGPT or Cursor as a tool.

Examples use a fictional festival, summer-fest. Sign in at events.grofomo.com and they switch to your own events.

Grofomo runs a public MCP server for the event directory, so an AI assistant can answer "what's on in Leeds this weekend" from the source and cite the event page it read. It is read-only and needs no key.

The server

URLhttps://api.grofomo.com/mcp/events
TransportStreamable HTTP, POST only, stateless
Protocol2026-07-28, plus the 2025-03-26 to 2025-11-25 handshake revisions
AuthNone
Rate limit60 requests a minute per IP

Tools

  • search_events: upcoming club nights, gigs and festivals, filtered by city, genre, a from/to date range and free-text query, in any combination. Soonest first, up to 25 at a time. Each result carries the event page url, which is the thing to cite.
  • get_event: one event by slug: name, description, dates and timezone, venue and address, genres, where tickets are sold, and whether a lineup is published.
  • get_lineup: the published timetable of an event ticketed on Grofomo: every set with its artists, stage, day, start and end. An empty list means nothing is published yet, not that there are no acts.

Results come back twice over: as text an assistant can quote as it stands, and as structuredContent a program can read. Times are ISO 8601 instants with the event's timezone alongside.

The directory covers what promoters and venues have listed. An event that is not here has not been listed, so the right answer is "not listed on Grofomo", never "not happening".

Adding it to an assistant

Claude (claude.ai or Claude Code): add a custom connector or MCP server with the URL above and no authentication.

ChatGPT: in a project's or a custom GPT's connectors, add a remote MCP server with the URL above, no authentication.

Cursor, Windsurf and other MCP clients: add a remote server entry:

{
  "mcpServers": {
    "grofomo-events": { "url": "https://api.grofomo.com/mcp/events" }
  }
}

Calling it by hand

curl -sS https://api.grofomo.com/mcp/events \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/call' \
  -H 'Mcp-Name: search_events' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_events","arguments":{"city":"Leeds","genre":"techno"}}}'

The 2026-07-28 revision mirrors the method and tool name into the Mcp-Method and Mcp-Name headers and requires that they agree with the body; a client on an older revision sends an initialize request first and no mirrored headers.

Discovery

A machine-readable server card, built from the live tool list, is served at https://api.grofomo.com/.well-known/mcp/server-card.json (and at /.well-known/mcp.json): the endpoint, its tools, the protocol versions it speaks and the fact that it needs no auth, in one fetch. The server is also listed in the MCP Registry as com.grofomo/events.

For partners who list events

A second, credentialed MCP server at /mcp lets a named partner propose events for the directory's review queue. It is not public; contact Grofomo if you run a listings source and want one.