# Clusterhack MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.clusterhack%2Fclusterhack
Registry id: `mcp-registry/dev.clusterhack/clusterhack`
Status: unreachable (checked 2026-10-25T08:58:01.585Z)

## Measurements (30 days)

- Uptime: 99.51%
- Checks: 4165
- Outages (90 days): 6

## Install

```json
{
  "mcpServers": {
    "clusterhack-mcp-server": {
      "type": "http",
      "url": "https://clusterhack.dev/mcp/"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http clusterhack-mcp-server https://clusterhack.dev/mcp/
```

## Tools (60)

- `account_ai_access`: How the signed-in user sees and revokes AI access to their own account — read this instead of looking for a tool that lists or cuts off connected clients, becau
- `account_how_to_sign_in`: Explains how to connect an account to this MCP server — read this instead of guessing at a login/registration tool, because there isn't one. ClusterHack's own c
- `article_get`: Retrieve one CMS article by id: its body, publish date, hidden flag, and which title/slug and language it belongs to.
- `article_languages`: List the languages articles can be written in, e.g. {"language_name": "English", "short_name": "en"}. Use this to find the `language_id` `article_create` needs.
- `article_list`: Browse CMS articles (the pages under /articles/<language>/<slug>). Filter by `language` (a language's short code, e.g. 'en') and/or `slug` (a title's slug) to f
- `article_titles`: List the CMS "title" records — each one a page's title text and slug, e.g. {"title": "How to organize a hackathon", "slug": "how-to-organize"}. An article alway
- `company_about_us`: A company's longer "about us" blurb (up to 10,000 characters), separate from its short `description`. Returns `found: false` if the company has not written one 
- `company_employees`: A company's employee roster (position, start date). Without `company_id`, returns every roster row the caller can see (their own employment rows plus every comp
- `company_employment_requests`: Pending requests to join a company. A company admin sees everyone waiting on their door; anyone else sees only their own outstanding applications. This is where
- `company_ex_employees`: A company's former employees (position, start and end date) — the record created when someone is fired via `company_fire_employee`. Without `company_id`, return
- `company_get`: One company page by id: name, description, organisation type, website and logo. Public read. Use it after `company_list` or `search` to get the full record, and
- `company_list`: Browse ClusterHack company pages: name, description, org type, website and logo. Public data — use this to find a company's id before calling any other company 
- `company_roster`: The company page's public roster in one call: the people listed as employees and the people listed as moderators, exactly as the company page renders them to an
- `company_vacancies`: The public board of companies not yet on ClusterHack (a lightweight off-platform listing — name, description, website — not a job-posting system). Public, no fi
- `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.
- `event_branding`: Read an event's white-label branding: brand colours, public-page theme and dedicated subdomain, plus the resolved values actually used for rendering and `brandi
- `event_cities`: The global catalogue of cities (used for the `city` field on `event_create`/`event_update` and to show where events happen).
- `event_faq`: An 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 gu
- `event_free_agents`: List 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 
- `event_get`: Get 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 `se
- `event_info_blocks`: An event's additional free-form information blocks (extra sections shown on its public page beyond the main description — rules, prizes, sponsors notes, etc.).
- `event_leaderboard`: The 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 organ
- `event_list`: Browse 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 
- `event_my_membership`: Summarise 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,
- `event_my_registration_answers`: List the signed-in user's own answers to one event's registration questions. Only ever returns their own data — use `event_registration_responses` (organiser on
- `event_nominations`: An event's award nominations/tracks (e.g. "Best AI prototype"), used when creating teams, awarding winners and building the leaderboard per track.
- `event_presets`: Public catalogue of event-creation presets (AI build day, student hackathon, corporate innovation day, ...) with sensible defaults and starter nominations. Call
- `event_registration_form`: List the custom questions an event asks at registration time (its registration form), in display order. Public data — the question text is visible to anyone. Us
- `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 need to know whether
- `event_schedule`: The event's timeline: an ordered list of stages/activities (opening, workshops, deadlines, closing ceremony) with title, location, time window and status (past/
- `event_share_links`: The 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 whe
- `event_sponsor_text`: Sponsors of one event that are NOT themselves on ClusterHack (a name, description, website and logo entered as free text, with the sponsorship tier each one bel
- `event_sponsor_tiers`: The sponsorship tiers/groups defined for one event (e.g. "Sponsors", "Partners", "General Partner") — the buckets `event_add_sponsor` slots companies into. Publ
- `event_sponsors`: The on-platform companies sponsoring one event, with the sponsorship tier each one is slotted into (e.g. "Sponsors", "Partners", "General Partner"). Public read
- `event_team_stages`: An 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 o
- `event_types`: The global catalogue of event types (used for the `type` field on `event_create`/`event_update`). Small and rarely changes.
- `invite_preview`: Look 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 (a
- `legal_info`: The service's legal identity, as the terms-of-service, privacy and support pages render it: the service and operating entity, whether that entity is registered 
- `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 is read from the liv
- `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 purpose, the role it is
- `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 user means ("the AI 
- `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 revoke the connection.
- `showcase_browse`: Browse the public, cross-event showcase: shipped/submitted projects ranked for display, with title, tagline, team name, vote count and a cover image. Optionally
- `submission_get`: Retrieve one project submission by id: title, links, description, status, approval status, vote count and attached media. Anonymous and unrelated callers only s
- `submission_list`: Browse project submissions, filterable by event, team or status. Anonymous and unrelated callers only ever see submitted (public) projects; a signed-in caller a
- `submission_list_media`: List the screenshots/gallery images attached to a submission. Visibility mirrors the parent submission: public once submitted, otherwise limited to the team, ev
- `submission_page`: Read 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
- `tag_list`: List tags used to categorize content across the platform (articles, projects and more share the same tag vocabulary).
- `team_get`: Get one team's full detail: name, description, project info, readiness, accessibility flags, and which event and nomination it belongs to. Only visible if the s
- `team_list`: List 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 
- `team_locations`: Read 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-servic
- `team_matchmaking_teams`: AI-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 ev
- `team_members`: List 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`: List 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 
- `team_posts`: List 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 wha
- `team_readiness`: Check whether a team has marked itself ready to present, plus whether it is banned or currently accessible for judging.
- `team_roles`: List the roles a team has defined (e.g. "Frontend", "Designer"), which members can be assigned via `team_assign_role`.
- `team_seeking_members`: Browse 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, includi
- `tech_list`: List technologies (tech-stack tags) that projects and teams can be labelled with, e.g. "React", "PostgreSQL".
- `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 this connection was gr

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.