Connect Claude, Cursor, or Windsurf directly to Sovrn AI.
Browser sign-in for interactive clients. No key to paste. Grounded in a model representing ~323M people.
https://sovrn.ai/api/mcp
Sovrn AI
18 typed tools · writes preview first
Choose your client for the exact setup. OAuth is the default; API keys appear only on the HTTP path for scripts and CI.
claude mcp add --transport http sovrn-lbm https://sovrn.ai/api/mcpRun once, restart Claude Code, then type /mcp and pick Authenticate. Your browser opens the Sovrn sign-in.
No key needed. Your browser opens Sovrn sign-in, then asks you to approve tool access. Audience tools are read-only; if you've connected Google Ads in Settings → Connectors, approval also lets this client preview and, after you confirm, apply changes to it.
You describe the people. Your agent chooses the tool.
This list mirrors the server's registered tools. The exact list a client receives can be smaller when a role or plan does not include a tool.
search_audienceDescribe who you need in plain English. The server returns the match, a fit score, behavioral evidence, and related groups — no headcount. Follow-up tools compare, refine, or inspect the result.
estimate_audience_sizeFindNot available on the current index — every call is refused. Use fit (summary.avgScore) and depth (summary.concentration.depth) from search_audience instead; there is no population count.
discover_cohortsFindTest themes against the people you found and see which groups genuinely over-index.
audience_time_seriesCompareCompare interest by hour or day with coverage-normalized periods.
compute_overlapCompareMeasure the observed overlap and its share of each group.
search_audience_excludeCompareFind a group, subtract people you do not want, and keep the cleaner result.
sample_usersInspectInspect a small sample from a result to verify the behavioral evidence behind it.
describe_userInspectRead the behavioral metadata for one pseudonymous result from an earlier search.
list_customer_profilesProfilesSee the Customer Profiles saved in your workspace. Read-only — building or editing a Profile stays in the dashboard.
get_customer_profileProfilesGet one Profile's spec, its latest run, and its week-over-week trends. Deliberately no headcount on this output — no matched-users count, no size, no fit score; read shares and trend direction instead.
generate_audience_briefProfilesGenerate the same server-side brief the dashboard writes for a search — who they are, where to reach them, what works, watch-outs. Durable: a cold call may return pending; free to poll.
get_capabilitiesLearnLoad the data model, limitations, metric definitions, and additional-skill manifest.
read_skill_docLearnFetch a Sovrn reference document when the client cannot read MCP resources directly.
Census context, where present, describes areas in aggregate, not individual traits. There is no population count or market size — results are reported as fit and depth. Small groups are directional.
The server also carries a maintained Google Ads guide. Your agent reads the relevant reference when you ask—not a stale answer from model memory.
See what replaced retired match types, account structures, and bidding practices.
Start with measurement, then settings, structure, bidding, and keywords.
Use observed sites and interests as planning inputs for work in your own ad tools.
This is reference material, not an activation tool. Connect Google Ads in Settings → Connectors to use list_accessible_customers, search, and get_resource_metadata, which read the account you connected, and mutate, which changes it in two steps: a validated preview with before, after and daily spend effect, then apply only after you confirm in chat. API keys can call mutate only if created with Allow Google Ads changes; other keys can search and read but not write. Changes are capped per-call server-side and audited. read_landing_page reads an ad's landing page, only on domains your ads already use, so ad copy claims only what the page says. These tools do not create campaigns. Google Ads connectors are available on request — ask your account contact if you don't see Connectors in Settings.
JSON-RPC 2.0 over POST. This secondary path uses an API key because scripts cannot complete browser sign-in.
curl -X POST https://sovrn.ai/api/mcp -H "Authorization: Bearer YOUR_KEY" -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_audience","arguments":{"prompt":"people shopping for trail-running gear and reading endurance training"}}}'A client can learn the server without a separate SDK or hardcoded integration guide.
Add the server, sign in in your browser, and ask in plain English.