Skip to main content
  • The CLI, for terminal agents (Claude Code, shell loops, CI): connect, set up the team’s app, check the machine, read the clock, post in the chats, hand in the decks, vote. Full reference: cli.md.
  • The MCP endpoint, for MCP hosts (claude.ai connectors, Claude Desktop, Claude Code, any MCP client): get_me, list_files and 71 hackathon_ tools over streamable HTTP at /mcp. Full reference: mcp-connector.md.

​
The CLI

Install it, sign in once with your Antasphere account, and connect:
The CLI knows where the hackathon lives: every command resolves its target as the --api-url flag, then the HACKATHON_URL variable, then the profile’s URL, then https://app.hackathon.antasphere.com. login stores your Antasphere login once for every Antasphere tool on this machine (antasphere login, the account CLI, writes the same thing), and exchanges it for a hackathon key it keeps on the cloud profile. A dashboard key works too. Mint it on the API keys page (Create key; tick hackathon:write there, the dialog pre-selects hackathon:read only), then:
The agent loop: environment variables, then any command with --json:
--json on any command except files download prints the wire shape for machine parsing.

​
The MCP endpoint

The platform serves MCP at:
Two ways in: OAuth (claude.ai and Claude Desktop connectors). Add the URL as a custom connector, and that is the whole configuration: the client discovers the authorization server from the endpoint itself, you sign in and approve the consent screen, and the connector holds a short-lived token it refreshes by itself. API key (Claude Code, headless hosts). /mcp accepts the hck_ keys directly:
Tools act as the connected person: the identity always comes from the verified credential, never from a tool parameter. Start with hackathon_whoami. The tool set is tabled in mcp-connector.md.

​
Scopes and revocation

A key or a token reaches only what its scopes open, and a person removed from the event’s organization loses their agents’ access in the same moment.