Zeotap CDP MCP Server
Enables Claude to interact with Zeotap's Customer Data Platform through natural language queries, allowing users to fetch audience data, check sync status, and manage destinations without needing API IDs.
README
Zeotap CDP MCP Server
An MCP (Model Context Protocol) server that connects Claude to Zeotap's Audience and Destination APIs. Clients can ask questions in plain English — Claude handles all the API calls and ID lookups internally.
What it does
- Fetches audiences, destinations, and sync status from Zeotap
- Compresses API responses by ~85% using tiktoken so Claude can handle more data
- Joins audience + destination data (replicating your SQL join via API calls)
- Accepts org names and audience names — clients never need to know IDs
Files
| File | Purpose |
|---|---|
server.py |
MCP server — handles tool calls, API requests, response compression |
tools.yaml |
Configuration — org IDs, tool definitions, LLM-friendly descriptions |
requirements.txt |
Python dependencies |
Skills.md |
Full API blueprint and tool design reference |
.env |
Bearer token (not committed — update every hour) |
Setup
1. Install dependencies
python3 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -r requirements.txt
2. Get your bearer token
- Log into unity.zeotap.com
- Open DevTools → Network tab → click any request
- Copy the
Authorization: Bearer eyJ...value (just theeyJ...part)
3. Set the token
echo 'ZEOTAP_TOKEN=your-token-here' > .env
⚠️ Tokens expire every 1 hour. Repeat step 2–3 when you get a 401 error.
4. Run with MCP Inspector (for testing)
npx @modelcontextprotocol/inspector .venv/bin/python server.py
Open the URL printed in the terminal.
Adding a new org
Each org needs two IDs. Find them from DevTools when browsing that org in the Zeotap app:
| ID | Where to find | Used for |
|---|---|---|
Numeric ID (e.g. 1918) |
URL: /audiences/orgs/1918/... |
Audience APIs |
UUID (e.g. efc1d9ad-...) |
Network tab: /channelSettings/...?orgId=efc1... |
Destination name lookup |
Update tools.yaml:
audience_org_id: 1918
org_uuid: "efc1d9ad-8bb2-48a2-8c84-46f2e9f2b9b4"
org_name: "Your Org Name"
Tools
| Tool | Description | Required params |
|---|---|---|
get_org_overview |
Total audiences, status breakdown, top 5 by size | none |
search_audiences |
Find audiences by name or status | optional: query, status |
get_audience_full |
Full details + filters + destinations for one audience | audience_name or audience_id |
get_org_full_report |
All audiences joined with their destinations and sync status | none |
list_all_destinations |
All destinations configured in the org | none (needs UUID) |
get_destination_full |
Details for one destination | destination_name or destination_id (needs UUID) |
list_orgs |
Lists known client orgs with their IDs | none |
Example Claude queries
Once connected to Claude Desktop, clients can ask:
| Question | Tool used |
|---|---|
| "Give me a summary of our audiences" | get_org_overview |
| "List all active audiences" | search_audiences |
| "Tell me about the Loyalty Program audience" | get_audience_full |
| "Which audiences are failing to sync?" | get_org_full_report |
| "What platforms is our CDP syncing to?" | get_org_full_report |
| "What destinations do we have?" | list_all_destinations |
Connect to Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"zeotap-cdp": {
"command": "/Users/megha/Documents/MCP1/.venv/bin/python",
"args": ["/Users/megha/Documents/MCP1/server.py"],
"env": {
"ZEOTAP_TOKEN": "your-token-here"
}
}
}
}
On Mac, the config file is at:
~/Library/Application Support/Claude/claude_desktop_config.json
Restart Claude Desktop after updating the config.
Audience ↔ Destination Join
The get_org_full_report tool replicates this SQL join via two API calls:
SELECT fpa.name, fpa.status, csw.status, ip.int_partner_name
FROM public_audience_destinations pad
JOIN public_first_party_audience fpa ON pad.first_party_audience_id = fpa.id
JOIN public_channel_service_workflow csw ON pad.latest_channel_service_workflow_id = csw.id
JOIN public_integration_partner ip ON pad.channel_id = ip.int_id
WHERE fpa.org_id = 1918
| SQL field | API source |
|---|---|
fpa.name, fpa.status |
audienceSummaries response |
csw.status, csw.status_detail |
destinationsSummary.status + statusDetail.message |
ip.int_partner_name |
channelSettings → integrationPartnerName (joined via channelId = intId) |
channelSegmentId |
destinationsSummary.integrationDetail.channelSegmentId |
Token reduction
| Tool | Raw tokens | Minified | Reduction |
|---|---|---|---|
get_org_overview (100 audiences) |
~15,000 | ~800 | ~95% |
search_audiences (20 results) |
~8,000 | ~600 | ~93% |
get_audience_full |
~3,000 | ~300 | ~90% |
get_org_full_report |
~20,000 | ~2,000 | ~90% |
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。