Pinterest MCP Server for Posting Pins From Claude and ChatGPT

A Pinterest MCP server is a program that hands an AI assistant a set of Pinterest tools. Claude, ChatGPT, Claude Code and Cursor all speak the Model Context Protocol, so once a server is connected the assistant can call tools such as "list my boards" or "create a Pin". You describe the Pin in plain words, the assistant picks the tool, and the server makes the request to Pinterest.

People who search for a Pinterest MCP want one of three things: to publish Pins without opening Pinterest, to research images and trending keywords, or, for advertisers, to ask about campaigns. Each needs a different server. This page is about publishing.

A Pin is stricter than a post on most networks. It always lives on a board, it carries a title next to the description, and the link is the point of it, because people tap a Pin to reach the page behind it. A good Pinterest MCP server handles all three.

For the wider field, our roundup of the best social media MCP servers compares every scheduling vendor with a server, and the Spreadcast social media MCP server page covers every network it posts to. The same questions for other networks are on the Instagram MCP server page and the LinkedIn MCP server page. This page stays on Pinterest.

Yes and no, on October 16, 2026. Pinterest does run something called Pinterest MCP, but it is not a way to post Pins. Pinterest's newsroom post from June 17, 2026 describes it as infrastructure that connects Pinterest to the copilots and agent tools advertisers use, with access to campaign, analytics and keyword insights. Pinterest says it is developing it with alpha partners and names PMG, Pacvue, Dentsu, Havas, Innovid by Mediaocean and Omnicom's Jump450. The post does not mention organic Pins and does not name Claude or ChatGPT.

Pinterest's own blog post on AI for marketers, from June 29, 2026, calls it an open source MCP server but links no code repository and no developer documentation. Advertisers who want in are told to contact their Pinterest team. So for a founder who wants to put a Pin on a board from a chat, there is no official server to connect today, and no public address to paste into an assistant.

Claude's side is just as empty. A search for Pinterest in Claude's connector directory returned no connectors when we checked. Every Pinterest MCP server that publishes Pins is built by someone other than Pinterest, on top of Pinterest's public API.

So the first test for any server is how it reaches Pinterest: through the API after you approve access on Pinterest's own screen, or through a hidden browser or your password. Only the first stays within Pinterest's rules.

Not from Pinterest. A search for Pinterest in ChatGPT's plugin directory on October 16, 2026 returned one result, and it was Tailwind, a Pinterest scheduling company, not Pinterest. Tailwind's listing in the directory names Tailwind App as the developer and describes drafting Pins from webpages, managing boards and board sections, reviewing recommended posting times and scheduling Pins. If you already pay for Tailwind and want a ChatGPT Pinterest integration that schedules, it is the most direct option in the directory.

Without any app, ChatGPT can still write a Pin title and description, suggest board names and brainstorm Pin ideas. It cannot see your boards or publish, so you copy the words and make the Pin in Pinterest by hand.

A custom MCP server closes that gap, with a catch on the ChatGPT side. OpenAI's help article on custom MCP servers gives full support, including write actions, only to Business and Enterprise or Edu on the web. Pro users get read and fetch permissions, which cannot save a Pin.

Yes, Pinterest has a public API, now on version 5, and anyone with a business account can register a developer app for it. The permissions it hands out cover user accounts, boards, Pins, ads, catalogs and billing, each as a read or a write scope, per Pinterest's authentication guide. Posting needs only a small part of that: Pinterest's guide to creating boards and Pins shows a POST to the v5 pins endpoint with an image link as the media source and the board the Pin should sit on.

On price, we found no fee anywhere in Pinterest's developer pages. Pinterest's access tiers page describes Trial and Standard access with no charge attached, and nothing in the documentation mentions a paid plan or a bill. The cost is time: a review for each tier, the daily caps on Trial access, and a token that has to be refreshed before it lapses, all covered below.

A hosted Pinterest MCP server skips that work, because its own app already went through review.

This is the part most GitHub READMEs leave out. When you register a Pinterest developer app, it starts on Trial access. Pinterest's page on access tiers says Trial access can create Pins and boards, but marks both as visible only to the creator. All Pins and boards made with Trial access are sandbox entities, which you can see on your own profile and nobody else can.

So a self hosted Pinterest MCP server on a fresh app looks like it works. The assistant reports success, the Pin shows up when you open Pinterest, and no follower ever sees it.

Getting Pins in front of people needs Standard access, and Standard needs a review. The same page asks for a screen recording of your app completing an action through the API, including the OAuth sign in, even if you are the only person who will ever use it. Pinterest lists the reasons it turns requests down. One of them matters for MCP servers in particular: an app that collects login credentials or Pinterest session cookies instead of using an OAuth token may be denied.

There is a newer wrinkle as well. Pinterest's developer changelog says apps registered on or after September 14, 2026 may get a 403 error named PINNER_DATA_ACCESS_DENIED when they read a board or a Pin of a non business user without Pinterest's approval. The affected calls include getting a board, listing Pins on a board and getting a Pin. Pinterest says not to retry the call in a loop and to ask your Pinterest account manager for access. Apps registered before that date are not affected.

None of this applies to a hosted service whose own app already holds Standard access. Its Pins go out as normal public Pins.

Requests fail at both tiers, and Pinterest's access tiers page names the usual causes. A Trial request is turned down when the privacy policy is inaccurate, does not load in full, is not public, or sits on a domain that has nothing to do with your company or app. It is also turned down when the app description is incomplete or unclear.

A Standard request usually fails on the demo video. Pinterest rejects videos that skip the sign in step, that show a sign in flow other than Pinterest's own authorization screen, and that show wireframes or a general tour of your product instead of a live connection to Pinterest. It accepts a recording made in a terminal or in Postman, and the recording should make clear that no sensitive information is stored.

For a self hosted MCP server with no screens of its own, a terminal recording is the simplest route: start the server's sign in, approve access on Pinterest's page, create one Pin and open it. Put your privacy policy on a page of your own domain before you apply, even if you will be the only user. Pinterest emails its decision, and the same page suggests allowing a few days before you follow up on an appeal.

People search for a Pinterest pin limit per day because they fear an automated tool will get them flagged. The answer has three parts.

First, Pinterest publishes no daily cap on how many Pins a person may create. We found none in its help center, its developer documentation or its developer guidelines. The daily figures that circulate online, such as 15, 25 or 50 Pins a day, come from bloggers and tool vendors, not from Pinterest.

Second, the API has caps, and they apply to the tool rather than to you. Under Trial access, creating Pins shares 300 requests a day across the whole app. Under Standard access it is 100 a minute for each user of each app. Be wary of numbers in READMEs that Pinterest does not publish: one popular Python Pinterest MCP server states 10 Pins a minute and 250 a day as Pinterest's limits for organic posting, and neither figure appears on Pinterest's rate limits page.

Third, Pinterest's own tools have limits of their own. Pinterest's page on scheduling Pins lets a business account schedule a Pin up to 30 days ahead and hold up to 10 scheduled Pins at a time. And every account has lifetime limits of 2,000 boards and 200,000 Pins.

What Pinterest does say plainly is how a tool should behave. Pinterest's developer guidelines say that when an app lets people schedule Pins, the person must choose each Pin to be published. The same guidelines rule out features that let people start actions automatically without considering each one, and features that make it easier to spam Pinterest. For an AI assistant, the safe reading is simple: an assistant can propose a week of Pins, and a person should look at each one before it goes out.

The first risk is quiet failure. A server built on your own Trial app publishes Pins nobody else can see, and nothing in the assistant's reply tells you so. Check one Pin from a second account, or from a browser where you are signed out, before you trust a week of them.

The second is your account. Scraping servers drive Pinterest's website, which is what Pinterest's developer guidelines forbid when they rule out automated scraping and soliciting login credentials. A server that asks for your Pinterest password or a session cookie is the same pattern Pinterest names as a reason to deny Standard access. Bulk tools carry their own risk, because the guidelines expect a person to choose each Pin that is published.

The third is where the keys live. Self hosted servers keep your app secret and your access token in a local file or a config entry. The MCP security best practices warn that local servers may have direct access to your system, can be reached by other processes on the same machine, and run with the same privileges as the client. Anyone who can read that file can create and delete Pins on your account.

The fourth is upkeep. Pinterest keeps changing its API, as the September 14, 2026 change to reading Pins shows, and with a self hosted server every fix is your job.

Spreadcast is a hosted Pinterest MCP server for people who make App Store apps. You connect Pinterest once in Spreadcast and Spreadcast once in your assistant. What sets it apart from a plain posting server is that it also makes the Pin: it designs the picture in your app's brand, writes the Pinterest title and description, and saves the result as a draft for you to approve.

On the Pinterest side, Spreadcast signs in through Pinterest's OAuth screen and asks for five permissions: user_accounts:read to know which account it is, boards:read and boards:write for boards, and pins:read and pins:write for Pins. It never sees your Pinterest password and does not use a browser session.

The picture comes from the same design code as the Spreadcast app. A single post comes in one of 11 kinds, such as feature, launch, tutorial or stat, in your app's colors, fonts and logo, with a real screenshot of your app in an iPhone frame when your brand kit has one. Designs are 1080 by 1350 pixels, a 4:5 shape. That is shorter than Pinterest's recommended 2:3, so the whole picture shows in the feed, though it stands a little less tall than a 2:3 Pin would.

The words are written for Pinterest rather than copied from Instagram: two or three sentences full of the words people search for, under 450 characters, no hashtags, plus a separate title. When the assistant works from your App Store news, the moment it reads includes the store address, so the Pin can link to your App Store page.

Then it stops. Every new connection saves drafts, and a draft waits on your Spreadcast calendar until you approve it. If you choose Make and Publish when you connect, the assistant is told to show you the Pin, the network and the time and ask before it schedules or publishes. Scheduling and publishing need the Pro plan.

The same draft can also go to Instagram, TikTok, LinkedIn, Facebook, Threads, Bluesky, Telegram and Discord, and YouTube and Mastodon connect too, each with text written for that network.

Every Pin needs a board, so boards come up in almost every Pinterest chat. Pinterest's page on entities explains the shape: boards hold Pins on a common theme, boards can have sections, and each Pin belongs to one board or one section. A Pin can still appear on more boards later through saving, which Pinterest recommends for curating so accounts do not hit their limits.

An assistant is good at the thinking part: planning boards around the phrases your audience searches and sorting Pin ideas into them. For an app, a few boards built around the jobs it does, such as morning routines, beat one board named after the app.

Doing it is where servers differ. Open source API servers usually include tools to list and create boards, and Tailwind's ChatGPT app lists and creates boards and sections. In Spreadcast you pick the board in the editor when you approve the Pin. Left empty, it goes to the account's first board.

For the strategy behind boards and Pins for an app, our guide to Pinterest for app founders covers what to pin and how often, and our comparison of Instagram, Pinterest and LinkedIn helps decide whether Pinterest deserves your time at all.

It does not post several pictures in one Pin. A Pinterest post in Spreadcast is one picture or one video, so a carousel designed for Instagram cannot go to Pinterest as it is. Use one slide, or design a single post for the Pin.

It does not list or create boards from the chat. The board is picked in the Spreadcast editor, and the assistant leaves it to the account's first board.

It does not fill alt text or Pinterest's AI disclosure field. Spreadcast designs are built from your real screenshots, fonts and colors. If you attach a picture made with an AI image tool, know that TechCrunch reported Pinterest reads image metadata and runs its own classifiers to put an AI modified label on such images, whatever fields the posting tool sends.

It does not read each Pin's numbers. Spreadcast records your Pinterest followers, following and Pin count every day, but not impressions, saves or clicks per Pin. Check those in Pinterest Analytics, which comes with a free business account.

It does not search Pinterest, read other people's Pins or create ads. Spreadcast is built for publishing your own Pins.

Pinterest puts an AI modified label on image Pins it thinks were made or edited with generative AI. In its April 30, 2025 post on the Pinterest Business Community, Pinterest said the label appears at the bottom left when someone opens an image Pin up close, that it comes from reading the image's metadata plus classifiers that look for AI content without obvious markers, and that those classifiers are not always right. Creators who think a Pin was labeled by mistake can appeal through Pinterest's Help Center.

Viewers can act on the label as well. A later Pinterest post on the same forum, dated October 22, 2025, describes a choice under refine your recommendations in settings that lets people see fewer generative AI Pins in each supported category. It reached Android and desktop first and iOS over the following weeks.

For an app maker this is a reach question. People who chose to see fewer AI Pins will see fewer of the Pins that carry the label, so a Pin built from real app screenshots and your own fonts and colors is the safer bet than one made with an image generator.

Pinterest's own scheduler costs nothing. With a free business account, Pinterest's scheduling page lets you choose Publish at a later date when you make a Pin on the website, or set a date in the app, up to 30 days ahead. You schedule one Pin at a time and can keep up to 10 waiting. Once a Pin is scheduled you can still change its date, title, board, description and link, but not the picture or the video.

That covers a few hand made Pins a week, but not designed Pins, more than 10 in the queue, or the same post on other networks.

On Spreadcast's Free plan the assistant designs Pins, writes their titles and descriptions and saves drafts, all without charge. Scheduling and publishing from Spreadcast need Pro. Spreadcast publishes each Pin through the API at the time set on the post, so the 10 Pin queue of Pinterest's own scheduler does not apply.