
Pinterest Ads
com.getmcpadsPublished by getmcpads.comv2.1.1Updated Oct 26, 2026
Pinterest Ads MCP server: 29 read tools, 30 opt-in preview-first writes.
Overview
Local stdio MCP server that lets an assistant read Pinterest Ads reporting, targeting, catalogs and organic Pins, with 30 opt-in preview-first write tools.
- What you can do
- Check credentials and list reachable ad accounts, then read delivery metrics, run and validate reports, catalog and conversion reports, and specialized exports
- Inspect campaigns, ad groups, ads, creatives, targeting options, keyword intelligence, audiences and audience insights, delivery estimates and conversion setup
- Read catalog inventory and diagnostics, lead-form configuration, business assets, billing and orders, platform metadata and video upload status
- Read organic Pins, boards, Pin analytics and Pinterest Trends alongside paid data
- Create, update, rename and pause campaigns, ad groups, ads, promotions, boards, Pins and catalogs, and upload videos, when writes are enabled
- Read seven…
- When to use it
- Useful when you want an assistant to review or report on Pinterest advertising performance, research targeting and trends, or prepare campaign changes from a desktop MCP client, using your own Pinterest developer credentials instead of a hosted service.
- Requirements
- Runs locally over stdio via the npm package, needing Node.js 22.23.4, 24.22.1 or 26.12.1 or newer on those lines, and a desktop client that supports stdio MCP. Requires a Pinterest access token with the ads:read scope, plus PINTEREST_APP_ID, PINTEREST_APP_SECRET and PINTEREST_REFRESH_TOKEN for automatic renewal. PINTEREST_AD_ACCOUNT_IDS is recommended and will be required in 3.0.0. Network access to the Pinterest API is needed.
Installation
In SourceWeft
- Open Pinterest Ads in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Pinterest Ads MCP server
Connect the dots in your Pinterest campaigns.
Explore reporting, audiences, catalogs and native campaign operations from your MCP client.
[Release] [CI] [Smithery] [License: Apache 2.0] [Node]
Watch the film · What's new · Install · Tool reference · Try hosted getmcpads
[Watch the getmcpads film: every ad account in one conversation with your AI assistant]
The film shows hosted getmcpads with sample data. Its MCP Apps, from creative galleries and alerts to Google Sheets exports and bulk launches, belong to the hosted product. This repository provides the standalone native API tools.
29 read tools · 30 write tools, disabled by default.
Run locally with your own platform credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to the platform. For managed connections, including supported ChatGPT setups, use the hosted option.
What's new
v2.1.1: Zod 4 security update · October 26, 2026
- Update
zodto 4.6.7. Every Zod release before 4.6.6 is covered by the high-severity advisory GHSA-mrhx-c7xc-m3w5: validating an oversized constrained collection can exhaust memory, and no Zod 3 release carries the fix.npm audit --omit=devreports no vulnerability again. - Keep the Zod 3 validation behaviour. A parameter default is still validated and completed before use, so an omitted object must still supply its required fields.
- Keep each parameter's own description when the parameter is optional or has a default. Zod 4 stores a description on the wrapped schema only, so the shared fallback description could otherwise replace it.
- Tool names, parameters and descriptions published over MCP are unchanged.
server-card.jsonis regenerated with Zod 4's JSON Schema output, which spells some constraints differently.
Earlier releases
Source synchronization: SOURCE_SYNC.md.
Upgrade notes
Requires Node.js 22.23.4, 24.22.1 or 26.12.1, or a newer release of those lines. On an older runtime the server starts and writes a warning to stderr. CI covers Node 22, 24 and 26.
This release has no breaking change, and existing configurations keep working. Two changes are planned for 3.0.0, and the server announces each one on stderr at startup when it applies to your configuration:
PINTEREST_AD_ACCOUNT_IDSwill be required. Set it now to restrict the server to the listed ad accounts. Until then,PINTEREST_AD_ACCOUNT_IDremains a default account, not a restriction.PINTEREST_ENABLE_WRITESwill accept onlytrueto enable writes. Replace1,yesoronwithtrue.
The pinterest://attribution resource now names its default defaultAttribution. The former defaults key remains as an alias until 3.0.0.
Read the current tool schemas before reusing saved arguments. Writes remain optional and require explicit confirmation. Hosted creative integrations and MCP Apps UI are outside this release.
Install this release
This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned npx examples later in this document select the version currently available on npm.
Configure your MCP client to run node with the absolute path to dist/cli.js and the platform credentials documented below.
Prefer a managed connection? Use Pinterest Ads with hosted getmcpads. Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.
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.
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.
- Create an app in the Pinterest developer portal.
- Note the App ID and App secret.
- Run the OAuth flow while signed in to the account that can access your ad accounts.
Request
ads:read, andads:writeonly if you plan to enable writes. - 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):
PINTEREST_AD_ACCOUNT_IDS is optional and recommended. It restricts the server to the listed ad accounts, and version 3.0.0 will require it.
Restart Claude Desktop. Ask it: "list my Pinterest ad accounts".
Claude Code
Cursor
.cursor/mcp.json in your project, same shape as the Claude Desktop config above.
From source
Configuration
Either the access token, or the refresh trio. The server refuses to start with neither.
Without PINTEREST_AD_ACCOUNT_IDS, every ad account the token can access is reachable, and the server says so on stderr at startup.
Writes, and why they preview first
Write tools are disabled by default. Enable them with PINTEREST_ENABLE_WRITES=true, and
grant ads:write on top of ads:read.
When enabled, every write tool returns a preview and changes nothing:
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_campaignalways creates the campaignPAUSED. 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
Every tool is listed below. See server-card.json for complete parameter and output schemas.
29 read tools
30 write tools
Disabled by default. Calls preview unless explicitly confirmed. Check the configuration and exact schema before use.
7 resources
Security
- The token is never logged, at any log level, or written to disk.
- Credentials go to the Pinterest API only:
api.pinterest.com, orapi-sandbox.pinterest.comin sandbox mode. A test fails the build if another host appears in the source. PINTEREST_AD_ACCOUNT_IDSrestricts the reachable ad accounts. When it is set, a request that names another account is refused before it is sent, and discovery only returns listed accounts.- No fetch follows a redirect. Every outbound call sets
redirect: "error", so a redirect cannot forward your token to another host. A test fails the build if any fetch omits this. - Async report URLs are validated before being fetched. Pinterest returns a download URL on a host it chooses; that value is data from the API, not something to trust. HTTPS only, no private or loopback address, no redirect, and no credential attached.
- Video uploads go to the destination Pinterest returns, an Amazon S3 host checked before use, with signed form fields and never the access token. A video URL you pass gets the same checks as a report URL. Every request has a timeout and a response size limit.
- No telemetry. Outside the Pinterest API, the server only contacts the report and upload URLs that Pinterest returns, and a video URL that you pass to the upload tools.
Full policy, including how personal data is handled: SECURITY.md.
Looking for a managed, multi-platform version?
Try hosted Pinterest Ads if you want to use this source without operating a local server. getmcpads also connects advertising, Search Console and GA4 through one MCP URL. Source availability and plan limits are listed on the site; connecting an account is still required.
- Follow the Pinterest Ads connection guide.
- Select the account or property your assistant may read.
- Connect Claude, ChatGPT or Codex.
- Try a read-only review: “Review campaign performance using your selected ad account. State missing data and do not change anything.”
See the current hosted tool catalogue and pricing before choosing a paid plan. This Apache 2.0 adapter remains independently useful with your own credentials.
Contributing
Issues and pull requests are welcome. See CONTRIBUTING.md. Please read SECURITY.md before reporting anything security-related.
Licence
Apache License 2.0. See also NOTICE.
Pinterest is a trademark of Pinterest, Inc. This project is not affiliated with, endorsed by, or sponsored by Pinterest, Inc. It is an independent client of a public API.
MCP contracts and desktop bundle
Every tool declares read/write annotations, parameter descriptions and a structured output schema. Successful calls expose the payload as structuredContent.result; errors retain isError: true. The generated server card contains definitions only.
Run npm run bundle -- /path/to/output to build a .mcpb desktop bundle from the current catalog. Credentials are entered locally during installation. Write tools remain disabled unless explicitly enabled.
More from getmcpads
Meta Ads · Google Ads · Google Analytics 4 · Google Search Console · TikTok Ads · X Ads
Maintained by Emmanuel at getmcpads. Questions: [email protected].
Source: README.md at commit 77d783e
Tools
0Version history
4- v2.1.1LatestOct 26, 2026
- v2.1.0Oct 23, 2026
- v2.0.1Sep 23, 2026
- v1.0.2Sep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts