The ClusterHack MCP server,
connected in one click.

“Use “event_roles”: Which roles the signed-in user holds at one specific event. Cheaper and more precise than `whoami` when you already know the event and just.”

“Use “list_api_endpoints”: List the raw REST endpoints behind this server. Use it together with `api_request` when you need something no curated tool covers. The list.”

“Use “list_capabilities”: The catalogue of everything this server can do, grouped by area. Returns each tool available to the current connection with its one-line pu.”

“Use “search”: Search across the platform: events, teams, projects, people and articles. One call when you do not yet know the identifier of the thing the.”

event_roles — Which roles the signed-in user holds at one specific event. Cheaper and more precise than `whoami` when you already know the event and just

list_api_endpoints — List the raw REST endpoints behind this server. Use it together with `api_request` when you need something no curated tool covers. The list

list_capabilities — The catalogue of everything this server can do, grouped by area. Returns each tool available to the current connection with its one-line pu

search — Search across the platform: events, teams, projects, people and articles. One call when you do not yet know the identifier of the thing the

server_info — What this MCP server is, which version it speaks, and how to connect. Useful for diagnostics and for telling the user where to manage or re

whoami — Who is signed in, what roles they hold, and where. Call this first in any new conversation. It returns the account, the OAuth permissions t

event_background_images — The global catalogue of certificate background templates (used for the `background` field of an event's certificate config). Not tied to one

event_cities — The global catalogue of cities (used for the `city` field on `event_create`/`event_update` and to show where events happen).