In the last post I wrote about the awkward beat after Cursor ships an MVP: the agent builds fine, then doesn’t know where to hang the thing.
We already had REST + OpenAPI for that. Now there’s also a public MCP endpoint, same three moves as the API:
submit_productlist_productsget_product
Point Cursor/Claude at https://launchsignal.ai/mcp (Streamable HTTP, no OAuth this round). Example mcp.json:
{
"mcpServers": {
"launchsignal": {
"url": "https://launchsignal.ai/mcp"
}
}
}
Docs/OpenAPI still at https://launchsignal.ai/docs/api and https://launchsignal.ai/openapi.json. Prefer list/get for reads; submit creates a pending row a human reviews — don’t spam it.
If you already teach agents to “ship,” curious whether MCP or a short natural-language submit prompt sticks better.
Top comments (0)