Agents Index

ClusterHack

Online

Run hackathons end to end: events, teams, submissions, judging and winners.

Visit publisherConnectJSON

What it can do: 60 tools

  • event_roles read-onlyWhich roles the signed-in user holds at one specific event. Cheaper and more precise than `whoami` when you already know the event and just need to know whether the user can organise, judge or only take part.
  • list_api_endpoints read-onlyList the raw REST endpoints behind this server. Use it together with `api_request` when you need something no curated tool covers. The list is read from the live URL configuration, so it always matches what the server a
  • list_capabilities read-onlyThe catalogue of everything this server can do, grouped by area. Returns each tool available to the current connection with its one-line purpose, the role it is meant for and the permission it consumes. Use it when you
  • search read-onlySearch across the platform: events, teams, projects, people and articles. One call when you do not yet know the identifier of the thing the user means ("the AI hackathon in Berlin", "Sasha's team"). Returns the matching
  • server_info read-onlyWhat this MCP server is, which version it speaks, and how to connect. Useful for diagnostics and for telling the user where to manage or revoke the connection.
  • whoami read-onlyWho is signed in, what roles they hold, and where. Call this first in any new conversation. It returns the account, the OAuth permissions this connection was granted, and — crucially — the list of events, teams and comp
  • event_background_images read-onlyThe global catalogue of certificate background templates (used for the `background` field of an event's certificate config). Not tied to one event.
  • event_cities read-onlyThe global catalogue of cities (used for the `city` field on `event_create`/`event_update` and to show where events happen).
  • event_faq read-onlyAn event's FAQ: the question/answer pairs shown on its public page. Public read — use it to answer a participant's question from the event's own words before guessing, and to check what is already covered before adding m
  • event_get read-onlyGet one event's full public profile by slug: name, dates, address, topic, description, status and city. Call this once you have a slug (from `event_list` or `search`) and need the details. It does not include the schedu
  • event_info_blocks read-onlyAn event's additional free-form information blocks (extra sections shown on its public page beyond the main description — rules, prizes, sponsors notes, etc.).
  • event_list read-onlyBrowse hackathons on the platform — filter by status, city or date. Returns each event's slug, which every other event tool needs, plus name, status, dates and city. Use this when the user names an event you do not have
  • event_nominations read-onlyAn event's award nominations/tracks (e.g. "Best AI prototype"), used when creating teams, awarding winners and building the leaderboard per track.
  • event_presets read-onlyPublic catalogue of event-creation presets (AI build day, student hackathon, corporate innovation day, ...) with sensible defaults and starter nominations. Call before `event_create` when the user describes a kind of hac
  • event_schedule read-onlyThe event's timeline: an ordered list of stages/activities (opening, workshops, deadlines, closing ceremony) with title, location, time window and status (past/now/future). This is what participants see as "the schedule"
  • event_share_links read-onlyThe public links for promoting an event: its shareable page, the calendar file participants can add to their own calendar, the Open Graph preview image used when the link is pasted into chat, and a plain-text digest mean
  • event_team_stages read-onlyAn event's team-facing reporting checkpoints (e.g. "Idea locked", "Demo ready") with their time windows — distinct from `event_schedule`, which is the event's own agenda. Used to track team progress through the event.
  • event_types read-onlyThe global catalogue of event types (used for the `type` field on `event_create`/`event_update`). Small and rarely changes.
  • event_branding read-onlyRead an event's white-label branding: brand colours, public-page theme and dedicated subdomain, plus the resolved values actually used for rendering and `branding_enabled` — whether the evening currently wears its costum
  • event_free_agents read-onlyList participants at an event who are looking for a team. Visibility follows the platform's own rule, not a full public roster: a normal caller only sees their own free-agent listing here, while an organiser of the even
  • event_my_membership read-onlySummarise the signed-in user's relationship to one event: whether they have joined, their registration answers on file, whether they are listed as a free agent, and which roles they hold there (organizer, judge, team lea
  • event_my_registration_answers read-onlyList the signed-in user's own answers to one event's registration questions. Only ever returns their own data — use `event_registration_responses` (organiser only) to read other people's.
  • event_registration_form read-onlyList the custom questions an event asks at registration time (its registration form), in display order. Public data — the question text is visible to anyone. Use this before `event_submit_registration_answers` to know w
  • invite_preview read-onlyLook up what a shareable invite link opens, without redeeming it. Public and PII-free: returns the event's name and slug and whether the token is still valid (active, not expired, uses remaining). Use this before `invit
  • team_get read-onlyGet one team's full detail: name, description, project info, readiness, accessibility flags, and which event and nomination it belongs to. Only visible if the signed-in user belongs to the team, created it, or administe
  • team_list read-onlyList teams — scoped to what the signed-in account can see: teams they belong to, created, or administer via being an admin of the team's event. This is never a full public directory of every team on the platform. Filter
  • team_locations read-onlyRead the physical location details linked to a team's additional-info profile (street, city, state, zip), if one has been set. There is currently no self-service way to create a new location through this API — location r
  • team_matchmaking_teams read-onlyAI-ranked list of teams one free (teamless) participant could join, within the same event. Callable by the free-agent listing's own owner, or an admin of the event. Use `event_free_agents` or `event_join_as_free_agent` t
  • team_members read-onlyList a team's current members with their role and caption. Use the row `id` (a membership id, not a user id) with `team_assign_role` or `team_remove_member`.
  • team_open_roles read-onlyList the positions teams are looking to fill ("we need a designer"). Visibility is limited to what the signed-in account can already see: their own team's open roles, or — if they organise the event — every team's. It i
  • team_posts read-onlyList a team's public updates ("twits") — the short build-log posts a team publishes as it works, in the order the server returns them. Use it to catch up on what a team has been doing, or to check what has already been p
  • team_readiness read-onlyCheck whether a team has marked itself ready to present, plus whether it is banned or currently accessible for judging.
  • team_roles read-onlyList the roles a team has defined (e.g. "Frontend", "Designer"), which members can be assigned via `team_assign_role`.
  • team_seeking_members read-onlyBrowse the teams of one event that are advertising open positions — the public "who is recruiting" list behind the find-a-team page, readable by anyone, including someone who has not joined the event yet. This is the to
  • submission_get read-onlyRetrieve one project submission by id: title, links, description, status, approval status, vote count and attached media. Anonymous and unrelated callers only see it once the team has submitted (status "submitted"); dra
  • submission_list read-onlyBrowse project submissions, filterable by event, team or status. Anonymous and unrelated callers only ever see submitted (public) projects; a signed-in caller additionally sees their own team's drafts and every submissi
  • submission_list_media read-onlyList the screenshots/gallery images attached to a submission. Visibility mirrors the parent submission: public once submitted, otherwise limited to the team, event admins and judges.
  • submission_page read-onlyRead a project's public page: the submission itself, every judge's written feedback (signed with the judge's name only where that judge consented to being named, empty otherwise), and — once the organiser has published t
  • event_leaderboard read-onlyThe ranked leaderboard for one event: submissions ordered by weighted judge score then vote count, with each entry's rank, team and score. Public once the organiser publishes winners; before that, only the event's admins
  • showcase_browse read-onlyBrowse the public, cross-event showcase: shipped/submitted projects ranked for display, with title, tagline, team name, vote count and a cover image. Optionally narrow to one event. This is the public gallery — use `even

…and 20 more.

Connect it

Claude Code
claude mcp add --transport http clusterhack https://clusterhack.dev/mcp/
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://clusterhack.dev/mcp/
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "clusterhack": {
      "url": "https://clusterhack.dev/mcp/"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "clusterhack": {
      "type": "http",
      "url": "https://clusterhack.dev/mcp/"
    }
  }
}

Questions

What does ClusterHack do?

Run hackathons end to end: events, teams, submissions, judging and winners. It exposes 60 tools to AI assistants.

What tools does ClusterHack provide?

60 tools, including event_roles, list_api_endpoints, list_capabilities, search, server_info, whoami, event_background_images, event_cities, event_faq, event_get, event_info_blocks, event_list….

How do I connect ClusterHack to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://clusterhack.dev/mcp/ as a custom connector or MCP server. Copy-paste setup is on this page.

Does ClusterHack require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is ClusterHack online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes ClusterHack?

clusterhack.dev. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Communication