Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 60 tools

Disambiguation4/5

Most tools have clearly scoped, mutually exclusive purposes, and descriptions explicitly disambiguate tricky pairs such as company_roster vs company_employees, team_open_roles vs team_seeking_members, and event_schedule vs event_team_stages. A few generic meta tools (list_api_endpoints vs list_capabilities) and the large volume of event/team reads could still cause occasional confusion, but the guidance is strong.

Naming Consistency4/5

Naming is overwhelmingly snake_case with predictable resource prefixes (article_*, company_*, event_*, team_*, submission_*). Minor deviations exist—whoami lacks an underscore, search is unprefixed, and list_api_endpoints/list_capabilities use verb-first naming—but the set remains highly readable.

Tool Count1/5

With 60 tools, this is an extreme mismatch for a single MCP surface; the rubric treats 50+ tools as excessive. Even though the platform spans many resources, the volume imposes high selection overhead and makes it hard for an agent to find the right tool quickly.

Completeness2/5

The surface is almost entirely read-only and omits write/lifecycle tools that the descriptions repeatedly reference, such as article_create, event_create/update, team_post, team_assign_role, invite_join, and team_request_join. Read coverage is broad, but common action-oriented workflows end in dead ends.

Available Tools

60 tools
account_ai_accessManaging AI access to this accountA
Read-only
Inspect

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, because there is deliberately no such tool.

The controls over AI access (list connected clients, revoke one, list and end live MCP sessions, read the record of what a client did as them) are gated to the account holder signing in directly: a browser session, a JWT, or an API token they hold themselves. A connected AI client — including this one — is refused, on purpose. If it were not, a client could revoke its rivals, enumerate the user's other connections, or read the trail it leaves behind. So this tool tells the user where to go and what they will find; it makes no API call and cannot fail.

Also names where account deletion and data export live: the export has a tool (account_export_data), the deletion deliberately does not.

Inputs: no named parameters.

account_how_to_sign_inHow to sign inA
Read-only
Inspect

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 credential endpoints (register, login, JWT issuance, password reset) are the website's login form, not MCP tools: an MCP client authenticates by OAuth 2.1 (the same flow a human approves in a browser tab) and must never see or handle a ClusterHack password directly. This tool works with no account at all, and just explains the steps and links.

Inputs: no named parameters.

article_getGet an articleA
Read-only
Inspect

Retrieve one CMS article by id: its body, publish date, hidden flag, and which title/slug and language it belongs to.

Inputs: article_id (required).

article_languagesList article languagesA
Read-only
Inspect

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.

Inputs: page, page_size.

article_listList articlesA
Read-only
Inspect

Browse CMS articles (the pages under /articles//). Filter by language (a language's short code, e.g. 'en') and/or slug (a title's slug) to find one specific page's translations. Hidden drafts are only included for staff callers; everyone else sees only published articles.

Inputs: page, slug, language, page_size.

article_titlesList article titlesA
Read-only
Inspect

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 always points at one of these; use this to find the title_id article_create needs, or to see what pages exist at all.

Inputs: page, page_size.

company_about_usGet a company's about-us pageA
Read-only
Inspect

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 yet.

Inputs: company_id (required).

company_employeesList company employeesA
Read-only
Inspect

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 company they administer) — the underlying API is already scoped that way. With company_id, narrows to that company only.

Inputs: page, page_size, company_id.

company_employment_requestsList employment requestsA
Read-only
Inspect

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 the request_id for company_decide_employment_request comes from.

Inputs: page, page_size, company_id.

company_ex_employeesList a company's former employeesA
Read-only
Inspect

A company's former employees (position, start and end date) — the record created when someone is fired via company_fire_employee. Without company_id, returns every ex-employment row the caller can see (their own, plus every company they administer).

Inputs: page, page_size, company_id.

company_getGet a companyA
Read-only
Inspect

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 to confirm you have the right company before employment or sponsorship actions, which are irreversible for the people involved.

Inputs: company_id (required).

company_listList companiesA
Read-only
Inspect

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 tool.

Inputs: page, page_size.

company_rosterA company's public rosterA
Read-only
Inspect

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 any visitor.

Use this — not company_employees / company_admins — whenever you want to read someone else's roster. Those two are scoped to self-or-admin, so an outsider gets an empty list from them and cannot tell "nobody works here" apart from "you may not see who does". This endpoint is the part of the page that is already public, and nothing more: no join requests, no ex-employees, no write verbs.

Inputs: company_id (required).

company_vacanciesList off-platform companiesA
Read-only
Inspect

The public board of companies not yet on ClusterHack (a lightweight off-platform listing — name, description, website — not a job-posting system). Public, no filters.

Inputs: page, page_size.

event_background_imagesList certificate backgroundsA
Read-only
Inspect

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

Inputs: page, page_size.

event_brandingGet event brandingA
Read-only
Inspect

Read 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 costume, i.e. whether those values are applied.

Public, because the colours are visible on the event page anyway. Use it before event_set_branding to see what is already set.

Inputs: event_slug (required).

event_citiesList citiesA
Read-only
Inspect

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

Inputs: page, page_size.

event_faqGet event FAQA
Read-only
Inspect

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 guessing, and to check what is already covered before adding more.

Inputs: event_slug (required), page, page_size.

event_free_agentsList free agents at an eventA
Read-only
Inspect

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 own free-agent listing here, while an organiser of the event sees everyone's. Use team_matchmaking_teams on a listing's id for AI-ranked team suggestions for that person.

Inputs: event_slug (required), page, page_size.

event_getGet an eventA
Read-only
Inspect

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 search) and need the details. It does not include the schedule, FAQ or nominations — use event_schedule, event_faq and event_nominations for those.

Inputs: event_slug (required).

event_info_blocksGet event info blocksB
Read-only
Inspect

An event's additional free-form information blocks (extra sections shown on its public page beyond the main description — rules, prizes, sponsors notes, etc.).

Inputs: event_slug (required), page, page_size.

event_leaderboardGet an event's leaderboardA
Read-only
Inspect

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 organiser publishes winners; before that, only the event's admins and judges can preview it (everyone else gets a clear "not published yet" error).

Inputs: event_slug (required).

event_listBrowse eventsA
Read-only
Inspect

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 city. Use this when the user names an event you do not have a slug for and search is not precise enough, or to show a list of upcoming/past events. Hidden events only appear here for their own organisers.

Inputs: page, status, page_size.

event_my_membershipMy status at an eventA
Read-only
Inspect

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, and which roles they hold there (organizer, judge, team lead, ...).

Cheaper than combining several other tools when you just need "is this user in, and how" for one event.

Inputs: event_slug (required).

event_my_registration_answersGet my registration answersA
Read-only
Inspect

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 only) to read other people's.

Inputs: event_slug (required), page, page_size.

event_nominationsGet event nominationsA
Read-only
Inspect

An event's award nominations/tracks (e.g. "Best AI prototype"), used when creating teams, awarding winners and building the leaderboard per track.

Inputs: event_slug (required), page, page_size.

event_presetsEvent creation presetsA
Read-only
Inspect

Public 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 hackathon rather than exact field values.

Inputs: no named parameters.

event_registration_formGet an event's registration formA
Read-only
Inspect

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. Use this before event_submit_registration_answers to know which form_field_ids exist and which are required.

Inputs: event_slug (required), page, page_size.

event_rolesMy roles at an eventA
Read-only
Inspect

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 the user can organise, judge or only take part.

Inputs: event_slug (required).

event_scheduleGet event scheduleA
Read-only
Inspect

The 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". Broadcast link and chat link are only included for the event's admins and registered participants — everyone else sees them blanked.

Inputs: event_slug (required), page, page_size.

event_sponsorsList an event's sponsorsA
Read-only
Inspect

The on-platform companies sponsoring one event, with the sponsorship tier each one is slotted into (e.g. "Sponsors", "Partners", "General Partner"). Public read. Use event_sponsor_text alongside this for sponsors that are not themselves on ClusterHack yet.

Inputs: event_slug (required).

event_sponsor_textList an event's off-platform sponsorsA
Read-only
Inspect

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 belongs to) — the off-platform counterpart to event_sponsors. Public read.

Inputs: event_slug (required).

event_sponsor_tiersList an event's sponsor tiersA
Read-only
Inspect

The sponsorship tiers/groups defined for one event (e.g. "Sponsors", "Partners", "General Partner") — the buckets event_add_sponsor slots companies into. Public read.

Inputs: event_slug (required).

event_team_stagesGet team-progress stagesA
Read-only
Inspect

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 own agenda. Used to track team progress through the event.

Inputs: event_slug (required), page, page_size.

event_typesList event typesA
Read-only
Inspect

The global catalogue of event types (used for the type field on event_create/event_update). Small and rarely changes.

Inputs: page, page_size.

invite_previewPreview an invite linkA
Read-only
Inspect

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 (active, not expired, uses remaining). Use this before invite_join to show the user what they are about to join, or to explain why a link stopped working.

Inputs: token (required).

list_api_endpointsList API endpointsA
Read-only
Inspect

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 live URL configuration, so it always matches what the server actually serves.

Inputs: limit, query.

list_capabilitiesList capabilitiesA
Read-only
Inspect

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 meant for and the permission it consumes. Use it when you are not sure a capability exists — it is cheaper than guessing tool names, and it shows what the user would gain by granting more permissions.

Inputs: category, include_unavailable.

server_infoServer infoA
Read-only
Inspect

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.

Inputs: no named parameters.

showcase_browseBrowse the showcaseA
Read-only
Inspect

Browse 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 event_leaderboard instead when you specifically need judged rankings for one event.

Inputs: page, page_size, event_slug.

submission_getGet a submissionA
Read-only
Inspect

Retrieve 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"); drafts are visible only to the team, the event's admins and its judges. Use submission_list or submission_get_mine when you do not already know the numeric id.

Inputs: submission_id (required).

submission_listList submissionsA
Read-only
Inspect

Browse 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 submission at events they administer or judge. status narrows the returned page client-side (draft / submitted / disqualified) since the underlying list endpoint does not filter by status itself — combine with a larger page_size if you need it applied beyond one page.

Inputs: page, status, team_id, page_size, +1 more.

submission_list_mediaList submission mediaA
Read-only
Inspect

List 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.

Inputs: submission_id (required), page, page_size.

submission_pageRead a project's page and its judge feedbackA
Read-only
Inspect

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, empty otherwise), and — once the organiser has published the winners — its placement, rank and judge score.

This is the tool for "what did the judges say about our project?". submission_get returns the project's own fields and nothing about how it was received; judging_scores_for_submission is scoped to judges and event admins, so a team cannot read its own verdict through it. A submitted project's page is public; a draft is visible only to its team and the event's admins. Before the ceremony the placement is shown to the team and the hosts alone, flagged placement_private so a client says "not announced yet" instead of leaking it. private_note is the organisers' line and is absent — not blanked, absent — from everyone else's payload.

Inputs: submission_id (required).

tag_listList tagsA
Read-only
Inspect

List tags used to categorize content across the platform (articles, projects and more share the same tag vocabulary).

Inputs: page, page_size.

team_getGet a teamA
Read-only
Inspect

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 signed-in user belongs to the team, created it, or administers its event.

Inputs: team_id (required).

team_listList teamsA
Read-only
Inspect

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 full public directory of every team on the platform.

Filter by event_slug to see just one event's teams, or search to match team/project name and description. Use team_get for the full detail of one team once you have its id.

Inputs: page, search, page_size, event_slug.

team_locationsGet a team's locationA
Read-only
Inspect

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-service way to create a new location through this API — location rows are set up separately, then referenced by id via team_additional_info's location_id.

Inputs: team_id (required).

team_matchmaking_teamsSuggest teams for a free agentA
Read-only
Inspect

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 event. Use event_free_agents or event_join_as_free_agent to get a free_member_id. Throttled — do not call it in a tight loop.

Inputs: free_member_id (required), locale.

team_membersList team membersA
Read-only
Inspect

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.

Inputs: team_id (required), page, page_size.

team_open_rolesList open team rolesA
Read-only
Inspect

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 roles, or — if they organise the event — every team's. It is not a public cross-team browse for a stranger looking for any team: that is team_seeking_members, which reads the find-a-team page's own list (pair it with event_free_agents and team_matchmaking_teams). Filter with team_id for one team, or event_slug to see everything the caller can see at that event.

team_id is answered exactly. event_slug (and the unfiltered form) is not: the underlying endpoint narrows by one team at a time and has no event filter, so a very large event can return a note saying rows were left unscanned. Ask per team when that matters.

Inputs: page, team_id, page_size, event_slug.

team_postsList a team's postsA
Read-only
Inspect

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 what a team has been doing, or to check what has already been posted before writing another update with team_post.

Inputs: team_id (required), page, page_size.

team_readinessGet a team's readinessA
Read-only
Inspect

Check whether a team has marked itself ready to present, plus whether it is banned or currently accessible for judging.

Inputs: team_id (required).

team_rolesList a team's rolesA
Read-only
Inspect

List the roles a team has defined (e.g. "Frontend", "Designer"), which members can be assigned via team_assign_role.

Inputs: team_id (required), page, page_size.

team_seeking_membersBrowse teams looking for peopleA
Read-only
Inspect

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, including someone who has not joined the event yet.

This is the tool for a person looking for a team. team_open_roles is the other direction: it lists open positions the caller already has access to (their own teams', or every team's if they organise the event) and shows a stranger nothing. Each row here carries the team's public profile plus its open_roles. Follow up with team_request_join, or list yourself with event_join_as_free_agent if nothing fits.

Inputs: event_slug (required), page, search, page_size.

tech_listList technologiesA
Read-only
Inspect

List technologies (tech-stack tags) that projects and teams can be labelled with, e.g. "React", "PostgreSQL".

Inputs: page, page_size.

whoamiWho am IA
Read-only
Inspect

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 granted, and — crucially — the list of events, teams and companies the user belongs to with the role they hold in each one (organizer, judge, participant, team lead, free agent, builder, speaker, company admin, platform admin).

Use it to decide which tools apply before calling anything else, and to resolve "my event" / "our team" into a concrete slug or id.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables hackathon organizers to manage a GitHub organization through plan-and-confirm natural-language operations, including creating teams and per-team repositories, granting reviewer access, reviewing app installation requests, and freezing or reopening submissions.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Automates the evaluation of GitHub hackathon submissions by providing tools to collect issue data, apply scoring rubrics, and generate ranking reports. It enables a multi-agent system to manage scoring consistency, statistical outlier detection, and feedback generation through the GitHub CLI.
      5
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives a hackathon team's AI coding agents and their humans a shared task board and inbox, so agents can atomically claim tasks, move them between todo/doing/blocked/done, post messages to teammates or the whole team, and read new messages plus board events since they last checked. It also exposes member and agent activity, letting multiple agents working in the same repo coordinate without duplicating work.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any coding model or session to pick up where a previous one left off by keeping handoff state (START / SPEC / DECISIONS / TASKS / LOG) in the repository and projecting each harness's entry files from a single source. It also blocks commits until structural checks and the project's own executable acceptance tests actually pass, providing init, onboarding, session briefing/exit, verification, sync, and task-claim tools.
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources