Trends MCP is the Pinterest MCP to install first when the job is a live public search board plus keyword history in Cursor or Claude. The live type strings are Pinterest Trending and Pinterest Trending by Category on get_top_trends. Country is valid. Default limit is 100, billed as 10 MCP requests (1 per 10 rows), max 200. Keyword history is a second tool: get_growth on source Pinterest, about two years of weekly 0-100 scores. Pinterest's own MCP at https://api.pinterest.com/mcp is the ads path, still invite-only as of 16 Nov 2026. pinterest-mcp 0.3.0 wins own-account boards, pins, and 90-day organic analytics through API v5. pinterest-mcp-server 1.2.0 is a Puppeteer image scrape, not a trend feed.

Which Pinterest MCP should an agent install first?

Pick by job. A live public search board, an ads campaign in chat, and a pin the caller owns are three products.

Trends MCP wins the public-trend job. One Bearer key covers type Pinterest Trending, type Pinterest Trending by Category (21 official names), and get_growth on source Pinterest. Cursor install is one remote URL. No Pinterest app review. The sibling trend-tool roundup, written for dashboards rather than MCP, is best Pinterest trend research tools.

Pinterest's hosted MCP wins ads once an invite lands. The published JSON points at https://api.pinterest.com/mcp with a Bearer token (developers.pinterest.com/about-pinterest-mcp, fetched 16 Nov 2026). The 3 Nov 2026 community post says access is invite-basis and the server is currently built for ads workflows. Exact tool names are not public. The interest form on help.pinterest.com still asks teams to wait until early access opens.

pinterest-mcp 0.3.0 (npm, published 11 Sep 2026) wins own-account work. Thirty-five typed tools cover profile, boards, pins, analytics, own-library search, and OAuth. Analytics sit on Pinterest's organic reporting contract: 90-day lookback for account and Pin metrics (developers.pinterest.com/docs/analytics-and-reports/organic-reporting, fetched 16 Nov 2026). Search tools query the authenticated library. They do not search Pinterest at large.

pinterest-mcp-server 1.2.0 (npm, last published 5 May 2025) wins a local image hunt. Three tools scrape search results with Puppeteer: pinterest_search (default limit 10), pinterest_get_image_info, pinterest_search_and_download. No API key. No ranked search board. HTML changes are the operator's problem.

None of those replace each other. Pair them. Do not expect one JSON blob to post a pin, pull an ads report, and return this month's public Pinterest searches.

Is the official Pinterest MCP server available yet?

Partly. The URL and Cursor-shaped JSON are on the developer page. Access is not a self-serve signup.

Pinterest announced the server on 22 Sep 2026 (community post 51358). On 3 Nov 2026, @PinterestButtercup opened an invite list for developers who want to test ads workflows, and pinned that thread on 5 Nov 2026. The marketing page still prints "Be the first to know when it launches" above the same https://api.pinterest.com/mcp object. Treat that page as a waitlist plus a config preview, not as a live public catalog of tools.

The official path uses OAuth 2.0 and scoped permissions. Pinterest has not published a dollar price for MCP itself. Do not budget from a third-party page. For ads work that cannot wait, the v5 REST ads endpoints still exist behind a reviewed app. Trial access caps the whole app at 1,000 requests per day. Standard access raises that to 100 requests per second per user per app (rate-limits doc, fetched 16 Nov 2026). trends_read, the category on trending-keyword calls, is 1,000/day on Trial and 60/minute on Standard.

Pinterest also ships a separate Trends API, GET /v5/trends/keywords/{region}/top/{trend_type}. That endpoint is not an MCP server. Docs cap it at 50 keywords, return today's date only, and attach a one-year weekly 0-100 time_series per row (analytics-and-reports/trends, fetched 16 Nov 2026). Region is required. Past-date boards are not available. A wrapper that only calls this endpoint still needs a Pinterest app and still cannot ask for November 2025.

Two tools, two strings. Mixing them is the usual invalid_source.

get_top_trends wants type Pinterest Trending or Pinterest Trending by Category. No keyword. Country is an ISO 3166-1 alpha-2 code. Omit country and the board defaults to the United States. The live MCP schema and data-catalog.md (fetched 16 Nov 2026) set default limit 100, which costs 10 MCP requests because boards bill 1 request per 10 rows, max 200. REST at POST https://api.trendsmcp.ai/api bills 1 request per call. Free is 100 requests a month. Paid boards are real-time. Free boards lag 24 hours unless credits sit on the account (llms.txt, Updated 2026-11-16).

Pinterest Trending by Category needs an official name. The 21 names on data-catalog.md are Animals, Architecture, Art, Beauty, DIY and Crafts, Design, Education, Electronics, Entertainment, Event Planning, Finance, Food and Drink, Health, Home Decor, Lawn and Garden, Parenting, Quotes, Sports, Travel, Vehicles, and Weddings. Blank category does not 400. The feed mixes rank-1 rows from every board. Pin one name.

Keyword history is get_growth (or get_time_series) with source Pinterest. Any phrase. About two years of weekly 0-100 search interest. Country is valid. That is shorter than Google Search's about-five-year window on the same catalog. get_context has no Pinterest source. get_reviews has no Pinterest source. A prompt that asks "what are people pinning about X" will not hit a Pinterest conversation feed through this server.

Cursor wants url plus transport http on the API host. The copy-config JSON on the homepage still omits transport. Use this object:

{
  "mcpServers": {
    "trends-mcp": {
      "url": "https://api.trendsmcp.ai/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Mac and Linux store it at ~/.cursor/mcp.json. Windows uses %USERPROFILE%\.cursor\mcp.json. Fully quit Cursor after saving. The host page is Trends MCP for Cursor. That page is still dated 26 Aug 2026 and still prints default limit 25. Live MCP default on get_top_trends is 100.

A current-rank pull and a climber pull are two calls. sort rank_change plus a window (1d, 3d, 7d, 14d, 30d) returns objects with rank, keyword, prev_rank, and rank_change. Default sort stays a rank-and-title list. A limit 10 page costs 1 MCP request. A default 100-row page costs 10.

get_top_trends(type="Pinterest Trending", limit=10)
get_top_trends(type="Pinterest Trending by Category", category="Home Decor", limit=10)
get_growth(keyword="fall nails", source="Pinterest", percent_growth=["3M", "12M"])

Plans from llms.txt Updated 2026-11-16: Free $0 / 100 requests; Starter $19 / 1,000 ($16/month billed yearly, $192 a year); Pro $49 / 5,000 ($39 / $468); Business $199 / 25,000 ($159 / $1,910). Pay-as-you-go packs: $15 / 600, $49 / 2,500, $199 / 12,000. Copy on yearly billing says 2 months free. 54 data sources across 27 platforms. Five billed tools plus free get_usage.

A Google-only Cursor page, useful when the next check is search interest rather than Pin search, is Google Trends MCP for Cursor. TikTok has a matching MCP roundup at best TikTok MCP servers.

Which Pinterest MCP wins which job?

ServerJob it winsAuthPinterest coveragePrice (fetched 16 Nov 2026)
Trends MCPLive public search board plus ~2-year keyword historyBearer key or OAuth on the www hostTypes Pinterest Trending and Pinterest Trending by Category (21 names); get_growth source PinterestFree 100 req/mo; Starter $19; Pro $49; Business $199
Pinterest MCP (official)Ads workflows in chat, once invitedOAuth Bearer at https://api.pinterest.com/mcpAds-first; exact tool list unlistedNo public MCP price; waitlist
pinterest-mcp 0.3.0Own boards, pins, 90-day organic analyticsPINTEREST_ACCESS_TOKEN or app OAuth35 API v5 tools; search is own-library onlyMIT, npx; 28 weekly npm downloads (8-14 Nov 2026); 3 GitHub stars
pinterest-mcp-server 1.2.0Local image search and downloadNonepinterest_search, pinterest_get_image_info, pinterest_search_and_download; default search limit 10MIT, npx; 156 weekly npm downloads (8-14 Nov 2026); 52 GitHub stars
Pinterest Trends API (REST)Today's top 50 keywords with 1-year seriesPinterest app + tokentrending_keywords/list; no past-date board; not MCPApp review; trends_read 1,000/day Trial, 60/min Standard

Trends MCP is first in that table because the query is a Pinterest MCP for live trend data. It is not first for ads, not first for publishing, and not a Pinterest Business login.

What does pinterest-mcp wrap on API v5?

The npm package pinterest-mcp is the widest public v5 wrap found this run. Install is npx pinterest-mcp. Claude Code add uses an env token:

claude mcp add pinterest --env PINTEREST_ACCESS_TOKEN=your_token -- npx -y pinterest-mcp

Tool groups on the 0.3.0 README: account (profile, followers, following, claimed websites); boards (list, get, create, update, delete, sections); pins (list, get, create, update, delete, save, video upload registration); analytics (account daily metrics, top pins, top video pins, single- and multi-pin); search (pinterest_search_my_pins and board search against the signed-in library); OAuth helpers; pinterest_api_request as an escape hatch. Destructive deletes carry destructiveHint. 429 and 5xx retries honour Retry-After up to a 30-second cap. Tokens last roughly 30 days; refresh tokens roughly a year.

Trial vs Standard still binds the wrapper. A new Pinterest app starts on Trial after review. Pins and boards created on Trial are visible only to the creator as sandbox entities (access-tiers doc, fetched 16 Nov 2026). Apps registered on or after 14 Sep 2026 can hit HTTP 403 PINNER_DATA_ACCESS_DENIED when they request a board or Pin without Pinterest's authorization for non-business users. Standard needs an approved Trial app, Developer Guidelines compliance, and a video of the OAuth flow.

A hosted demo at https://pinterest-mcp-http-production.up.railway.app/mcp holds no default token (GET /health reports default_token_configured: false on the README). Callers pass their own Bearer per request. Treat it as a try-out URL. Run a private instance for anything that matters.

pinterest-mcp-server 1.2.0 is a different product with a similar name. GitHub is terryso/mcp-pinterest (52 stars, last push 2 Nov 2026). It depends on puppeteer-core ^24.3.0 and @modelcontextprotocol/sdk ^0.6.0. Default search limit is 10. Env knobs: MCP_PINTEREST_DOWNLOAD_DIR, MCP_PINTEREST_FILENAME_TEMPLATE, MCP_PINTEREST_PROXY_SERVER. Node 18 or higher. No ranked trend board. No ads. No organic analytics.

collactivelabs/pinterest-mcp-server has 41 GitHub stars and a last push of 24 May 2025. It speaks Socket.IO on http://localhost:3052, with seven pinterest.* tools and a README that still clones yourusername. That is not Cursor's url plus transport http shape. Skip it as a current install. sapyx/sapyx-mcp has 0 stars and a last push of 10 Apr 2026. Mentioned so a search hit does not look like a missing row.

FAQ

Is Trends MCP the best Pinterest MCP overall?

No. It is the best fit for a live Pinterest Trending board, a 21-name category board, and about two years of public keyword history next to 53 other sources. Pinterest's own MCP is the better ads server once an invite arrives. pinterest-mcp 0.3.0 is the better own-account publisher and 90-day analytics server. pinterest-mcp-server 1.2.0 is the better keyless image scrape.

What is the exact get_top_trends call for Pinterest?

MCP tool get_top_trends with type Pinterest Trending. REST mode get_top_trends (alias top_trends) to https://api.trendsmcp.ai/api. Country is optional and defaults to the United States board. Default limit on the live MCP schema is 100. Max 200. A limit 10 page costs 1 MCP request. Category boards use type Pinterest Trending by Category plus one official name such as Home Decor.

Can get_growth search Pinterest by pin URL or board id?

Not on the documented path. source Pinterest takes a search phrase, the same shape as Google Search. Pin ids, board ids, and Pinterest profile handles are the v5 wrapper's job. Mixing type Pinterest Trending into get_growth is invalid_source. Mixing source Pinterest into get_top_trends is invalid_request.

Does Pinterest provide an official Pinterest MCP server?

Yes as a URL and a JSON snippet, no as a public self-serve catalog. https://api.pinterest.com/mcp is documented. Access is invite-only and ads-first as of the 3 Nov 2026 community post, fetched again 16 Nov 2026. The interest form still describes early access as not yet open. Exact MCP tool names were not on the public docs this run.

How much does a Pinterest MCP cost to try?

Trends MCP Free is 100 requests a month, no card. pinterest-mcp and pinterest-mcp-server are MIT npx installs; Pinterest still has to approve a v5 app before the API wrapper can act. Official Pinterest MCP has no public price. Pinterest Trends in a Business account remains the free dashboard for search, save, and shopping curves up to two years (help article, fetched 16 Nov 2026). Check current pricing on each vendor before locking a budget.

Sources (accessed 16 Nov 2026): Trends MCP llms.txt (Updated 2026-11-16), homepage copy-config, pricing page, data-catalog.md; live MCP get_top_trends and get_growth tool schemas; Pinterest MCP page and community posts 51358 (22 Sep 2026) and 52939 (3 Nov 2026); help.pinterest.com MCP interest form; Pinterest Trends help article; Pinterest access-tiers, rate-limits, organic-reporting, and Trends API docs; npm pinterest-mcp 0.3.0 and pinterest-mcp-server 1.2.0 plus npm download counts for 8-14 Nov 2026; GitHub aymandakirgh/pinterest-mcp, terryso/mcp-pinterest, collactivelabs/pinterest-mcp-server, sapyx/sapyx-mcp.