# @cesteral/pinterest-mcp

Pinterest Ads MCP Server - Campaign entity management and reporting via Pinterest Ads API v5

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 1.3.0
- **Author:** Unknown
- **License:** Apache-2.0
- **npm:** @cesteral/pinterest-mcp
- **Endpoints:** streamable-http https://{host}/pinterest-mcp/mcp
- **Source:** https://github.com/cesteral/mcp-open-advertising
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** warnings
- **Scanned:** 2026-08-29T21:42:37.559Z
- **Version scanned:** 1.3.0
- **CVEs:** none found by OSV at scan time

## Tools

19 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `pinterest_bulk_operations_workflow` — Guide for performing bulk create, update, and status operations on Pinterest Ads entities
- `adAccountId` — Pinterest Advertiser ID
- `entityType` — Entity type to operate on (campaign, adGroup, ad)
- `pinterest_campaign_setup_workflow` — Step-by-step guide for creating a complete Pinterest Ads campaign structure (Campaign > Ad Group > Ad)
- `objective` — Campaign objective (e.g., AWARENESS, CONSIDERATION, VIDEO_VIEW, CATALOG_SALES, CONVERSIONS, APP_INSTALL, SHOPPING)
- `creative_upload_workflow` — Step-by-step guide for uploading video creatives and creating Pinterest Ads. Image creatives reference a hosted image URL directly rather than uploading a file.
- `cross_platform_campaign_setup` — Guide for setting up a coordinated multi-platform campaign across DV360 (dv360-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), Meta Ads (meta-mcp), Linke
- `totalBudget` — Total campaign budget across all platforms (e.g., '50000' for $50,000)
- `cross_platform_performance_comparison` — Guide for comparing campaign performance across DV360 (via dbm-mcp), The Trade Desk (ttd-mcp), Google Ads (gads-mcp), and Meta Ads (meta-mcp). Normalizes metric
- `dateRange` — Date range for comparison (e.g., LAST_7_DAYS, LAST_30_DAYS, or custom YYYY-MM-DD format)
- `pinterest_entity_duplication_workflow` — Step-by-step guide for duplicating Pinterest Ads campaigns, ad groups, and ads using pinterest_duplicate_entity — covers A/B testing, scaling, and common patter
- `entityId` — Numeric ID of the entity to duplicate
- `pinterest_entity_update_workflow` — Step-by-step guide for safely updating Pinterest Ads entities — covers field updates vs status changes (separate endpoints), budget values in account currency, 
- `pinterest_reporting_workflow` — Guide for submitting and retrieving Pinterest Ads async reports with dimensions, metrics, and breakdowns
- `reportLevel` — Report level: AUCTION, RESERVATION (default: AUCTION)
- `pinterest_targeting_discovery_workflow` — Step-by-step guide for researching Pinterest audiences: search interest categories, browse behaviors, build targeting configs, and estimate audience size before
- `goal` — Research goal: 'search' (find by keyword), 'browse' (explore options), or 'build' (assemble targeting). Default: search
- `pinterest_tool_schema_exploration` — Guide for discovering and understanding Pinterest MCP tools, resources, and schemas
- `pinterest_troubleshoot_entity` — Diagnostic workflow for troubleshooting Pinterest Ads entity issues

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"pinterest\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@cesteral/pinterest-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive blast radius — mutates data; runs locally and hosted.
- Floor 34, ceiling 58 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40cesteral%2Fpinterest-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40cesteral%2Fpinterest-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40cesteral%2Fpinterest-mcp
- HTML page: https://forgeregistry.com/registry/%40cesteral%2Fpinterest-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.