UK content hub
Workflow guide ยท MCP
Index a UK audience by postcode district in under a minute
Step-by-step workflow for indexing any AMAP UK audience to postcode-district resolution using the MCP server.
22 April 2026 5 min read
MCPIndexingPostcode
This workflow takes a media planner from a blank Claude or Cursor session to a ranked, postcode-level audience index ready to brief into TTD, DV360 or ITVX.
What you'll achieve
- A ranked postcode-district list for any AMAP UK audience.
- Composition + index values per postcode, ready to copy into a media plan.
- An exportable JSON payload you can hand to activation.
Prerequisites
- An MCP-compatible client (Claude Desktop, Cursor, ChatGPT desktop).
- The AMAP UK MCP block in your client config.
- 1
Connect the AMAP UK MCP server
Drop the JSON block into your client config. No SDK or auth โ the MCP endpoint is public for evaluation.
claude_desktop_config.json{ "mcpServers": { "amap-data-uk": { "url": "https://mcp.amapdata.com", "transport": "streamable-http" } } } - 2
Ask for an audience index
Use natural language. The MCP server resolves the audience to AMAP's UK taxonomy and returns postcode-district results.
Index pet owners โ London ITV regionIndex pet owners across the London ITV region at the postcode-district level โ return top 5 with composition and index.
response{ "audience": "pet_owners", "geo_level": "postcode_district", "market": "London ITV region", "results": [ { "postcode": "SW1A", "composition": 0.41, "index": 184 }, { "postcode": "W1K", "composition": 0.39, "index": 176 }, { "postcode": "NW3", "composition": 0.38, "index": 172 } ], "source": "AMAP ยท Geograph UK", "privacy": "aggregated_no_pii" } - 3
Hand off to activation
Pipe the same payload into a TTD, DV360, ITVX or Channel 4 brief. AMAP keeps the geographic resolution end-to-end so reporting matches planning.
Want this wired up for your team?
Book a UK walkthrough