pinterest-ads-mcp-server

An open-source Model Context Protocol server for the Pinterest Ads API. It lets Claude, ChatGPT, Cursor or any MCP client read and analyse your Pinterest advertising data, and change it if you choose to.

You run it. Your token stays on your machine. Nothing is proxied through a third party.

npx -y @getmcpads/pinterest-ads-mcp-server

Also listed in the MCP Registry as com.getmcpads/pinterest-ads, so clients that read the registry can install it by name.

Prefer not to run it yourself? getmcpads.com is the hosted version of this server, with Pinterest Ads alongside Meta Ads, Google Ads, TikTok Ads, Google Analytics and Search Console behind a single endpoint, hosted OAuth, and cross-platform reporting. Same tools, same safety model, no setup.

What you get

Raw column names, on purpose

Pinterest names its reporting columns in its own way, and this server accepts those names directly rather than inventing friendly aliases on top. A column that exists in the API works here; one that does not fails immediately rather than being silently translated into something else.

pinterest://reporting-columns lists what is available, and pinterest_validate_report checks a request before it runs.

How this compares to Pinterest's own MCP server

Pinterest shipped an official MCP server in June 2026, with authentication handled by Pinterest's own systems. It launched read-only: an agent can pull performance data and account context, but cannot change a budget, pause a campaign or edit a bid.

Choose Pinterest's for the least setup, if reporting is all you need. Choose this one if you want your data to stay on your infrastructure, want to audit or extend what the model can do, or want guarded writes rather than none. Choose getmcpads.com if you want this server's capabilities without running it, or you need more than one ad platform in the same conversation.

Privacy, built into what the tools return

Two protections, and they work differently.

Lead records are never exposed. pinterest_get_lead_assets returns lead form and subscription configuration, but never the lead export itself, because those rows carry personal information submitted by end users. This is an exclusion, not a redaction: the data does not leave Pinterest through this server at all.

Business member identifiers are redacted by default. Member IDs, email addresses and usernames are replaced before they reach the model when you read members, asset members or invites. includePersonalIdentifiers: true returns the raw values and defaults to false. These are your colleagues' addresses, so the default is the safe one.

Getting a token

You need a Pinterest access token with the ads:read scope.

1. Create an app in the Pinterest developer portal.
2. Note the App ID and App secret.
3. Run the OAuth flow while signed in to the account that can access your ad accounts. Request ads:read, and ads:write only if you plan to enable writes.
4. Keep the access token, and the refresh token if you want the server to renew it.

📖 Pinterest API authentication

You can run with just PINTEREST_ACCESS_TOKEN, but it expires. Supplying PINTEREST_REFRESH_TOKEN, PINTEREST_APP_ID and PINTEREST_APP_SECRET together lets the server renew the token itself, which is what you want for daily use.

Run pinterest_health_check as your first call. It verifies the token and lists the ad accounts you can reach, without printing the token.

Setup

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "pinterest-ads": {
      "command": "npx",
      "args": ["-y", "@getmcpads/pinterest-ads-mcp-server"],
      "env": {
        "PINTEREST_ACCESS_TOKEN": "your-token-here"
      }
    }
  }
}

Restart Claude Desktop. Ask it: "list my Pinterest ad accounts".

Claude Code

claude mcp add pinterest-ads --env PINTEREST_ACCESS_TOKEN=your-token -- npx -y @getmcpads/pinterest-ads-mcp-server

Cursor

.cursor/mcp.json in your project, same shape as the Claude Desktop config above.

From source

git clone https://github.com/getmcpads-com/pinterest-ads-mcp-server.git
cd pinterest-ads-mcp-server
npm install && npm run build
cp .env.example .env   # then fill in your credentials
npm start

Configuration

Either the access token, or the refresh trio. The server refuses to start with neither.

npm run doctor

Writes, and why they preview first

Write tools are disabled by default. Enable them with PINTEREST_ENABLE_WRITES=1, and grant ads:write on top of ads:read.

When enabled, every write tool returns a preview and changes nothing:

// pinterest_update_adgroup_budget { adAccountId: "549…", adGroupId: "268…", dailyBudget: 50 }
{
  "applied": false,
  "action": "pinterest_update_adgroup_budget",
  "change": { "adAccount": "549…", "adGroup": "268…",
              "field": "budget_in_micro_currency", "amount": 50,
              "inMicroCurrency": 50000000 },
  "message": "Preview only, nothing was changed. Repeat the same call with confirm: true to apply this change to the live account."
}

Only a second call carrying confirm: true touches the live account.

This is deliberate. An assistant composes these calls, and it can pick the wrong ad account, the wrong campaign, or the wrong order of magnitude on a budget. A mandatory preview makes the mistake visible before it costs money, and gives a human the stopping point the protocol does not guarantee on its own.

Two further guardrails:

• pinterest_create_campaign always creates the campaign PAUSED. There is no option to create it active.
• Amounts are converted to micro units for you. Pinterest holds money in millionths, so 12.50 in the account currency is 12500000. The preview shows both, so a factor-of-a-million mistake is visible before it applies. A daily and a lifetime budget sent together are refused rather than silently resolved.

Tools