Glimpse still wins the Google Trends Chrome overlay and absolute volume on that UI. Trends MCP wins multi-source MCP and REST inside agents.
Live data as of 2026-08-26 · Updated 2026-08-26
Glimpse still wins the Google Trends website in Chrome. Trends MCP still wins Google plus TikTok, YouTube, Reddit, Amazon, and the rest of the catalog inside an agent. Those are different desks. A roundup that treats every overlay, SEO suite, and API as one list lives on best Glimpse alternatives. This page stays the two-product split.
Glimpse (meetglimpse.com) is a browser extension. It sits on trends.google.com and adds absolute volume, long-tail panels, and alerts on top of Google’s own chart. Trends MCP is a hosted MCP at https://api.trendsmcp.ai/mcp (Bearer) and OAuth at https://www.trendsmcp.ai/mcp for Claude.ai. Connecting Trends MCP is free. Calling is not.
Glimpse is the right install when the workflow is already the Google Trends UI. Absolute volume on that y-axis, related-query mining as Google shows it, geographic heat as Google draws it, and alerts while the tab is open are Glimpse’s product. Chrome, Edge, Opera, Brave, and Vivaldi are the browsers Glimpse documents. There is no Cursor JSON. There is no Claude connector.
Trends MCP does not inject a volume layer into trends.google.com. It will not match Glimpse at that job. Claiming otherwise is how comparison pages lose trust.
Glimpse’s own alternatives chapter (accessed 26 August 2026) describes absolute volume over a long Google Trends history, growth rate, seasonality, and tracking. Recheck that page for current UI claims. This vs file does not copy Glimpse’s forecast accuracy number as a Trends MCP fact.
Trends MCP is the right install when the next sentence happens in Claude, Cursor, or a timer. get_top_trends with type Google Trends returns the live board (default limit 25, max 200). get_growth and get_trends with source google search return keyword history. The same key accepts tiktok, youtube, reddit, amazon, npm, and the other sources on data sources. REST mode get_time_series is the series name for cron. Empty history is not_found or data_unavailable.
get_top_trends(type="Google Trends", limit=25)
get_growth(keyword="glimpse trends", source="google search", percent_growth=["30D", "12M"])
get_growth(keyword="air fryer", source="google search, tiktok, youtube", percent_growth=["3M", "12M"])
Claude setup: Trends MCP for Claude. Cursor setup: Trends MCP for Cursor. Google API contract: Google Trends API.
Glimpse does not return TikTok hashtags or a YouTube Trending board. A fashion or food phrase that moves on TikTok first is invisible in a Google-only overlay until Google Search catches up. That lead time is the usual reason to add Trends MCP without uninstalling Glimpse.
Official Google Trends API Alpha is neither product. Application-gated, relative interest, Google’s credential. Trends MCP does not proxy it.
Glimpse: free plan 10 searches per month, paid from $99 per month, per Glimpse’s Google Trends alternatives chapter (accessed 26 August 2026). Recheck that page before a purchase order. Older comparison posts that quote $49 as a Glimpse floor are stale relative to that chapter.
Trends MCP: Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Annual 20 percent off. Pricing. Same sources on every plan. get_top_trends counts per feed and per page. get_growth counts once per source plus keyword.
A weekly Claude session of one Google board, one TikTok board, and ten get_growth rows is 12 requests. That fits the Trends MCP free plan. It does not replace 10 Glimpse searches on the Trends website if the analyst still needs the overlay. Those meters are not interchangeable.
SerpApi (free 250 searches, Starter $25 / 1,000, serpapi.com/pricing, 26 August 2026) is a scrape of Trends pages, not an overlay and not this MCP. Exploding Topics lists Entrepreneur $39 per month, Investor $99, Business $249 (explodingtopics.com/pricing, 26 August 2026) as a curated-trend product. The blog roundup covers that family. This page does not pretend those SKUs are Glimpse.
get_growth pulled 26 August 2026 via Trends MCP, recent_date 2026-08-22, keyword glimpse trends, source google search: 30D 41 to 18 (minus 56.1 percent), 12M 88 to 18 (minus 79.55 percent). That is search demand for the product name, not a quality score for the overlay.
A cooling branded query does not mean Chrome users stopped needing absolute volume on Google Trends. It does mean “Glimpse alternative” is a query this site should answer honestly. The overlay still does a job Trends MCP refuses. The agent path still does a job Glimpse never shipped.
Do not read that series as “Glimpse is dead.” The PyPI-versus-search split on pytrends taught that lesson already: pytrends alternative.
Keep Glimpse for deep Google Trends work in the browser. Keep Trends MCP for multi-source questions in Claude or Cursor, and for REST jobs that should not wait on a laptop. Name the product in the prompt. “Using TrendsMCP” routes to tools. Opening Chrome routes to Glimpse. Mixing those instructions in one sentence is how an analyst pastes a 0-100 index into a slide that needed Glimpse’s volume axis.
A bake-off that only opens Google Trends in Chrome will crown Glimpse. A bake-off that only asks Claude for TikTok versus Google will crown Trends MCP. Run the bake-off that matches the ticket.
Related-query scrape fields and city-level heat remain Glimpse’s (and some scraper APIs’) ground. Trends MCP’s Google tools stay the live board and the google search series. If the ticket is “people also search for” on Google’s UI, Glimpse still wins. If the ticket is “did TikTok move first,” Trends MCP still wins.
FAQ