MCP
MCP Usage Policy
How Pinterest developer guidelines apply to AI-assisted publishing via PinBridge, and which workflows are compliant.
Overview
PinBridge gives AI assistants direct access to Pinterest publishing. Pinterest's own developer guidelines define how that publishing must be initiated — and PinBridge operates fully within those rules. This page explains what Pinterest requires, and how PinBridge MCP workflows stay compliant.
What You Will Learn
- What Pinterest's developer guidelines require for AI-assisted publishing.
- Why per-pin human intent is part of the Pinterest platform policy.
- Which PinBridge MCP workflows are compliant.
- Which automation patterns fall outside Pinterest's permitted use.
Implementation Checklist
- Review each pin individually before calling a write tool — Pinterest requires explicit per-pin intent.
- Avoid fully autonomous pipelines that bulk-publish without reviewing each item.
- When scheduling, confirm the pin, board, and time are intentionally chosen before the call is made.
- AI-assisted drafting and editing is fine — the per-pin requirement applies at the moment of publishing.
Important Resources
Official package and source links for direct installation and version tracking.
Deep Dive
What Pinterest's guidelines require
Pinterest's Developer Guidelines state that end users must specifically consider each action before it is taken. For publishing, this means:
- "If your app allows end users to schedule Pin publishing, the end user must choose each Pin to be published." — Pinterest Developer Guidelines.
- A single approval for a batch ("publish all of these") does not satisfy the per-pin intent requirement.
- "Specifically" is the operative word — each pin must be individually and intentionally chosen.
Compliant MCP workflows
PinBridge MCP tools are fully compliant when a human reviews and approves each pin before the publish call is made:
- Using Claude Desktop to draft a pin, review it, then publish — compliant.
- Asking an AI assistant to suggest a schedule time for a specific pin the user selected — compliant.
- AI-generated captions reviewed and approved by the user before publishing — compliant.
- Reviewing each item in a list individually and publishing one at a time — compliant.
Patterns outside Pinterest's permitted use
Some automation patterns that are technically possible via MCP tools fall outside what Pinterest permits on its platform:
- Fully autonomous agents that generate content, select boards, and publish without any human review.
- Batch flows where the user approves once and the AI publishes multiple pins without per-item confirmation.
- Content calendars generated and queued entirely by AI without per-pin sign-off.
- Bulk republishing or rescheduling of existing pins without per-pin review.
How PinBridge handles this
PinBridge operates as an authorised Pinterest API partner and applies Pinterest's guidelines to all publishing activity. The MCP server exposes the same Pinterest publishing pipeline as the REST API — per-pin intent is a Pinterest platform requirement that applies to all publishing methods, including AI-assisted ones. Pinterest actively reviews third-party integrations and distinguishes between tools that "facilitate" publishing (allowed) and tools that "take actions without specific knowledge and consent" (not allowed).