Create Pinterest pins from Claude or ChatGPT with an MCP server

Is there an official Pinterest MCP server?

Pinterest announced one on June 17, 2026, in an alpha with agency partners, and its developer page is still a sign-up form aimed at ads and insights. The npm package called pinterest-mcp was published by a community developer, not by Pinterest. Community servers either scrape image search with a headless browser or call Pinterest’s API through a developer app you register, and an app on Pinterest’s trial access creates pins only its creator can see.

Read on 1 October 2026 from each project’s own page. Descriptions of other servers are their own claims; Mellow has not tested them.

Pinterest’s access tiers are on its developer site, read on 1 October 2026.

What Pinterest account do I need?

A Pinterest business account with at least one board to pin to. You sign in to Pinterest yourself. Naming a board is optional: give options.pinterest.boardIds to choose one, and without it the pin goes to a board on the account.

1. Open Accounts in Hub and choose Pinterest, or ask the assistant to call connect_channel with platform set to pinterest. That tool only returns a link and an instruction for a person. It needs the channels:connect permission.
2. Open the link and sign in to Pinterest yourself. Hub never sees your Pinterest password.
3. Tell the assistant you are done. It calls list_channels with refresh: true and uses the returned channel ID, which begins with spc_. A username is not a substitute for that ID.

Connect Claude, ChatGPT, Cursor or another MCP client

Every client uses the same server URL, https://www.mellow.world/mcp, over Streamable HTTP. A client signs in with OAuth 2.1 (dynamic client registration and PKCE) or sends an owner-created Hub API key as a Bearer token. Menus change between client versions, so the official guides linked below describe the current screens. The last column says only what Mellow itself has tested, on any network.

1. Add the server in your client and select Connect. Sign in to Mellow if asked. Hub’s consent screen names the app that is asking.
2. Choose the permissions the task needs (below), select your Pinterest channel, choose review or autopilot, a daily ceiling and an expiry, then approve.
3. Back in the client, run the read-only check from the prompts below. Confirm the profile, the mode and the Pinterest channel ID. Agents shows the grant’s permissions, channels and expiry.
4. If a client cannot complete OAuth, create a key in Agents and set it as the client’s Authorization: Bearer header, from its secret settings or an environment variable. Never paste a key into a chat.

Which permissions to approve

The consent screen arrives with every permission the assistant asked for already ticked, except spending AI credits. Untick anything it should not have.

What you delegate, and how to take it back

Hub treats an assistant’s access as a delegation you give once, with limits: the permissions, the channels (the ones you select, or explicitly all), review or autopilot, a daily ceiling of 1 to 1,000 posts (50 by default) and an expiry of 1, 7 or 30 days (30 by default). Autopilot is the default: the assistant publishes on its own within those limits. Choose review and each post waits for you to approve it in Hub. A key or a connected app cannot approve its own post.

Hub records the posts an assistant creates or has refused, approvals, reschedules, cancellations and connection attempts in a journal you read in Agents. Revoking a key or a connected app takes effect on its next request. Publishing always needs an idempotency key, so a retried request cannot publish twice.

Pinterest rules Hub checks before anything is sent

This table is generated from the registry that validate_post enforces, the same one behind the rules for every network. These are Hub’s input rules; Pinterest still judges the media itself when it fetches it.

Give a video pin a cover: set thumbnailUrl on the media item to a JPEG frame. Without one, Pinterest refused our video pin on September 29, and Hub now reports cover_required before sending. Add a destination with options.pinterest.link, an https address.

Pinterest’s own figures differ from Hub’s in one place: Pinterest allows a description of 800 characters, where Hub checks 500. Pinterest’s pin specs recommend 9:16 at 1080 × 1920 for a full-screen pin and also list 1:2, 2:3, 3:4, 4:5 and 1:1; videos run 4 seconds to 5 minutes (Pinterest Help, read on 1 October 2026).

When validate_post refuses the post

Read ok, issues and notes in the result. The check publishes nothing and reports every problem at once, each with its field and, for a network rule, its channel. Fix them together and validate again.

Other refusals concern the request or the grant: schedule_in_past (use a future time with a UTC offset), insufficient_scope (approve a delegation with the missing permission), channel_out_of_scope (the channel is not in the grant), and at creation daily_limit_reached and idempotency_key_reused. A passing check is not proof of publication: Pinterest can still refuse the media or the account. The free post checker runs the same input rules on a draft before you connect anything.

Prompts you can paste

Replace the bracketed parts. Each prompt names the tools to call, so the assistant does not have to guess the order.

Use only Mellow Hub. Call whoami, then list_channels, then list_platforms.
Tell me my Pinterest channel ID, whether this connection is in review or
autopilot mode, how many posts it may still create today, and Pinterest's
rules. Do not create anything.

Use Mellow Hub. Create a pin on my Pinterest channel from the image at
[public https URL of a JPEG], title "[up to 100 characters]",
description "[description]", link [https address].
Call register_media, then validate_post, then create_post once with
idempotencyKey "pin-[short-name]-1", then get_post. Report the link.

Use Mellow Hub. Schedule a video pin for [time] on [date] in [your timezone]
from the video at [public https URL of an MP4], with the cover image at
[public https URL of a JPEG] as the media item's thumbnailUrl,
title "[title]". Write scheduledAt with an explicit UTC offset. Validate,
then create_post once with idempotencyKey "pin-video-[date]", then get_post.

Media has to be reachable at a public https URL when Pinterest fetches it. An agent that can make HTTP requests, such as Claude Code or a script of your own, can instead call request_upload_url, send a local file with PUT to the returned uploadUrl and use the returned mediaUrl. An assistant that only has Hub’s tools cannot send file bytes itself.

Publish once, then read the Pinterest result

create_post is the step that publishes or schedules. It needs an idempotencyKey of 8 to 120 letters, digits or the characters . _ : -, stable for this post. If the response is lost or times out, send the same request with the same key: Hub returns the original post instead of making a second one. Reusing a key for different content is refused.

Under a review-mode grant the post comes back as pending_review and waits until you approve it, signed in, in Hub. Under autopilot it goes out at scheduledAt, or immediately without it. Always write scheduledAt with Z or an explicit UTC offset.

Then call get_post and read the Pinterest entry in targets, not only the post’s status. publishing means Pinterest has not reported a result yet; published comes with the post’s link; failed comes with the network’s message. In a post to several networks each target settles on its own and the post can end partial: republish only the failed channel, with a new key. Once Pinterest has published a post, Hub cannot edit or delete it; cancel_post works only before it goes out.

Each destination counts once against your plan: one post to Pinterest and two other networks is three publications. Validating, drafting and connecting work without a plan; publishing needs an active one. See plans.

What Mellow has tested with Pinterest

Production records on 1 October 2026 show four pins published through Hub between September 5 and October 1, each with a public link, all on one account. The first, an image, named no board. On September 29 a video sent through Hub’s MCP endpoint by a Claude Code session failed on Pinterest with “Failed to post to Pinterest”; sent again with a cover frame as thumbnailUrl, it published. On September 30 a video pin with a cover, scheduled the evening before, went out at its set time, and on October 1 another video pin, created with an owner-created key about 20 hours ahead for 12:30 UTC, went out at 12:32 UTC with nothing changed in between.

Not tested yet: choosing a board with boardIds, pins with a link, and connecting through ChatGPT or Cursor.

Questions

Related

• Instagram MCP guide for the same pictures on Instagram.
• Character counter for titles and descriptions.
• Publish to social media with an MCP server: the workflow for every network.
• Before an AI agent posts: an MCP checklist.
• API and MCP reference and rules for every network.
• Plans: each destination counts once against the monthly publications.