Bring your ad performance into Claude.

Copy your connection URL from Settings, MCP tab, add it to Claude as a custom connector, and sign in with your Peachblue account. Nothing needs installing.

Claude Desktop and claude.ai

1. Open Customize, then Connectors, and click the plus button.
2. Choose Add custom connector, name it Peachblue, and paste your connection URL.
3. Complete the Peachblue sign-in, then ask "what were my top 5 creatives by composite score last month" to check it works.

Custom connectors work on every Claude plan, and the free plan allows one. On Team and Enterprise an owner adds the connector first, then each member connects with their own Peachblue login. Claude asks before it calls a tool unless you choose to always allow it, and you can switch tools off for a conversation in its Search and tools menu.

Claude Code

One command, then sign in when Claude Code first uses it:

claude mcp add --transport http peachblue <your-connection-url>

Other MCP clients

Any client that supports remote MCP connectors connects the same way. The server speaks Streamable HTTP with an OAuth sign-in, so there is never an API key to paste. The setup docs carry the latest steps.

Each of the 23 tools answers one kind of question, and Claude picks the tools for you. Every one is read-only, returns its data with the time window it covers, and runs on the same engine as the app, so a number in Claude matches the number on the Performance page.

Pacing and supplier answers need Amazon DSP connected, and the roster comparison an agency workspace. Arguments and return fields are in the MCP tool reference.

Real data, already worked out. Four questions asked of the sample account, Fizzli, the fictional drinks brand behind every product picture on this site. Claude writes the sentences; Peachblue supplies the numbers, the ranking, and the verdicts.

In clients that support MCP Apps, creative results also arrive as inline cards with thumbnails and scores, like the one at the top of this page.

Yes, four. In clients that support MCP prompts, Peachblue offers them as starting points: each one calls the right tools in order and asks for a structured write-up.

• Weekly creative review. Top creatives to scale, underperformers to pause, the best headlines by ROAS, and what Reddit is saying, for the last 7, 14, or 30 days.
• Generate creative brief.A brief built from your winners' tags, audiences, and copy themes, with what to avoid.
• Cross-platform audit. Spend share and scores by platform, the best creatives on each, and the creatives winning on more than one.
• Competitive landscape. Your Brand Intel from Reddit beside what is working in your account, to find the angles the market wants and your ads miss.

It sees your workspace's synced ad data and Brand Intel, and it can change nothing. Every tool is read-only, and Peachblue itself only ever reads from Meta, TikTok, Google Ads, and Amazon DSP, so no step between Claude and your ad accounts creates, edits, or pauses anything.

• A sign-in, not a key. You approve access with your Peachblue account over OAuth. There is no API key to create, share, or leak.
• Scoped like the app. Each person connects with their own login and sees only their workspace, and agency calls stay inside the client you name. Disconnect from the same Settings tab and access ends at once.
• Your data stays yours. It is never shared across workspaces, never sold, and never used to train models for other customers. See data access and deletion.

• Plan. MCP is on Pro and up; Amazon DSP data needs Scale.
• Platforms. Answers cover what Peachblue syncs: Meta, TikTok, Google Ads (Search, Display, and Video), and Amazon DSP. Performance Max, LinkedIn, Pinterest, Snapchat, and YouTube as a channel of its own are not covered.
• Read, not act. Peachblue cannot pause an ad or move a budget; that stays in the ad platform or its own connector.
• Freshness. Data is as current as the last daily sync.
• Fair use. A rate limit per workspace guards the server, and normal analysis never reaches it. Questions use no credits: credits pay for creative analysis.

Agency workspaces get the same server, with every call scoped per client. Name a client in the question ("how are Fizzli's DSP flights pacing?") and the tools answer for that client alone; leave the name out and they answer across the roster. Clients are your Amazon DSP advertisers and Meta ad accounts.

• The roster in one table.One row per client with spend, CPM, CTR, results, and CPA, so "which client is the problem" is one question.
• Pacing and suppliers per client. Every DSP flight against its budget and blended CPM, and spend supplier by supplier.

Agency workspaces are on the Agency plan, priced to your client roster. The Amazon DSP page has the pacing and reporting side.

A platform's own server reaches one platform's raw account, and most of them can act on it. Peachblue's reaches four platforms' data with the analysis already done, and cannot act. They work well together: the platform server acts, and Peachblue tells Claude what deserves acting on.

None of the platform servers documents a tool that tags a creative's hook, format, or angle, or recognizes the same asset across ads and platforms; Peachblue does both at sync. For data connectors and other creative analytics servers, see the best MCP servers for ad data.