Fast. Flexible. Built for how media actually moves.
The AMAP MCP server isn't a wrapper around a database. It's an audience graph shaped for the way planners and traders already think — and structured to push live to every major platform from a single prompt.
Sub-second responses.
Pre-indexed at the ZIP and census-block level. Most prompts return audience composition, geo ranking, and activation IDs in under a second — no model retraining, no overnight builds.
Compose any audience in a sentence.
50,000+ Geograph, third-party, government, and proprietary signals — all queryable in one prompt. Mix demographics, intent, life events, and behavior into a custom recipe on the fly.
One config block. Done.
Drop a single JSON block into Claude Desktop, Cursor, ChatGPT, or any MCP-compatible client. No SDK, no infra, no data team. We're live in your stack in under a minute.
Speaks the data structure of planning + activation.
Every response is shaped for the way media is actually planned and bought — segments, geographies, indices, activation IDs ready to traffic. Push to TTD, DV360, Meta, Google, CTV, and DOOH from the same prompt.
An audience graph an AI can actually think in.
We modeled this MCP on a decade of audience strategy work. Then we rebuilt the AMAP taxonomy and Geograph indexing engine around how an AI agent actually queries — composable, geographic, and aggregation-first.
The agent doesn't sit on top of our data. It thinks in it.
The old way wasn't slow. It was stitched together.
This isn't just faster. It's a different workflow entirely.
Three reasons audience strategists keep this tab open.
Index any audience in 30 seconds.
Ask in plain English, get composition and index back instantly across ZIP, census block, county, or DMA. No CSV exports, no waiting on a data team.
50,000+ segments. One query.
Unified access to Geograph audiences, third-party (Acxiom, Experian-class), government, and proprietary signals — composable in a single prompt.
Geo + behavior + intent — composable.
Census-block resolution, life events, purchase intent, search listening, and custom recipes. The targeting layer no general-purpose AI can compose on its own.
Decision in. Audience out.
Pick geographies by who's actually there.
The AMAP MCP returns a composition + index for every segment, at every geographic resolution, in a single prompt. Ask for an audience — get back the ZIPs, blocks, or DMAs that over-index for it.
Then filter your campaign, brief your agency, or push the segment straight to a DSP.
Tune the inputs. Watch the audience move.
Not just who. Where.
Some places just matter more.
The cookie tracked users.
Signals understand them.
Try a sample query.
{
"audience": "pet_owners",
"geo_level": "zip",
"dma": "Los Angeles",
"results": [
{ "zip": "90272", "composition": 0.41, "index": 184 },
{ "zip": "91011", "composition": 0.39, "index": 176 },
{ "zip": "90402", "composition": 0.38, "index": 172 },
{ "zip": "91436", "composition": 0.37, "index": 168 },
{ "zip": "90049", "composition": 0.36, "index": 164 }
],
"source": "AMAP · Geograph",
"privacy": "aggregated_no_pii"
}Illustrative. Real values are returned live from AMAP per query.
Eight things you can do today.
Each card is a real MCP tool call. Pick one, copy the JSON-RPC payload, or hit Run to send it live to mcp.amapdata.com.
ZIP, census block, county, or DMA — composition + index returned for any AMAP segment in one call.
Their day vs. your day.
- · 6 tabs, 6 logins. Re-query each.
- · CSV exports. Rebuilt every campaign.
- · Click-only UIs. AI agents can't use them.
- · Audience + geo + intent stitched manually.
- One prompt. Unified across 50K+ segments.
- Live at the brief. Indices always current.
- Agent-native. JSON in, JSON out.
- Activation IDs returned ready to traffic.
Build once. Deploy everywhere.
Node
Plan vs. actual, in the same chat.
Post-flight, the same MCP can pull AMAP audience-level delivery — what was forecasted versus what actually reached. Ask in the thread, get the comparison back. No second login.
See how each segment performed against plan — broken out by audience and geography. No more end-of-flight hand-waving about whether the activation hit.
Request a sample report →Audience creation becomes infrastructure.
Admin builds & activates instantly
Strategists run prompts, ship audiences to DSPs in one motion.
Teams plug into the API
Agencies and brand teams wire AMAP into their planning + activation stack.
Clients upload & activate their own data
First-party data lands → Geograph indexes → audiences ship. Self-serve.
Deploy in under a minute. Built for any MCP client.
One JSON block. No SDK, no infra, no data team. Drop it into Claude Desktop, Cursor, ChatGPT, or any MCP-compatible client — start querying audiences and pushing to TTD, DV360, Meta, Google, CTV, and DOOH from the same prompt.
{
"mcpServers": {
"amap-data": {
"url": "https://mcp.amapdata.com",
"transport": "streamable-http"
}
}
}If your data has a location,
it's an audience.
Signals Agent turns it on.