The Trade Desk MCP Server
What it does
The Trade Desk management — CRUD, GraphQL, bulk ops, and async reports
- Connects 电脑或云端
- Account or key No key needed
- Category 开发者工具
安装
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 你的提问会经过开发者的服务器({host}) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
地址中有 {…} 部分,需要先改成你自己的 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称The Trade Desk MCP ServerRemote MCP server URL · 地址https://{host}/ttd-mcp/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsThe Trade Desk MCP Server
试一试
用 The Trade Desk MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 The Trade Desk MCP Server,或回答中出现 The Trade Desk MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页 · 地址中有 {…} 部分,需要先改成你自己的
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称The Trade Desk MCP ServerConnection · 地址https://{host}/ttd-mcp/mcp在聊天中选择 The Trade Desk MCP Server
开启新聊天,输入前先从插件列表中选择 The Trade Desk MCP Server
试一试
用 The Trade Desk MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 The Trade Desk MCP Server,或回答中出现 The Trade Desk MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code,但需要先准备
地址中有 {…} 部分,需要先改成你自己的
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user ttd 'https://{host}/ttd-mcp/mcp'在 Claude Code 中输入 /mcp
应能看到 The Trade Desk MCP Server 在列表中并显示已连接
试一试
用 The Trade Desk MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 The Trade Desk MCP Server,或回答中出现 The Trade Desk MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
地址中有 {…} 部分,需要先改成你自己的
打开 Cursor 的 MCP 设置文件
~/.cursor/mcp.json
粘贴这些设置,填写空着的值并保存
{ "mcpServers": { "ttd": { "url": "https://{host}/ttd-mcp/mcp" } } }在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 The Trade Desk MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 The Trade Desk MCP Server,或回答中出现 The Trade Desk MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
地址中有 {…} 部分,需要先改成你自己的
打开 VS Code 的 MCP 设置文件
MCP: Open User Configuration
粘贴这些设置,填写空着的值并保存
{ "servers": { "ttd": { "type": "http", "url": "https://{host}/ttd-mcp/mcp" } } }在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 The Trade Desk MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 The Trade Desk MCP Server,或回答中出现 The Trade Desk MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://{host}/ttd-mcp/mcpJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user ttd 'https://{host}/ttd-mcp/mcp'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ttd": {
"url": "https://{host}/ttd-mcp/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"ttd": {
"type": "http",
"url": "https://{host}/ttd-mcp/mcp"
}
}
}安装在电脑上
Claude Code
claude mcp add --scope user ttd -- npx -y @cesteral/ttd-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"ttd": {
"command": "npx",
"args": [
"-y",
"@cesteral/ttd-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ttd": {
"command": "npx",
"args": [
"-y",
"@cesteral/ttd-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"ttd": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cesteral/ttd-mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
这个地址需要填入你自己的值,所以我们无法替你读取工具列表。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月15日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 cesteral 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于昨天
- ✓ 通过
有许可证
使用 Apache-2.0
- – 不适用
端点有响应
这个地址需要填入你自己的账户信息,所以我们无法替你检查
- – 不适用
使用 OAuth 登录
这个地址需要填入你自己的账户信息,所以我们无法替你检查
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 5899 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5899 个服务器的 98% 更新
- 基础检查结果等于或优于此分类中其他 5899 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
The Trade Desk MCP Server 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
两种方式都可以:安装在你的电脑上,或者连接云端版本。
它还在维护吗?
GitHub 仓库最后更新于昨天,最新版本(1.4.0)于昨天进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同类别的其他选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Cesteral MCP Servers
Self-hostable MCP connectors for major advertising platforms.
Use this repo when you want transparent platform integrations, local experimentation, and infrastructure you control. Use Cesteral Intelligence when your team needs approvals before spend commits, credential brokering, auditability, and cross-platform execution from one governed environment.
Try Meta Ads MCP locally (~10 min) | Compare OSS vs Cesteral Intelligence | Book a workflow demo
Two Ways to Use This
This repo is an open connector layer, not the full product.
- Self-host a connector for transparency and direct control of your credentials, infrastructure, and platform access.
- Use Cesteral Intelligence when the workflow needs governed writes, team approvals, credential brokering, auditability, and cross-platform coordination — see when you need it below.
Flagship Connectors
Google Ads MCP
Campaign writes, GAQL reporting, bid adjustments, previews, and validation via Google Ads REST API v26.
Package docs | Use with Cesteral Intelligence
Meta Ads MCP
Campaign writes, insights, targeting discovery, delivery estimates, previews, and bulk operations via Meta Marketing API v26.0.
Package docs | Use with Cesteral Intelligence
DV360 MCP
Campaign writes, targeting, custom bidding, previews, uploads, and schema-driven validation via DV360 API v4.
Package docs | Use with Cesteral Intelligence
When You Need Cesteral Intelligence
The OSS connectors give you per-server tool execution + audit logs. Cesteral Intelligence layers governance and orchestration on top:
- Credential brokering -- keep platform secrets out of local operator workflows
- Approval workflows -- require human review before destructive or high-spend changes
- Aggregated audit -- unified, cross-server activity feed with provenance, tied to operator identity
- Cross-platform orchestration -- coordinate governed execution across multiple connectors
- Team operations -- shared workflows, tenant isolation, and operator visibility
Compare OSS connectors vs Cesteral Intelligence
The Full Fleet
| Server | Platform | Tools | Auth |
|---|---|---|---|
| gads-mcp | Google Ads REST API v26 | 19 | OAuth2 refresh token |
| meta-mcp | Meta Marketing API v26.0 | 27 | Bearer token |
| dv360-mcp | DV360 API v4 | 26 | Google OAuth2 / service account |
| ttd-mcp | The Trade Desk REST + GraphQL API | 46 | User token (TTD-Auth header) |
| linkedin-mcp | LinkedIn Marketing API (202610) | 23 | Bearer token |
| tiktok-mcp | TikTok Marketing API v1.3 | 29 | Bearer token + advertiser ID |
| cm360-mcp | CM360 API v5 | 22 | Google OAuth2 |
| sa360-mcp | SA360 Reporting API v0 + DS v2 | 18 | OAuth2 refresh token |
| pinterest-mcp | Pinterest Ads API v5 | 24 | Bearer token |
| snapchat-mcp | Snapchat Ads API v1 | 25 | Bearer token |
| amazon-dsp-mcp | Amazon Ads Unified API (DSP) | 28 | Bearer token |
| msads-mcp | Microsoft Advertising API v13 | 28 | Access token + developer token |
| dbm-mcp | Bid Manager API v2 | 7 | Google OAuth2 |
Thirteen servers, 290+ tools. Tool counts are the live registered total per server, including the *_search_tools discovery tool where present.
What Every Server Ships
Every server speaks MCP protocol revisions 2025-03-26, 2025-06-18 and 2025-11-25, the ones @modelcontextprotocol/sdk 1.31.0 implements; the Streamable HTTP transport rejects any other MCP-Protocol-Version. The current revision, 2026-07-28, is not supported yet (#242).
That is not the whole spec. In the MCP conformance suite (@modelcontextprotocol/conformance 0.1.16) every server passes 18 of the 30 active server scenarios — initialize, ping, logging level and log notifications, tool list and call, elicitation (form, defaults and enums), resource list, read and templates, prompt list and get, concurrent SSE streams, DNS-rebinding protection — and conformance/expected-failures.yaml gives the reason for each of the other 12. Not implemented: completions, resource subscriptions, sampling, progress notifications, image / audio / embedded-resource content, and SSE stream resumption. Elicitation requests (including the destructive-action confirmations below) and log notifications are sent on the calling tools/call request's response stream, so a client does not need the optional GET stream to receive them. A server bound to a loopback address (the default outside NODE_ENV=production) accepts only loopback Host and Origin headers on /mcp; a server on any other address checks Host only when MCP_ALLOWED_HOSTS is set.
Beyond raw tool calls, every server ships:
- MCP Prompts — on-demand, multi-step workflow guidance (campaign launch, reporting, troubleshooting) so agents don't have to rediscover each platform's sequencing. Present on all 13 servers.
- MCP Resources — structured, addressable context (schemas, field catalogs, examples, enums) fetched on demand instead of bloating every tool schema. Present on all 13 servers. DV360 uses these to keep its >1 MB discriminated unions off the wire (
entity-schema://,entity-fields://,entity-examples://). - Tool discovery — a
_search_toolstool that lets an agent search the server's own catalog by intent instead of paging the full list. On 10 of the 13 servers (all except the smallgads-mcpandsa360-mcp/ reporting-onlydbm-mcp). - Server discovery cards — SEP-2127 metadata at
/.well-known/mcp/server-card.json(name, version, transports, auth modes, capabilities) on every server, in every auth mode. - OAuth resource discovery — in
jwtauth mode, the RFC 9728 endpoint at/.well-known/oauth-protected-resource. - Report CSV spill — large report bodies spill to GCS behind a signed URL so responses stay bounded. On the six reporting-heavy servers:
ttd-mcp,tiktok-mcp,snapchat-mcp,amazon-dsp-mcp,pinterest-mcp,msads-mcp.
| Server | Discovery | Prompts | Resources | CSV spill |
|---|---|---|---|---|
| gads-mcp | ✅ | ✅ | ||
| meta-mcp | ✅ | ✅ | ✅ | |
| dv360-mcp | ✅ | ✅ | ✅ | |
| ttd-mcp | ✅ | ✅ | ✅ | ✅ |
| linkedin-mcp | ✅ | ✅ | ✅ | |
| tiktok-mcp | ✅ | ✅ | ✅ | ✅ |
| cm360-mcp | ✅ | ✅ | ✅ | |
| sa360-mcp | ✅ | ✅ | ||
| pinterest-mcp | ✅ | ✅ | ✅ | ✅ |
| snapchat-mcp | ✅ | ✅ | ✅ | ✅ |
| amazon-dsp-mcp | ✅ | ✅ | ✅ | ✅ |
| msads-mcp | ✅ | ✅ | ✅ | ✅ |
| dbm-mcp | ✅ | ✅ |
Built for Production
Self-hosting an AI agent that touches live ad spend is a trust problem first and a capability problem second. Two things make this fleet shippable to production without hand-rolling guardrails:
- Audit-grade observability. Every tool call is captured as append-only JSONL. Failures additionally capture the full upstream HTTP trail — every request, every retry, every response — with secrets redacted at the source. Query it directly in BigQuery for hosted deployments, or pipe stdout to your existing log stack for self-host. Read the observability guide.
- Destructive-action elicitation gates. 51 destructive tools across the twelve write-capable servers (
dbm-mcpis reporting-only) prompt the user before deletes, bulk status changes, bid adjustments, budget changes, conversion uploads, and async Workflows batch jobs. Stdio and clients without elicitation support fall back to a documented non-interactive contract. Bulk mutations under 10 items skip the prompt unless they touch a sensitive field (status / budget / bid). - Verifiable release provenance. Governed tools carry a canonical SHA-256
definitionHash(from@cesteral/contract-hash) emitted into a per-packagecesteral-manifest.json. Tagged releases publish to npm with build provenance, signing the manifest transitively inside the tarball, so a downstream