Connect PinBridge to your AI assistant

PinBridge runs a hosted MCP server for Pinterest. In Claude, add it from the connector directory and sign in, with no API key to copy. Every other MCP client connects with one API key. Either way it takes about a minute.

• Endpoint: https://mcp.pinbridge.io
• Claude: listed in Claude’s connector directory, sign in with your PinBridge account (OAuth)
• Other clients: send Authorization: Bearer <api_key>

What you need

• A PinBridge account. Create one for free. The Playground plan is enough to try the whole flow.
• A connected Pinterest account. Connect it once from the PinBridge dashboard: open Pinterest Accounts and approve access on Pinterest. It takes about 30 seconds. PinBridge stores and refreshes the tokens, so your assistant never touches Pinterest credentials, and it can only publish to accounts linked to your workspace.
• An MCP client. Claude on the web or in the desktop app, Claude Code, Codex, Cursor, Windsurf, or any assistant built on the Model Context Protocol.

Connect Claude from the connector directory

1. Open PinBridge in Claude’s connector directory. You can also find it in Claude: open Customize, then Connectors, and search for PinBridge.
2. Click Connect to Claude.
3. Sign in to PinBridge with your email and password, or click Continue with Google. New to PinBridge? The sign-in page links to the plans so you can create an account first.
4. Choose the workspace Claude may use and click Authorize.

Claude is now connected. The connector’s page in Claude lists every PinBridge tool, and you can decide for each one whether Claude asks you before using it.

The connection shows up in your PinBridge dashboard under API Keys, labelled Agent with the assistant’s name. Revoke it there to disconnect Claude. Connecting again replaces the previous connection’s key.

PinBridge is listed as a community connector. If Connect to Claude isn’t available in your Claude organization, ask an admin to allow it, or add https://mcp.pinbridge.io as a custom connector instead. It uses the same sign-in.

Connect other clients with an API key

1. Get your API key

Log into the PinBridge dashboard, open API Keys, create a key, and copy it. It starts with pb_ followed by 64 hexadecimal characters:

pb_your_api_key

Keep this key private. Anyone who has it can publish to your connected Pinterest accounts. Store it in a secrets manager, never in client-side code or source control. See Authentication for creating and revoking keys.

2. Add PinBridge to your client

Every client connects to the same endpoint, https://mcp.pinbridge.io (streamable HTTP), with your key in an Authorization: Bearer header.

Claude Code. Add the server from your terminal in one command:

claude mcp add pinbridge --transport http https://mcp.pinbridge.io \
  --header "Authorization: Bearer pb_your_api_key"

To skip the key, add the server without the header, then run /mcp inside Claude Code, pick pinbridge and choose Authenticate. You sign in to PinBridge in the browser, as in the Claude steps above.

Codex, Windsurf, Cursor & other clients. Add a new MCP server in your client’s settings using these values, then restart the client:

# Transport  streamable HTTP
# URL        https://mcp.pinbridge.io
# Header     Authorization: Bearer pb_your_api_key

Replace pb_your_api_key with your real key everywhere, and make sure there are no stray spaces around it.

Verify the connection

Open a new conversation and ask your assistant:

List my Pinterest accounts

It should return your connected account details. You can also ask it to run server_info, which reports the server version, the PinBridge API it targets, and whether write (publishing) tools are enabled.

Publish your first pin

In a new conversation, describe the pin:

Publish a pin to my Home Ideas board titled
"My first AI pin" using this image:
https://images.unsplash.com/photo-1506905925346-21bda4d32df4?w=800

Your assistant calls the create_pin tool, PinBridge queues the publish with per-account rate handling and retries, and the pin appears on Pinterest within seconds.

What your assistant can do

The hosted server exposes 34 tools: 16 read and 18 write, all scoped to your workspace.

• Publish & schedule. Publish a pin now with create_pin, or several at once with create_pins_batch. Queue one for later with create_schedule, then change, cancel, retry or delete it. Pass dry_run=true to create_pin to check a pin before anything is published.
• Fix mistakes. Change a pin with update_pin before it publishes. Published pins can’t be edited through Pinterest’s API, so remove a wrong one with delete_pin and publish it again. Retry a failed pin with retry_pin. Use upload_asset for an image or video that isn’t at a public URL, and delete_asset to remove an upload you no longer need.
• Manage boards. List boards, confirm a board can take pins with check_board_access, and create, update or delete one.
• Measure. Read pin and account analytics, get a dashboard summary, and find Pinterest keyword ideas with list_related_terms.
• Browse & track. List and inspect pins and schedules, review activity logs, check billing status and the live rate meter, and manage webhooks for publish results.

Read tools are always available. The hosted server at https://mcp.pinbridge.io has the write tools enabled too; if you run the server yourself, they stay off until you set PINBRIDGE_MCP_ENABLE_WRITE_TOOLS=true. Ask your assistant to run server_info to see what your connection allows. The delete tools (delete_pin, delete_board, delete_schedule, delete_webhook, delete_asset) are marked destructive, so clients ask you to confirm before calling them, and your key’s scopes and account allow-list apply to every call. All publishing follows Pinterest’s per-pin intent rule. See the usage policy for what that means.

Common issues

Claude doesn’t use the PinBridge tools. Check that the connector is turned on for the conversation in Claude’s tools menu. If Claude reports an authorization error, open the connector in Customize → Connectors and connect again.

Tools are not showing up in another client. Restart the client fully after saving the config. Some clients need a complete quit and reopen, not just a window reload.

Authentication error with an API key. Re-copy the key straight from the dashboard to avoid hidden characters or trailing spaces, and confirm it hasn’t been revoked.

“No Pinterest accounts found”. Connect a Pinterest account from the PinBridge dashboard first. The MCP server only sees accounts linked to your workspace.

Can’t publish / write tools missing. Ask your assistant to run server_info. On the hosted server the write tools are always on, so a publish that fails with insufficient_scope means your API key lacks the write scope: create a key with it, or ask a workspace admin. If you self-host, check PINBRIDGE_MCP_ENABLE_WRITE_TOOLS. Read tools stay available regardless.

“Quota exceeded”. Your plan’s weekly MCP request limit has been reached. Upgrade your plan or wait for the quota to reset.

Next steps

• MCP usage policy: how Pinterest’s per-pin intent rule applies to AI publishing.
• Authentication: create and manage the API keys your clients use.
• Rate limits & quotas: the quotas behind “quota exceeded”.
• MCP overview: the two-guide index for MCP.