Cursor Bug Bounty Programs unsubscribe
How to: Cursor Bug Bounty Programs unsubscribe
Add Bug Bounty Programs to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"bug-bounty-programs": {
"url": "https://gateway.pipeworx.io/bug-bounty-programs/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something unsubscribe does. Cursor lists the server's tools on connect and calls unsubscribe itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Bug Bounty Programs's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
Bug Bounty Programs will not start until these are set, so unsubscribe never becomes available.
-
PIPEWORX_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.