What Product Hunt MCP server does
Product Hunt MCP server exposes Product Hunt research and launch-management workflows to MCP-compatible AI clients. Its research tools cover categories, products, recent launches, alternatives, detailed product profiles, leaderboards, and launches that Product Hunt's model ranks highly for potential Series A fundraising. Results can include ratings, makers, categories, links, launch dates, funding, company details, and relevance or ranking information.
The authenticated launch tools work with launches that the signed-in user owns or manages as a hunter, maker, or active product team member. They can inspect account identity, list launches, read launch state, open a website editor, prepare images, update editable fields, preview submissions, and submit launches for scheduling. Drafts remain private until submission or another action makes content public.
How it works
The server is accessed as a remote Streamable HTTP MCP server. Sign in with Product Hunt through the installation flow; an API key is not required. Once connected, research tools can be used for public Product Hunt information, while launch-management tools operate on the authenticated account's permitted launches.
Launch submission is deliberately confirmation-based. A preview call returns the resolved product, launch day, public content, makers, images, comments, shoutouts, programs, warnings, and side effects. The launch is submitted only after the user reviews that preview and the client sends the returned confirmation token. Update operations can likewise require a preview and explicit approval when they may affect public content, move a launch day, or notify makers.
Launch images are staged separately from attaching them to a launch. An image can be supplied by public URL, uploaded to the Product Hunt-provided upload endpoint, or sent as base64 content when the client cannot reach that endpoint. Ready assets are then attached through the launch update operation.
Setup and configuration
Connect an MCP client to the Product Hunt installation endpoint at https://www.producthunt.com/mcp/install and complete Product Hunt sign-in. No Product Hunt API key is needed, and this server does not require environment variables for its connection.
The client must be able to use a remote Streamable HTTP MCP server. Account-scoped launch actions depend on the permissions of the signed-in Product Hunt account. Before making a change, clients should reread a launch after opening its editor or after competing edits, because the launch revision can change.
Tools and capabilities
Research and discovery include:
- Listing Product Hunt categories and slugs for use in other searches.
- Finding products by category, pricing, open-source status, or recency.
- Searching launches by text, category, date window, pricing, open-source status, or YC status.
- Searching products semantically from a natural-language use case.
- Finding alternatives with optional pricing, open-source, recency, and feature-tag filters.
- Reading product profiles with reviews, ratings, makers, company information, funding, and social links.
- Retrieving ranked daily, weekly, monthly, or yearly leaderboards.
- Finding launches in the model's Top 10% Series A ranking bands.
Launch operations include account lookup, launch-context checks, owned-launch listing, launch retrieval, website editing, preview retrieval, draft creation or resumption, field updates, submission previews, confirmed submission, and asset preparation. Launch reads expose editable fields, revision identifiers, assessment items, applicable actions, prepared assets, and website links. The feedback tool sends comments to the Product Hunt team only when the user explicitly requests or approves it.
Limitations and notes
A launch's availability snapshot is not a reservation. Product Hunt launch states distinguish drafts, unscheduled launches, scheduled launches, and live launches; changes to live or potentially public content may have immediate visibility. The client should change only fields reported as editable and use the expected revision when updating.
Submission always requires two calls: one to produce the preview and another with the confirmation token. Tokens expire after 15 minutes and become invalid if launch data, permissions, assets, or launch-day availability changes. Idempotency keys allow identical retries when an operation's outcome is unknown.
Prepared images must be PNG, JPEG, WebP, or GIF, no larger than 10 MB, 10,000 pixels on either side, or 40 megapixels. Base64 asset submissions are limited to 3 MB by the server, and clients may impose a smaller limit. The startup-ranking feature is a Product Hunt model ranking, not investment advice.