Pinterest keyword data inside ChatGPT and Claude

The quick way: sign in, no key to copy

Claude, ChatGPT, Claude Code, Cursor and VS Code can connect with just the server URL. They open a PinPinterest sign-in, you press Allow, and the app gets its own key (it shows in Settings → API as “connected”; revoke it there to disconnect).

claude mcp add --transport http pinpinterest https://api.pinpinterest.com/mcp

Server URL: https://api.pinpinterest.com/mcp. An app that cannot sign in (n8n, a script) uses a key, below.

1. Get your API key

Create an account, then open Settings → API in the dashboard and press Create key. The same key works for the REST API and here, and both draw on one monthly allowance.

Server URL: https://api.pinpinterest.com/mcp

The pin limit

Each plan can see a set number of different pins in any 30 days, with a tenth of it a day. One count covers the API, the MCP and the app together. A pin counts once per 30 days, so re-reading pins you have already seen is free, and keyword numbers (searches, related terms, trends) are not part of it.

• Starter: 20,000 different pins a month, 2,000 a day
• Pro: 60,000 different pins a month, 6,000 a day
• Studio: 200,000 different pins a month, 20,000 a day
• API Scale: 350,000 different pins a month, 35,000 a day

At the limit, pins you have already seen still come back and new ones pause: the API answers HTTP 429 with code: "pin_limit", returns_at (when new pins return) and upgrade_plan; a page that only partly fits answers 200 with the pins that fit and a pin_limit object. Why a pin limit? It keeps the data fair and fresh for everyone and stops bulk copying of the database.

2. Add it to your app

claude mcp add --transport http pinpinterest https://api.pinpinterest.com/mcp \
  --header "Authorization: Bearer pp_live_YOUR_KEY_HERE"

https://api.pinpinterest.com/mcp?key=pp_live_YOUR_KEY_HERE

https://api.pinpinterest.com/mcp?key=pp_live_YOUR_KEY_HERE

{
  "mcpServers": {
    "pinpinterest": {
      "url": "https://api.pinpinterest.com/mcp",
      "headers": {
        "Authorization": "Bearer pp_live_YOUR_KEY_HERE"
      }
    }
  }
}

{
  "servers": {
    "pinpinterest": {
      "type": "http",
      "url": "https://api.pinpinterest.com/mcp",
      "headers": {
        "Authorization": "Bearer pp_live_YOUR_KEY_HERE"
      }
    }
  }
}

Endpoint: https://api.pinpinterest.com/mcp
Server Transport: HTTP Streamable
Authentication: Bearer Auth → pp_live_YOUR_KEY_HERE

Replace pp_live_YOUR_KEY_HERE with your key. Keep a URL with your key in it private — anyone holding it can spend your lookups. You can revoke a key and make a new one at any time.

3. Ask

• How competitive is "fall porch decor" on Pinterest, and is it worth a pin?
• Those dog-grooming keywords came back as not tracked — ask PinPinterest to crawl all of them.
• Give me ten related Pinterest keywords for "meal prep" with low competition.
• Show me the top pins ranking for "capsule wardrobe" and what their titles have in common.
• What are the most-saved video pins in home decor from the last 30 days?
• What is rising in the food niche right now?
• How many PinPinterest lookups do I have left this month?

The tools

Each tool is a REST endpoint underneath, with the same numbers, the same plan rules and the same meter — see the allowance on each plan. When the month runs out, the assistant tells you, along with the plan that lifts the limit.

A keyword we have not crawled yet costs nothing. On a paid plan we start crawling it the moment you ask, and request_keywords queues a whole list in one go — you get one e-mail when they are in, and asking your assistant again then answers with the data. How the crawl works.