ph-data-connector-mcp-service
Establishes a persistent link to the Product Hunt data infrastructure via its official Application Programming Interface. This enables retrieval of aggregated information pertaining to product launches, user discourse, curated groupings, thematic categories, and registered participants. Primarily engineered to empower sophisticated Artificial Intelligence entities and conversational agents with direct access to Product Hunt functionalities.
Author

jaipandya
Quick Info
Actions
Tags
🌐 PH Data Connector for Model Context Protocol (MCP)
An ready-to-deploy Model Context Protocol (MCP) backend layer for Product Hunt interactions.
📥 Rapid Acquisition
bash pip install product-hunt-mcp
▶️ Immediate Execution Snippet
bash
Initiate the MCP gateway (Requires setting the PRODUCT_HUNT_TOKEN environmental variable)
export PRODUCT_HUNT_TOKEN=your_secret_api_key product-hunt-mcp
💡 Component Definition
This Product Hunt MCP Gateway bridges the Product Hunt Web Service APIs with any Large Language Model (LLM) or autonomous agent capable of interpreting the Model Context Protocol (MCP). Ideal for augmenting intelligent assistants, sophisticated dialogue systems, or custom automation pipelines!
- 🔎 Access product submissions, discussion threads, topic tags, and user profiles.
- 📊 Retrieve endorsement counts, comment hierarchies, and ancillary metadata.
- 🛠️ Seamlessly interface with platforms like Claude Desktop, Cursor, or any MCP-enabled consumer.
⚙️ Capabilities Overview
- Fetch granular data points for submissions, commentary, thematic structures, and users.
- Implement advanced querying and filtering based on topic relevance, temporal positioning, endorsement metrics, and more.
- Support for deep pagination mechanisms for comment streams and detailed user voting records.
- Engineered atop FastMCP to guarantee high throughput and strict protocol adherence.
🧑💻 Intended Audience
- AI/LLM Practitioners: Integrate effortlessly with Claude Desktop, Cursor, or proprietary agent frameworks.
- Software Engineers: Construct specialized bots, data visualization dashboards, or automated workflows utilizing Product Hunt intelligence.
- Explorers: Engage with the broader MCP ecosystem and prototype novel applications.
🏁 Configuration Guide
Prerequisites for Operation
- Python runtime, version 3.10 or newer.
- An active Product Hunt API Authentication Token (Obtain credentials here).
- A Product Hunt account is mandatory for token generation.
- Within the API Management Console, generate a new application.
- Use the resulting
Developer Tokenfor server authentication.
Important Detail: When registering the application on Product Hunt, a
redirect_urifield is mandatory. Although this MCP server deployment does not utilize callback functionality, a placeholder value (e.g.,https://localhost:8424/callback) must be provided to satisfy the registration form requirements.
Installation Procedures
Recommended: Utilize uv (The contemporary, high-velocity Python dependency manager)
bash
Install uv if not present
pip install uv
Standard Installation via PyPI (Preferred Path)
bash uv pip install product-hunt-mcp
OR standard pip
pip install product-hunt-mcp
Installation from Source Repository (Latest Development Build)
bash uv pip install 'git+https://github.com/jaipandya/producthunt-mcp-server.git'
OR standard pip
pip install 'git+https://github.com/jaipandya/producthunt-mcp-server.git'
Local Source Compilation
bash uv pip install .
OR standard pip
pip install .
🚀 Deployment with Claude Desktop & Cursor
After successful setup, the executable product-hunt-mcp becomes available in your system's path. Integrate this command into your client configuration file:
{ "mcpServers": { "product-hunt": { "command": "product-hunt-mcp", "env": { "PRODUCT_HUNT_TOKEN": "your_secret_api_key" } } } }
- Substitute
your_secret_api_keywith your genuine Product Hunt credential. - The token must be configured via an environment variable within the client's settings to ensure successful authentication.
- Always execute a full restart of Claude Desktop or Cursor subsequent to modifying its configuration JSON.
Troubleshooting Tip (macOS Pathing): If Claude Desktop fails to locate the server executable, it is often due to non-standard PATH settings. Determine the absolute path by running:
bash which product-hunt-mcp
Then, update the configuration object to use this full path instead of the simple command name (e.g.,
"command": "/Users/youruser/.local/bin/product-hunt-mcp").
Locating Client Configuration Files
- Claude Desktop:
- Windows:
%APPDATA%\claude-desktop\config.json - macOS:
~/Library/Application Support/claude-desktop/config.json -
Linux:
~/.config/claude-desktop/config.json -
Cursor:
- Windows:
%APPDATA%\Cursor\User\settings.json - macOS:
~/Library/Application Support/Cursor/User/settings.json - Linux:
~/.config/Cursor/User/settings.json
Containerized Execution (Docker)
You may opt to deploy the service via a container image:
bash
Construct the Docker image
docker build -t product-hunt-mcp .
Run the container interactively (essential for MCP stream)
docker run -i --rm -e PRODUCT_HUNT_TOKEN=your_token_here product-hunt-mcp
For integration into Claude Desktop/Cursor using Docker:
{ "mcpServers": { "product-hunt": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "PRODUCT_HUNT_TOKEN=your_token_here", "product-hunt-mcp"], "env": {} } } }
Security Warning: The
PRODUCT_HUNT_TOKENrepresents sensitive access credentials. Refrain from exposing this key in public repositories or version control systems.
🛠️ Available MCP Operations
| Operation Name | Purpose | Mandatory/Optional Arguments |
|---|---|---|
| get_post_details | Retrieve comprehensive data for a submission | id or slug, comments_count, comments_after |
| get_posts | Query submissions based on criteria | topic, order, count, featured, posted_before, posted_after |
| get_comment | Fetch details for a singular comment | id (required) |
| get_post_comments | Extract commentary associated with a post | post_id or slug, order, count, after |
| get_collection | Obtain details for a specific collection | id or slug |
| get_collections | List collections with filtering options | featured, user_id, post_id, order, count |
| get_topic | Retrieve information regarding a thematic tag | id or slug |
| search_topics | Execute a search against available topics | query, followed_by_user_id, order, count |
| get_user | Fetch profile data for a specified entity | id or username, posts_type, posts_count |
| get_viewer | Retrieve data for the authenticated account | None |
| check_server_status | Verify operational status and authentication | None |
🏗️ Internal Architecture Layout
product-hunt-mcp/ ├── src/ │ └── product_hunt_mcp/ # Core package structure │ ├── init.py │ ├── cli.py # Command line interface bootstrapping │ ├── api/ # Module for API client interactions and request handling │ ├── schemas/ # Pydantic/Marshmallow definitions for data validation │ ├── tools/ # Definitions of the MCP tool interfaces │ └── utils/ # Auxiliary functions and helpers ├── pyproject.toml # Project configuration, dependencies, and build metadata ├── README.md ├── CONTRIBUTING.md ├── CHANGELOG.md ├── Dockerfile └── ... (miscellaneous configuration assets)
♻️ API Quota Management
The underlying Product Hunt API imposes constraints on request frequency. This connector incorporates logic to honor these limitations. Should a rate ceiling be breached, the client will communicate the precise time until the quota is refreshed. Rate status can be inspected via get_api_rate_limits or during a general check_server_status invocation.
🐞 Common Issue Resolution
- Authentication Failure: Confirm that the
PRODUCT_HUNT_TOKENis correctly injected into the execution environment. - Connectivity Problems: Validate network accessibility and ensure the Product Hunt API endpoint is reachable.
- Quota Exhaustion: Reduce the density of requests or adhere to the stated reset window.
- Client Discovery Failure: Re-validate the executable's absolute path within your client configuration and ensure the client application has been relaunched.
🤝 Community Contribution Guidelines
We welcome enhancements and bug reports!
- Adherence to PEP8 standards is expected.
- Linting should be performed using ruff.
- See pyproject.toml for necessary development dependencies.
🔗 External References
- Model Context Protocol (MCP) Specification
- FastMCP Framework
- Product Hunt API Reference
- MCP Tool Inspector Utility
- Curated List of MCP Backends
📝 Legal Notices
- This utility is an independent development and holds no formal affiliation with Product Hunt.
- API specifications are subject to modification by the Product Hunt service providers.
📜 Licensing
Distributed under the MIT License.
WIKIPEDIA CONTEXTUAL REFERENCE (Business Management Tools): Business management tools encompass the entirety of systems, applications, control mechanisms, calculation solutions, and methodologies employed by enterprises to effectively navigate dynamic market conditions, maintain competitive footing, and elevate operational efficacy. These tools span departmental functions, including planning, process oversight, record management, personnel administration, decision support, and performance control. Modern business applications have undergone rapid transformation, moving from rudimentary MIS to complex cloud-based ERP and CRM suites. Successful integration necessitates careful selection and organizational tailoring of the tool, rather than adapting organizational needs to fit off-the-shelf software. Key drivers in this evolution include cost optimization, sales enhancement, customer insight acquisition, and precision in product delivery matching consumer expectations.
