Skip to content
Tailwind API

MCP Server Overview

The Tailwind MCP (Model Context Protocol) Server connects AI assistants directly to your Tailwind account. You can plan, create, and schedule Pinterest content in a conversation while Tailwind remains the system that manages your accounts and publishing queue.

Connect an AI assistant

What is MCP?

Section titled “What is MCP?”

MCP is an open standard that lets AI applications connect to external tools and data. Tailwind hosts a remote MCP server at:

https://mcp.tailwind.ai

Choose your AI client in the setup guide. Clients that support OAuth open a Tailwind sign-in page so you can approve access without creating or pasting an API key. API keys remain available as a fallback for clients that cannot use OAuth.

What you can do

Section titled “What you can do”

With the Tailwind MCP Server, an AI assistant can:

  • List accounts and browse boards or board lists
  • Review posts in draft, scheduled, or sent states
  • Check timeslots in your SmartSchedule
  • Create and schedule posts with images, titles, and descriptions
  • Delete posts from your draft or publishing queue

Assistant actions are performed with your Tailwind permissions and count toward the limits or credits included with your plan.

Supported AI assistants

Section titled “Supported AI assistants”

Claude Code

Add Tailwind as a remote HTTP server and authenticate with OAuth.

Setup instructions

If your client is not listed, use the Other MCP client setup.

Example conversations

Section titled “Example conversations”
Send one of these to your assistant to run your first workflow — point it at a URL, let it draft Pins, then schedule them and review the queue in Tailwind.

"What Pinterest accounts do I have connected to Tailwind?"

"Generate Pins from this URL with Tailwind, then show me the drafts: <paste your URL here>"

"Schedule that Pin with Tailwind to a relevant board at my next open time slot."

"Show me the Pins queued in Tailwind for the next week."

Your assistant may ask for confirmation before it performs an action that changes your Tailwind account.

Authentication and security

Section titled “Authentication and security”

Tailwind supports two ways to authenticate an MCP connection:

  • OAuth (recommended): Supported clients send you to Tailwind to sign in and approve access. The client receives a revocable access token; you do not paste an API key into its configuration.
  • API key fallback: Clients without compatible OAuth support can send a Tailwind API key in an Authorization: Bearer header. Keep the key private and revoke it from Settings > Integrations if it is exposed.

Only connect clients you trust. Review the permissions shown during OAuth authorization and review any configuration before accepting an install deeplink.

Next steps

Section titled “Next steps”
  1. Connect your AI assistant
  2. Browse the tools reference
  3. View the resources reference

Building a server-side integration instead of connecting an assistant? Start with the REST API authentication guide.