This is the MCP path for coding agents: add the server, then call apply with the site URL, contact email, and publisher name. Connecting is not an application. Humans can skip MCP and sign up / log in instead.
No agent? Sign up as a publisher. Already signed up? Log in.
One click for Cursor or VS Code, or add the config block to any MCP client. This only connects the tools. It is not an application.
ChatGPT: Settings → Connectors → Advanced → Developer Mode, then Add custom connector with URL https://rocketsloth.ai/mcp, authentication None.
{"mcpServers":{"rocketsloth":{"url":"https://rocketsloth.ai/mcp"}}}The first tool call is apply, not about. Fill in your site, email, and name. Humans can skip MCP and sign up on the web — same application.
Apply to Rocket Sloth for https://YOUR-SITE.com. Contact email YOUR@EMAIL, publisher name YOUR FULL NAME. Then call integration and add the script tag and ad units it returns. Connecting MCP is not an application.
After apply, call integration and paste the script (your pk_ key) into <head> and at least one <div data-rs-ad></div> on the page. Publish. Placeholder ads start immediately. This is only the shape — do not ship the placeholder key:
<script src="https://rocketsloth.ai/rs.js" data-rs-key="pk_your_key_here"></script> <div data-rs-ad></div>
The rocketsloth CLI exposes the same tools as subcommands — one line installs it:
curl -fsSL https://rocketsloth.ai/install.sh | sh
Full reference on the CLI page. If your agent can’t reach the MCP server directly, hand it the skill file (https://rocketsloth.ai/skill.md) — it teaches the whole workflow: apply, integrate, approval, reporting, payouts, and recovery.