List your product from your AI assistant
Let your AI assistant submit and track your launch. Streamable HTTP at https://pebblelaunch.com/mcp, no API key. Voting stays with people: there is no vote tool.
Connect
Claude Code
claude mcp add --transport http pebblelaunch https://pebblelaunch.com/mcpCursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in your project).
{
"mcpServers": {
"pebblelaunch": {
"url": "https://pebblelaunch.com/mcp"
}
}
}VS Code
Add to .vscode/mcp.json, then start the server from the MCP view.
{
"servers": {
"pebblelaunch": {
"type": "http",
"url": "https://pebblelaunch.com/mcp"
}
}
}Tools
list_launches
{ date? }
A day's launches, featured first, then by votes.
REST: GET /api/launches?date=
get_launch
{ slug }
One product: status, launch day, votes, and the badge snippet once live.
REST: GET /api/launches/{slug}
get_launch_calendar
{ from?, days? }
Seats left per day and the next free day.
REST: GET /api/calendar
submit_product
{ name, tagline, description, url, categories, pricing, logo_url?, screenshots?, maker_name, maker_email, preferred_date? }
Creates the listing. Returns its id, a status key (shown once) and the ownership-proof options.
REST: POST /api/submit
check_status
{ id, status_key, resend_email? }
Re-checks ownership while pending, then reports status and launch day.
REST: GET /api/status/{id} (x-status-key header)
Ownership proof
One of: /.well-known/pebblelaunch-verify.txt containing the token, <meta name="pebblelaunch-verify" content="TOKEN"> on the submitted page, or DNS TXT pebblelaunch-verify=TOKEN. https only, at most 2 redirects on the same domain.
Limits
- 3 submissions per IP per day; one active launch per domain.
- Reads: 60 a minute per IP. Ownership re-checks: once a minute per launch.
See the rules.