Producthunt

• Get my Product Hunt account — Return the authenticated Product Hunt account identity.
• Get launch requirements and context — Read composer limits, account eligibility, midnight-Pacific date availability, the existing product a link belongs to, your matching draft, and bounded topic/category/maker/funding backer/shoutout product suggestions. With no product, the launch is a new product and needs no product question. Availability is a snapshot, not a reservation.
• List my launch work — List drafts you own and launches you can manage as hunter, maker, or active product team member. permitted_actions lists the read tools and website editing that apply to each item.
• Get my launch draft — Read your launch draft and what still needs a change or a decision before it can be submitted. write_revision is the value draft-writing tools take as expected_revision.
• Assess my launch draft — Check your saved launch draft against current launch rules: what blocks submission and which decisions are open. Resolution options are alternatives; suggestions are optional.
• Get a launch I can manage — Read a launch you can manage as its hunter, maker, or active product team member. Editable fields describe website editing.
• Start a launch draft — Start a launch draft for a product link, or resume your existing incomplete draft for the same link and product choice without changing it (created: false). Omit product_choice for a new product; nothing needs confirming. Only when get_launch_context finds an existing product for the link, ask the user whether this launch belongs to it, then send product_choice "existing" with its product_id; a link that belongs to an existing product is refused as new. Initial values use the same fields as upda
• Update a launch draft — Save partial changes to your launch draft. Send only the fields the user asked to change: an omitted field keeps its saved value, null clears it, and additionalLinks replaces the whole list. expected_revision is write_revision from get_launch_draft or the previous write. If the draft changed since then, nothing is saved and the result is a conflict: read the draft again, keep the user's requested changes, ask about competing edits, and send only those changes. Incomplete drafts save; assessment
• Prepare a launch image — Stage a thumbnail or gallery image for exactly one owned draft or launch you can manage. This never changes displayed images or the draft revision. Supply source_url to import a public PNG, JPEG, WebP or GIF (up to 10 MB, 10000 pixels per side and 40 megapixels). Otherwise send the file as multipart form data to upload.url with upload.headers, for example curl -X POST -H "Authorization: Bearer <upload ticket>" -F file=@image.png <upload.url>. The upload ticket authorizes only this asset's bytes
• Preview submitting a draft, or editing or rescheduling a launch — Preview what a launch command would do, without doing it. With draft_id (operation submit, the default), it previews submitting your saved launch draft: operation is the complete submission as Product Hunt would carry it out: the resolved product, launch day, public content and links, final launch tags (including ones added from links or contests), makers including you when isMaker, images, first comment, shoutouts with their notes and ratings, funding, company, investor answers, contest and lau
• Submit a previewed launch draft — Submit your launch draft exactly as preview_launch showed it. Call this only after showing the user that preview (operation and side_effects) and getting their explicit confirmation; the preview_token proves which preview was returned, not that the user approved it. Submitting creates the launch on its launch day and carries out every side effect the preview listed, such as adding makers, posting the first comment, publishing shoutout reviews, entering programs and notifying followers. Product H
• Apply a previewed launch edit — Apply an edit to a submitted launch exactly as preview_launch (operation edit) showed it. Call this only after showing the user that preview (operation and side_effects) and getting their explicit confirmation; the preview_token proves which preview was returned, not that the user approved it. The token carries the reviewed changes, so nothing else is sent. Only the changed fields are written: everything else on the launch, including its launch day, stays as it is. Replaced lists, product page c
• Move a launch to a previewed day — Move a submitted launch that is not live yet to the day preview_launch (operation reschedule) showed, at exactly 00:00 America/Los_Angeles. Call this only after showing the user that preview (operation and side_effects) and getting their explicit confirmation; the preview_token proves which preview was returned, not that the user approved it. The token carries the reviewed day, so nothing else is sent. Ad orders and ad campaigns listed in the preview move with the launch; nothing else about the
• Send feedback about the Product Hunt MCP — Tell the Product Hunt team where this MCP server fell short. Call it when the user wants to give feedback about it, or once per task when a tool failed, returned something wrong or confusing, or no tool could do what the user asked. Never include secrets or personal details about anyone.
• Browse Product Hunt categories — List all available Product Hunt categories with their slugs. - When to use: When you need to find the right category_slug for get_products or search_launches, or when the user asks what categories Product Hunt has, or wants to browse available topics. - Returns: All searchable categories organised by parent/child hierarchy with slugs. Use the slug values directly in get_products(category_slug) or search_launches(category_slug).
• Get products by category — Get top-rated or recently launched products in a Product Hunt category. When to use: "best [topic] tools", "top [topic] apps", "find me a [topic] app", "top open source [topic] tools", "best free [topic] apps". Filters use named no-op defaults: pricing: "any" | "free" | "free_options" | "payment_required" (default "any") open_source: "any" | "open_source_only" (default "any") Pick a non-default sentinel ONLY when the user said the matching constraint. W
• Find alternatives to a product — Find alternative products to a given product. When to use: "alternatives to [product]", "apps like [product]", "[product] competitors", "what can I use instead of [product]?". Filters use named no-op defaults: pricing: "any" | "free" | "free_options" | "payment_required" (default "any") open_source: "any" | "open_source_only" (default "any") recency: "all_time" | "today" | "this_week" | "this_month" | "this_quarter" | "t
• Get product details — Get detailed information about a product including description, makers, categories, social links, pricing, ratings, review highlights, and credibility signals like YC backing, funding, founded date, and team size. - When to use: "tell me about [product]", "what is [product]?", "who made [product]?", "give me info on [product]", or wants a comprehensive overview of a specific product. - Args: product_name (name or slug). - Returns: Full profile with reviews, rating, sentiment, and credibility det
• Search product launches — Search recent product launches on Product Hunt. When to use: "what's new?", "latest AI launches", "trending products this week", "new tools launched today", "new YC startups", "open source products launched this week", "free AI tools", "paid AI tools launched recently". Filters use named no-op defaults: pricing: "any" | "free" | "free_options" | "payment_required" (default "any") open_source: "any" | "open_source_only" (default "any") yc: "any"
• Semantic product search — Search Product Hunt products by natural-language topic or use case using vector similarity. When to use: The user describes what they want without naming a category or product. Prefer get_products when the user asks for a category and find_alternatives when they name a specific product. Filters use named no-op defaults: pricing: "any" | "free" | "free_options" | "payment_required" (default "any") open_source: "any" | "open_source_only" (defaul
• Product Hunt leaderboard for a day, month, or year — Get the ranked Product Hunt leaderboard for a specific day, week, month, or year. - When to use: The user asks "what won on [date]?", "top launches in [week/month/year]", "#1 product on [date]", "Product Hunt winners for [period]", or wants the official ranking for a past or recent day, week, month, or year. - Args: date (required; YYYY-MM-DD for a day, YYYY-Www for an ISO week, YYYY-MM for a month, or YYYY for a year), limit (default 5, max 8). - Returns: Top-ranked products for that period wit

Schemas and invoke metadata: Directory API