Hand ad setup to your coding agent.

1. Sign in to your workspace, then open Settings → MCP.
2. Pick a client (Cursor / VS Code one-click, Claude Code CLI, Claude Desktop, or Manual).
3. Approve the workspace and environments on the consent screen.
4. Ask the agent to call list_sites, create_site, create_group, and get_integration.

Connected clients show in the same Settings panel. Workspace owners and admins can revoke access there. Consent is limited to owners and admins.

https://adsroster.com/mcp

• list_sites — websites in the workspace for an environment.
• create_site — create a website (idempotent on slug).
• create_group — create one placement with N spots. There is no bulk create — call it once per group when you need multiple placements or pages.
• get_integration — public key, placement slug/spots, and SDK snippets for wiring delivery.

Use a separate placement for each UI area or page (hero vs sidebar, /create vs /puzzle). Each group's path is a single site-relative page path — never comma-join routes. Do not ask AdsRoster to choose DOM placement; that stays with the coding agent.

• Coding agent — inspect the repo, install the SDK, decide where spots render, keep your design system.
• AdsRoster MCP — sites, groups, spots, public keys, integration snippets.

After inventory exists, follow Integration for delivery: drive UI count from spots.length (never hardcode), omit only paused spots (enabled: false), and use fallback for empty enabled spots.

Payouts, withdrawals, refunds, Bachs secrets, campaign approvals, advertiser booking, placement suggestions, analytics, and long-lived API tokens are not available over MCP.

Access tokens are short-lived; refresh tokens rotate. Useful paths on adsroster.com:

• MCP endpoint: /mcp
• Protected resource metadata: /.well-known/oauth-protected-resource/mcp
• Authorization server metadata: /.well-known/oauth-authorization-server
• OAuth: /oauth/register, /oauth/authorize, /oauth/consent, /oauth/token, /oauth/revoke