Peachblue

io.peachbluePublished by peachblue.ioOfficial publisherv1.0.0Updated Oct 30, 2026

Creative intelligence for Meta, TikTok, Google Ads and Amazon DSP, in Claude and other MCP clients.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Peachblue is a remote MCP server that brings creative intelligence for Meta, TikTok, Google Ads and Amazon DSP into Claude and other MCP clients.

What you can do
  • The manifest lists no tools, so capabilities are known only from the short description.
  • It is positioned as creative intelligence for advertising platforms: Meta, TikTok, Google Ads and Amazon DSP.
  • It is meant to be used from Claude and other MCP clients through a remote endpoint.
When to use it
Consider it if you work with ad creative across Meta, TikTok, Google Ads or Amazon DSP and want that context available to an assistant inside an MCP client. The description gives no detail on specific reports or actions, so check the vendor's documentation before relying on it.
Requirements
A remote MCP endpoint at app.peachblue.io over streamable HTTP. OAuth authentication is required, so a Peachblue account is presumably needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your Peachblue account; review the scopes requested during authorization. The description does not state whether the server reads or changes advertising data, so confirm before connecting accounts with live ad spend.

Installation

In SourceWeft

  1. Open Peachblue in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.peachblue%2Fpeachblue/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "peachblue": {
      "type": "http",
      "url": "https://app.peachblue.io/api/mcp/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.