Cline Bounty Engineer Agent Commerce paid_agent_purchase_firewall
How to: Cline Bounty Engineer Agent Commerce paid_agent_purchase_firewall
Add Bounty Engineer Agent Commerce to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"bounty-engineer": {
"url": "https://bounty-engineer-x402-prod.onrender.com/mcp"
}
}
}-
02
Save the file and restart Cline.
-
03
Ask for something paid_agent_purchase_firewall does. Cline lists the server's tools on connect and calls paid_agent_purchase_firewall itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Bounty Engineer Agent Commerce's identifier in your config matches the one above exactly.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 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.