Devpost - The home for hackathons

Get Hackathon Overview

Returns the title, short summary, full description, optional resources block, host, status, in-person/online classification with venue when applicable, and public URL for a hackathon. Call this first to ground any answer about a hackathon — the description carries the host's pitch (theme, what to build, why it matters), resources points participants at starter kits / docs / APIs the host has linked, in_person_type and location tell you whether participants need to show up somewhere, and the stat

Get Key Dates

Returns the hackathon's submission, judging, public voting, and winners-announced dates as ISO 8601 UTC timestamps, plus the configured time zone and the current phase. Call this before answering questions about deadlines, when participants can submit, or when results will be announced.

Get Prizes

Returns the prize tiers (name, type, amount, winner count, description) and the total prize pool for a hackathon. Call this before answering questions about what participants can win or prize amounts.

Get Judging Criteria

Returns the judging criteria (name, description, position), the scale each criterion is scored on (judging_scale: the highest score a judge can give), and any judging tracks or categories that submissions are sorted into. Call this before answering questions about how submissions are evaluated or which track a project should target.

Get Submission Requirements

Returns the host's prose description of what to submit, the custom questions participants must answer when submitting (id, label, type, required flag, options for dropdowns, allowed_extensions/max_size_bytes for file uploads), and the global deliverable rules (video, website, zip file, kind of submission object). Call this before answering questions about what a participant needs to submit. Each field's `id` is what you pass as `submission_field_id` in submit_project's `custom_answers`. Question

Get Hackathon Rules

Returns the formal rules (terms_and_conditions), how-to-enter instructions, additional user instructions, and a 'who can participate' eligibility block (age, geography, occupation, team, company). Call this before answering questions about eligibility, IP, what's allowed, or how to register. Quote rule and eligibility text verbatim — don't paraphrase.

Get Announcements

Returns the most recent host announcements/updates for a hackathon (title, body, sent timestamp), ordered newest-first. Call this before answering questions about rule changes, deadline shifts, or anything 'recent' — and to surface what's new.

Show Hackathon Stepper

Render the hackathon-journey stepper inline, highlighting the stage the user is on (register -> review -> resources -> prepare -> submit). Call it at the start of each stage with the matching active_step so the user can see where they are. On the 'resources' step, pass build_assistant: true to also show the optional guided build tool, with build_step for its current stage. Orientation only — it changes nothing on the server.

Whoami

Returns the authenticated user's id, email, display name, and granted scopes. Requires mcp:read.

List My Projects

Returns up to 24 of the authenticated user's projects (authored or team-member), filtered to non-spam and non-moderated. In-progress projects (submitted to a hackathon whose winners aren't announced yet) are listed first, followed by the most recently created remaining projects. Each project includes its membership type and the hackathons it has been submitted to (name, slug, public URL).

List Hackathons

Returns the hackathons the authenticated user is connected to — registered for and/or submitted a project to. Each includes its name, slug, public URL, status (submissions_open / judging / closed / upcoming), and the user's relationship(s): registered, submitted.

Search Hackathons

Search the Devpost hackathon catalog. Optional 'query' does a full-text keyword search across title, description, summary, domain, and location (title weighted highest). Supports sorting by relevance ('relevance', default when a query is given), newest ('new'), nearest submission deadline ('ending_soon'), or largest prize pool ('top_prizes'), plus an optional filter for hackathons managed by Devpost. Each result includes title, subdomain, url, start_date and end_date (UTC ISO 8601), prize_pool_u

List Open Hackathons

Returns a cached list of open or upcoming hackathons managed by Devpost (up to 15), newest first. Takes no arguments. Each entry includes title, url, start_date and end_date (UTC ISO 8601), prize_pool_usd (integer), a plain-text description, and themes (array of strings). Intended to be fetched once and matched to the user locally. Response carries hackathons, count, and generated_at. The underlying list is refreshed periodically, so it may lag live catalog changes by a few hours.

Get Project

Returns the details of one of the authenticated user's projects: the name, tagline, writeup, video URL, current state, public URL, and the hackathons it has been entered into. Reads the live, editable project (not a frozen submission snapshot). Only the author or a team member can fetch it. Does not expose judging scores or feedback.

Get Team Invite Link

Returns the secret team invite link for one of the authenticated user's projects. Anyone who opens this link is automatically added as a member of the project, letting them collaborate on it. Use this when the user wants to invite teammates or collaborators to a project, get a shareable join/invite link, or grow their team. The link is project-scoped, not submission-scoped: a person who joins becomes a member of the project across every hackathon it's entered into, not just one submission — make

Get Registration Form

Fetch the registration form spec for a hackathon. Always call this BEFORE register_for_hackathon to discover exactly what to collect from the user. The returned payload tells you: - challenge: basic identity of the hackathon - can_register / already_registered / blocked_reason: whether the user can register at all (stop here if not) - profile.missing_name_fields: name fields the account is missing. A first and last name are required to register — ask the user for each listed field and pass

Register For Hackathon

Register the authenticated user for a hackathon. Submits the same form the web flow uses, with identical validations and the same Rabbitmq event on success. MANDATORY workflow: 1. Call get_registration_form first. Do NOT call this tool until you have its response. 2. If can_register is false, stop and report blocked_reason — do not call this tool. 3. If profile.missing_name_fields is non-empty, ask the user for each listed name and pass it as first_name / last_name — a first and last name

Create Project

Create a new project (a Devpost project — internally a Software record) owned by the authenticated user, FOR a specific hackathon. The `hackathon_subdomain` is required: creating the project also starts a draft submission to that hackathon right away, so you can answer its file-upload questions by uploading directly to the draft (prepare_file_upload). You must already be registered for the hackathon (use register_for_hackathon) and it must be open for submissions. The project can still be enter

Update Project

Edit an existing project the authenticated user owns or is a team member of. Only the fields you pass are changed; everything else is left as-is. Edits automatically propagate to the project's submissions in every hackathon it has been entered into. Note: saving an existing project enforces the full completeness rules (name, tagline, description, and built_with must all be present), so include any that aren't set yet. `links` and `built_with` REPLACE the current values. Photos and team changes

Upload Project Thumbnail

Set the thumbnail image on an existing project the caller owns or is a team member of. Send the image as a base64-encoded string (no `data:` URI prefix). Accepts JPEG, PNG, and GIF up to 5 MB; the new image replaces any previous thumbnail. Returns the project id/slug/URL, the final `thumbnail_url` (404s while `processing` is true, goes live once the background resize finishes, typically within seconds), and the project's version. A non-error response means the upload succeeded — do NOT retry it.

Prepare Thumbnail Upload

Start an out-of-band thumbnail upload that streams the image from disk to Devpost without putting the bytes through the LLM context. Returns an upload URL, a 10-minute TTL, and the OS-specific command(s) you should run. Use this instead of upload_project_thumbnail whenever the image is larger than ~50 KB encoded (i.e. anything that's not a small LLM-generated thumbnail). After the upload command returns 200, parse the JSON response body for the new thumbnail URL — do NOT read the image file into

Prepare File Upload

Start an out-of-band file upload to answer a hackathon's file-upload submission question, streaming the file from disk to Devpost without putting the bytes through the LLM context. If the project has no entry in this hackathon yet, one is started for you as a draft — you must be registered and the hackathon must be open for submissions. Call get_submission_requirements first: file questions have type "file" plus the allowed_extensions and max_size_bytes this upload must respect. One call per fil

Prepare Gallery Image Upload

Start an out-of-band upload of an image to a project's media gallery (the ordered screenshots on the project page), streaming the image from disk to Devpost without putting the bytes through the LLM context. Returns an upload URL, a 10-minute TTL, and the OS-specific command(s) to run. One call per image (a gallery holds up to 15 images; each upload appends). Pass an optional caption. After the upload command returns 200, parse the JSON response body for `photo_id`, `gallery_image_url`, and `pos

Submit Project

Submit one of the authenticated user's projects to a hackathon (or re-submit to update an existing entry). The same project can be submitted to multiple hackathons. MANDATORY workflow: 1. Call get_submission_requirements for the hackathon to learn the custom questions and the deliverable rules (video/website/zip required). 2. Make sure the project itself is complete — name, tagline, description, built_with, and any required video/website. Use update_project to fill gaps. 3. Collect answer