Devpost Hackathons

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 that clear when sharing it. Returns the link and its expiration. Only the project's author or an existing team member can fetch it.

get_team_invite_link

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.

list_hackathons

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_my_projects

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.

list_open_hackathons

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 file (a question accepting several files needs several prepare/upload rounds, up to 10 files per question and 15 across the whole submission). Returns an upload URL, a 10-minute TTL, and the OS-specific command(s) to run. When the upload command returns HTTP 200 the file is ALREADY attached to the submission — that IS the answer to this question. Do NOT read the file into the conversation and do NOT pass anything for this question to submit_project. Each command runs exactly once: re-running it is refused, so if you don't see a 200, check the question's answer with get_submission_requirements before preparing a new upload.

prepare_file_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 `position` — do NOT read the image file into the conversation. Accepts JPEG, PNG, GIF up to 5 MB.

prepare_gallery_image_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 the conversation. Accepts JPEG, PNG, GIF up to 5 MB.

prepare_thumbnail_upload

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 are required to register. Never invent a name. 4. Ask the user to pick intending_to_team_up from team_preference_options. 5. Only if intending_to_team_up == 'Looking for teammates', offer to collect a short description (max 255 chars). 6. For each entry in custom_questions, ask the user. Every question with required=true MUST have an answer in custom_answers. For multi-select dropdowns, pass an array of strings. 7. Show the user agreements.rules_url AND agreements.terms_url, then ask for explicit confirmation. Only then set agree_to_rules=true. 8. If eligibility.requires_agreement is true, show eligibility.description verbatim, then ask for explicit confirmation. Only then set agree_to_eligibility=true. 9. Optionally offer the survey ('Who told you about this hackathon?'). If the user answers, pass source (and source_medium if the chosen source allows mediums, and source_specifics if source='Other'). If they skip, omit all three. 10. Submit. On success you get registration_id; on validation failure you get an InvalidParams error with the underlying message — relay it. NEVER set agree_to_rules or agree_to_eligibility to true without explicit confirmation from the user in this conversation.

register_for_hackathon

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_usd (integer), and managed_by_devpost (boolean). Paginated (default 5, max 25 per page); response carries query, count, total, total_pages, page, limit, sort. Rate limited to 10 calls per 60 seconds per user.

search_hackathons

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.

show_hackathon_stepper

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 answers to every required custom question into custom_answers. Do NOT include file-upload questions (type == 'file') here — upload each file with prepare_file_upload, which attaches it directly to the submission; an already-uploaded file is the answer. When updating an existing entry, answers already saved on it count — only send what you're adding or changing. 4. Submit. If the project doesn't meet the requirements this tool will NOT submit — it returns an error itemizing exactly what's missing. Fix it and retry. The user must already be registered for the hackathon (use register_for_hackathon) and the hackathon must be open for submissions. Returns the submission id, status ("Draft" or "Submitted"), and URL.

submit_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 aren't supported over MCP. To change the thumbnail, use the prepare_thumbnail_upload and upload_project_thumbnail tools. Returns the project's id, slug, URL, and new version.

update_project

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. Best for small images only: target ≤ 50 KB encoded (e.g. a 300×300 JPEG at quality 60). Pre-shrink the image in one step before calling — DO NOT iterate. For larger or higher-quality images, use `prepare_thumbnail_upload` instead, which returns a curl/PowerShell command that streams the file from disk without putting the bytes through the LLM context at all.

upload_project_thumbnail

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

whoami