# Pluggyback for coding agents > Pluggyback (https://pluggyback.com) is a network where indie software products show a small "Promoted" card for each other. This guide is for a coding agent that registers a member's product, installs the card snippet and verifies the site, holding only an API key. ## What a person does first 1. Signs in at https://pluggyback.com/signin. Creating the account stays with a person. 2. Creates an API key at https://pluggyback.com/app/agent. The key starts with pb_live_ and is shown once. An account holds up to 5 keys, and a revoked key stops working at once. 3. Gives the key to the agent, through the agent's MCP settings or the environment variable PLUGGYBACK_API_KEY. Never print, log or commit the key. ## The endpoint - MCP server, Streamable HTTP, stateless, JSON responses: POST https://pluggyback.com/api/mcp - Send the key on every request: Authorization: Bearer pb_live_... - Tools only. No sessions, no server-sent events. GET answers 405. - Without an MCP client, call it as plain JSON-RPC 2.0 over HTTP: curl -s https://pluggyback.com/api/mcp \ -H "Authorization: Bearer $PLUGGYBACK_API_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}}' The tool's output is JSON in result.content[0].text and in result.structuredContent. When result.isError is true, the text says what to fix. ## Connect a client Claude Code. Run once in a terminal: claude mcp add --transport http pluggyback https://pluggyback.com/api/mcp --header "Authorization: Bearer pb_live_YOUR_KEY" Cursor. Add to ~/.cursor/mcp.json: { "mcpServers": { "pluggyback": { "url": "https://pluggyback.com/api/mcp", "headers": { "Authorization": "Bearer pb_live_YOUR_KEY" } } } } VS Code. Add to .vscode/mcp.json. VS Code asks for the key and stores it, so the file holds no secret.: { "inputs": [ { "type": "promptString", "id": "pluggyback-key", "description": "Pluggyback API key", "password": true } ], "servers": { "pluggyback": { "type": "http", "url": "https://pluggyback.com/api/mcp", "headers": { "Authorization": "Bearer ${input:pluggyback-key}" } } } } Codex. Add to ~/.codex/config.toml, then set PLUGGYBACK_API_KEY in your shell: [mcp_servers.pluggyback] url = "https://pluggyback.com/api/mcp" bearer_token_env_var = "PLUGGYBACK_API_KEY" Other clients. Any client that speaks Streamable HTTP: URL: https://pluggyback.com/api/mcp Header: Authorization: Bearer pb_live_YOUR_KEY ## The flow 1. whoami: check the key and see whose account it is. 2. suggest_categories with the product's https address. It proposes a name, a tagline of at most 60 characters, a category, a subcategory and accepted categories. Check them against what the product really does. 3. create_product with url, name, tagline, category and subcategory. The product starts as a draft. Keep its id. 4. get_install_snippet with the product id, the project's framework (html, nextjs or react) and a placement. The snippet has the product's real key in it. Add it to the code exactly as given. 5. The person deploys. 6. check_install. It fetches the site, finds the script with the product's key and verifies the domain. When an agent-registered draft is verified it goes to review on its own, and the owner gets an email with the listing and categories the agent chose. If found is false, reason names the problem: script_missing, wrong_key, different_domain or fetch_blocked, and detail says what to fix. 7. A person at Pluggyback reviews the product, usually within a day. Nothing shows on the site until it is approved, so an empty slot right after install is expected. If the site cannot carry the script on its home page, get_verification gives a meta tag and a DNS TXT record that verify the domain instead. ## Install rules - Put the slot where real visitors will see it. Hidden, tiny or covered slots earn nothing. - Keep the attributes and the min-height on the div, and the data-key on the script, exactly as given. - The script tag must be in the HTML the server sends. In React or Next.js write it as a plain