Browse public product launches and post summaries using fixed read queries.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List public post summaries — producthunt.posts.list |
Read |
Get public post summary — producthunt.posts.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Product Hunt, then enter the issued values in the connection form below.
- Product Hunt requires its permission for commercial API use. Obtain that permission through the contact listed in its official API documentation before using this integration for a business; an API token alone is not that permission. In the Product Hunt API dashboard create an application and register https://api.tooluse.net/v1/oauth/callback. In My tools, open Product Hunt, choose Use my provider credentials, enter the OAuth client ID and secret, select read commands and save, then choose Sign in to provider. Consent requests public only, without private or write access. You can instead paste a developer access token for an authorized use. The published token response does not declare expiry or refresh: Tooluse.net does not invent scheduled renewal; reconnect if revoked. List one public post page with first=20 and optionally after from pageInfo.endCursor, or get an existing post slug. The queries are fixed read documents; arbitrary GraphQL, votes and follows are unavailable. Disconnect locally and remove access in Product Hunt when finished.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| OAuth access token (optional) | Optional |
| Product Hunt OAuth client ID | Optional |
| Product Hunt OAuth client secret | Optional |
| Registered OAuth redirect URI (optional) | Optional |
| Return URL after authorization | Optional |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"first": 20
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List public post summaries — producthunt.posts.list
Read one explicit public Product Hunt post page with names, slugs, taglines, vote counts, URL and creation date. The provider defaults to posts from the last month. Pass pageInfo.endCursor as after to continue deliberately; no private data, votes or follows.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.first |
integer | Required | Posts requested in this page; choose 20. GraphQL Int and the response byte budget apply. | minimum: 1; maximum: 2147483647 |
query.after |
string | Optional | Opaque cursor from the preceding response; omit on the first page. | maxLength: 8192; pattern: "^[\\x21-\\x7e]{1,8192}$" |
Full JSON Schema
Example input
{
"query": {
"first": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Get public post summary — producthunt.posts.get
Read public metadata for an existing Product Hunt post slug using a fixed GraphQL query. No private user data, comments, votes or follows.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.slug |
string | Required | Existing post URL slug. | maxLength: 512; pattern: "^[A-Za-z0-9_-]+$" |
Full JSON Schema
Example input
{
"query": {
"slug": "example"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.