# jaipandya/producthunt-mcp-server [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/jaipandya/producthunt-mcp-server  
**GitHub Stars:** 53  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/jaipandya-producthunt-mcp-server

## Description
MCP server for Product Hunt. Interact with trending posts, comments, collections, users, and more.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "producthunt-mcp-server": {
    "command": "uvx",
    "args": ["product-hunt-mcp"],
    "env": {
      "PRODUCT_HUNT_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `PRODUCT_HUNT_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What jaipandya/producthunt-mcp-server MCP server does

The jaipandya/producthunt-mcp-server MCP server connects an MCP-compatible client to the Product Hunt API. It makes Product Hunt entities available as callable tools rather than requiring an agent to handle direct API requests. Supported data includes posts, comments, collections, topics, users, votes, and details about the authenticated Product Hunt account.

The server is suitable for assistants that need to answer questions about Product Hunt activity, developers building bots or dashboards around Product Hunt data, and automations that monitor or filter product discovery information. It is not affiliated with Product Hunt, and the Product Hunt API may change over time.

## How it works

The server runs locally as a Python command-line application and communicates with an MCP client. Product Hunt authentication uses a developer token placed in the PRODUCT_HUNT_TOKEN environment variable. The token is sent to the Product Hunt API for requests that require authentication.

Queries can retrieve individual resources by ID or slug, or return collections of resources with filters. Posts can be constrained by topic, ordering, count, featured status, and posting dates. Comments support post-based retrieval, ordering, counts, and pagination cursors. Collection and topic tools provide lookup and search behavior, while user tools support account details, post types, and post counts.

## Setup and configuration

Python 3.10 or newer is required. Install the published package with `pip install product-hunt-mcp`, or use the equivalent `uv pip install product-hunt-mcp` command. The jaipandya/producthunt-mcp-server MCP server starts with the `product-hunt-mcp` executable after installation.

Create a Product Hunt application and use its Developer Token as the server credential. Set it before starting the process:

```bash
export PRODUCT_HUNT_TOKEN=your_token_here
product-hunt-mcp
```

Claude Desktop and Cursor configurations should run `product-hunt-mcp` and define PRODUCT_HUNT_TOKEN in the configuration's `env` object. Restart the client after changing its MCP configuration. Docker is also supported: build the included image, then run it interactively with PRODUCT_HUNT_TOKEN passed into the container.

## Tools and capabilities

Available tools include:

- `get_post_details` for a post and optional comment retrieval.
- `get_posts` for filtered post listings.
- `get_comment` and `get_post_comments` for comment data.
- `get_collection` and `get_collections` for collection lookups and listings.
- `get_topic` and `search_topics` for topic retrieval and search.
- `get_user` and `get_viewer` for user and authenticated-account information.
- `check_server_status` for API connectivity and authentication status.

The README also refers to `get_api_rate_limits` when discussing rate-limit status, but it is not included in the listed MCP tools.

## Limitations and notes

A valid Product Hunt API token is required, and requests remain subject to Product Hunt rate limits. When limits are reached, the client reports when the limit resets; reducing request frequency may be necessary. Missing credentials, network access problems, or an unavailable Product Hunt API can prevent requests from succeeding.

The jaipandya/producthunt-mcp-server MCP server does not use the OAuth redirect URI for its own operation, although Product Hunt requires a valid redirect URI when creating an application. Store PRODUCT_HUNT_TOKEN outside source control because it is sensitive. On macOS, clients may need the full path to the installed executable if it is not available on the default PATH.

_Full upstream README: https://allmcps.com/mcp/jaipandya-producthunt-mcp-server/readme_