ClusterHack speaks MCP. Point Claude, Cursor, or anything else that talks the protocol at one URL, sign in once, and it can do what you can do on the site — open an event, chase teams, score as a judge, publish the winners — as you, under your own permissions.
Nothing to install, no API key to mint. Give your client the endpoint; it discovers the login on its own, opens a consent screen in your browser, and remembers you from then on.
$ claude mcp add --transport http clusterhack https://clusterhack.dev/mcp/ # then, inside Claude Code: > /mcp # sign in, review the permissions > "what am I organizing right now?"
https://clusterhack.dev/mcp/
Add it to ~/.cursor/mcp.json, or to the
project's own .cursor/mcp.json:
{
"mcpServers": {
"clusterhack": { "url": "https://clusterhack.dev/mcp/" }
}
}
Add it to .vscode/mcp.json in your workspace:
{
"servers": {
"clusterhack": { "type": "http", "url": "https://clusterhack.dev/mcp/" }
}
}
Any client that supports remote MCP servers over Streamable HTTP with OAuth works. None of this is ClusterHack-specific — it is the standard discovery chain, so registration happens without you filling anything in.
# endpoint (Streamable HTTP) https://clusterhack.dev/mcp/ # your client finds the rest by itself: /.well-known/oauth-protected-resource # RFC 9728 /.well-known/oauth-authorization-server # RFC 8414 /oauth/register # RFC 7591
Protocol revisions spoken:
2025-06-18,
2025-03-26,
2024-11-05 — negotiated during
initialize.
Listed in the official MCP registry as
dev.clusterhack/clusterhack — clients that read
the registry can add it by name. Connected something already? Review or cut
it off any time at /settings/connections/.
Open an event, build the timeline, write the rubric, invite judges, watch the room on the day, crown the podium — then clone the lot for next year.
“set up a 24h hackathon with 5 criteria”
“who checked in but has not joined a team?”
“publish the winners”
Join an event, put yourself up as a free agent, form or join a team, plan the build on a board, then submit the project with its screenshots and pitch deck.
“find teams looking for a backend dev”
“break our idea into cards on a board”
“submit the project with these three shots”
Pull your assignments, read each rubric, submit a whole scoring pass in one call, and leave notes only the organizers ever see.
“what is left for me to judge?”
“score submission 42 on every criterion”
“flag this one privately for the organizers”
Keep the company page current, decide who joins the roster, sponsor an event and its prize tracks — or simply check where and when you are due on stage.
“who is waiting to join our company?”
“sponsor the AI track at this event”
“when am I speaking this weekend?”
261 tools across 15 areas — events, teams, submissions, judging, companies, boards, billing, notifications and the rest. Your client only ever lists the ones your account can actually use. Full catalogue in the docs.
Every call goes through the site's own permission checks — the very code that guards the web pages. There is no second, looser door. A refusal means you genuinely lack that right, not that something is misconfigured.
The consent screen spells out what is being asked for and lets you untick any of it. Reading other participants' personal data is off by default, and even then works only where you already administer the event.
Cut off any connected app instantly from connections. Every call is written to an audit log, with secrets and personal data redacted.
Free, on every plan. One command, one sign-in, no API key. Never run a hackathon here before? Start one first — the assistant can do that part too.
$ claude mcp add --transport http \ clusterhack https://clusterhack.dev/mcp/ ✓ connected · 261 tools