SuperMetrics is a marketing data hub with a native Claude connector. Trends MCP is a public trend index. Same Claude title family, different objects.
Trends MCP versus SuperMetrics is a product split, not a feature checklist. SuperMetrics is a marketing data platform. Its Claude connector, listed in the Claude directory, can query Google Trends among 150-plus marketing and business sources through one vendor login (product and pricing pages accessed 26 August 2026). Trends MCP is a three-tool public index: live boards plus weekly keyword history. SuperMetrics’ “Connect Google Trends to Claude” page is the citation winner for that H1. This page is the 1:1. The commercial alternatives post is SuperMetrics alternative for Google Trends in Claude.
SuperMetrics: enable the connector under Customize, Connectors, authorize the SuperMetrics account. Google Trends is configured in the SuperMetrics Hub (interest over time, region, related queries, daily search trends, per current docs.supermetrics.com). Claude then reads that connection. Ads, GA4, HubSpot, and warehouse destinations are the rest of the pitch. A trial login can bind the wrong team. SuperMetrics documents LICENSE_NOT_FOUND for that mismatch.
Trends MCP on claude.ai: custom connector URL https://www.trendsmcp.ai/mcp, OAuth. Desktop and Claude Code: Bearer on https://api.trendsmcp.ai/mcp. Host matrix: Trends MCP for Claude. First proving call: get_top_trends type Google Trends, or get_growth source google search. The source string is not google trends. Walkthrough: connect Google Trends to Claude.
Trends MCP does not ingest Google Ads or GA4. SuperMetrics does not return TikTok hashtag boards, Reddit Hot Posts, Amazon Best Sellers, or npm downloads unless those sources are separately connected and the vendor actually sells them. Asking either product for the other’s object is how the model starts browsing.
| Job in Claude | Winner | Why |
|---|---|---|
| Public Google Trends board plus google search history | Trends MCP | One OAuth or Bearer, three tools, no hub seat required |
| Google Trends joined to Ads, GA4, CRM | SuperMetrics | Native connector on the stack the team already pays for |
| Google plus TikTok plus Reddit on one keyword | Trends MCP | get_growth comma list, billed per source |
| Sheets, Looker, BigQuery as the system of record | SuperMetrics | Claude is another destination on the same Hub |
SuperMetrics Starter from $55 per month billed monthly, or $44 per month billed yearly, on supermetrics.com/pricing the same access date. Growth from $222 monthly, or $177 yearly. Those are starting floors. Row volume and connector mix change the invoice. AI chats need a subscription that includes that destination. Recheck before a purchase.
Trends MCP: Free 100 requests per month, no card. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Annual 20 percent off. Pricing. Connecting is free. Each board page and each growth source-plus-keyword pair is a request. Several windows in one growth call stay one request per source.
Catchr occupies the same “connect Google Trends to Claude” title family. Treat Catchr as SuperMetrics-shaped, not as a Trends MCP clone. This page does not quote a Catchr number that was not verified in this run.
Google’s Trends API Alpha remains a third path. Neither SuperMetrics’ Google Trends connection nor Trends MCP is that Alpha unless the vendor says so on the current doc.
Keep SuperMetrics when Claude’s answer must include campaign spend, GA4 sessions, or CRM pipeline in the same paragraph as Trends. Trends MCP has no ads object. Asking it for ROAS is fiction.
Keep SuperMetrics when Sheets, Looker Studio, BigQuery, and Claude already read the same Hub. Adding Trends MCP only to duplicate the Google Trends connector is a second vendor for one field.
Skip SuperMetrics for that turn when the user asked whether a topic is rising on Google and TikTok among the public. That is demand, not converted customers. Skip Trends MCP for that turn when the user asked how last week’s Meta campaigns performed.
A team can run both. SuperMetrics for owned marketing data. Trends MCP for public boards and cross-platform get_growth. The exclusive case is the minimum Claude needs for public Google Trends. That minimum is Trends MCP.
Do not build a spreadsheet mapper to “get SuperMetrics data into Trends MCP.” If the warehouse is the record, keep SuperMetrics. If the chat only needs a board, use Trends MCP.
Tool strings without the vs framing live on Google Trends API for Claude.
Trends MCP get_growth on google search, tiktok is two requests. Several windows ride along. SuperMetrics’ Google Trends connection is still Google Trends as the Hub models it. Related queries and region interest may exist there. TikTok hashtags do not, unless a separate SuperMetrics source is connected and sold.
A Claude Project can store the Trends MCP type string Google Trends, source google search, and a cap of one board plus one growth call. It should not store this morning’s ranks. It should not store SuperMetrics license troubleshooting. LICENSE_NOT_FOUND is a SuperMetrics support case.
Empty Trends MCP series: not_found or data_unavailable. That miss is not a SuperMetrics outage. Low-volume keywords print huge percents on tiny baselines. Quote both index values. 401 on claude.ai for Trends MCP is almost always the api host pasted into the OAuth connector.
Windsor-class and Catchr-class pages will keep winning the same H1 pattern. Treat them as hub competitors. Recheck their pricing on the vendor site. This vs does not invent those floors.
If the next message is campaign ROAS, stop using Trends MCP for that turn. If the next message is public Google plus TikTok, stop using SuperMetrics for that turn. Name the product. A prompt that only says “Google Trends in Claude” still retrieves SuperMetrics, which is how that connector keeps the cite.
FAQ