Give Claude direct access to your ad campaigns.
OOSA's Claude Connector exposes your advertising data and controls as MCP tools — so Claude can read performance, surface insights, pause campaigns, and adjust bids directly from a conversation.
47 tools across three ad platforms
Once connected, Claude can query live campaign data, read automation logs, and take reversible actions — all scoped to your brand's accounts. Every write operation is individually confirmed in the conversation before it executes.
Read-only tools carry readOnlyHint: true. Write tools carry
destructiveHint: false — they are all reversible operations with
a full audit trail.
Connected where your spend lives
Tools are gated by the platforms your OOSA brand account has connected. A brand with only Amazon Ads will see Amazon tools; Google and Meta tools appear automatically once those channels are connected.
OAuth 2.0 — standard authorization code flow
The connector uses a standard OAuth 2.0 Authorization Code flow with PKCE. No credentials ever leave your browser — you authenticate with your OOSA account (Google SSO or email OTP) and authorize the Claude client to act on your behalf.
-
1
Click "Connect" in Claude
Claude redirects to
oosa.ai/oauth/authorize/with a PKCE code challenge. -
2
Log in with your OOSA account
Sign in via Google SSO or a one-time email code — the same account you use for the OOSA portal.
-
3
Review the consent screen
Confirm which brand account Claude will access and what the
adsscope permits. -
4
Start talking to your campaigns
Claude now has MCP access to your ad data. Tokens expire after 30 days; refresh tokens are issued automatically.
One scope, explicitly bounded
| Scope | Read access | Write access | What it cannot do |
|---|---|---|---|
ads |
Campaign data, keywords, spend, reports, automation logs | Pause/enable campaigns, adjust bids, add keywords, set budgets, raise alerts | Access billing, modify users, read other brands, access Shopify or Klaviyo data |
Your data stays in your account
The connector reads from OOSA's database, which is populated by your connected ad platform accounts. No advertising data is transmitted to third-party services beyond the platform APIs that OOSA already uses for daily automation. Access tokens are stored as irreversible SHA-256 hashes. Tokens can be revoked at any time from your OOSA portal settings.
Get in touch
For integration questions, reviewer access requests, or partnership inquiries: [email protected]