Google Trends MCP server

Read from the package source without running it. The installed server may list more.

• check_endpoints

  Ask each Google Trends endpoint one small question and report which ones answer.

• clear_cachewrite action

  Delete saved answers so the next call asks Google again.

• compare_locations

  One term in up to 5 countries or regions side by side: where it matters more, and whether the curves move together.

• compare_many

  Rank 6 to 25 terms on one scale — past Google Trends' limit of five per comparison.

• compare_periods

  One term in two time ranges on the same scale: this year against last year, this quarter against the one before.

• content_calendar

  A publishing calendar from seasonality: for up to 8 topics, when each peaks and the date its content must be live.

• daily_history

  Day-by-day interest over a long range — Google Trends itself only gives daily data for up to ~9 months.

• find_category

  Find the id of a Google Trends category ("Autos & Vehicles" = 47) to narrow a term to one meaning.

• find_location

  Find the location code (geo) for a country, region, state or metro area by name.

• find_spikes

  The moments a term suddenly jumped: when each spike started, when it peaked, how long it lasted and how big it was.

• find_topic

  Find the Google Trends *topics* for a piece of text and the ids that select them.

• get_capabilities

  Version, settings, session and cache state, saved history and the list of tools. Call this first when unsure.

• history_sqlwrite action

  Run a read-only SQL SELECT on the local data file, for questions the other history tools do not cover.

• interest_by_region

  Where a term is most popular: countries, regions, cities or metro areas ranked by interest.

• interest_over_time

  Search interest over time for up to 5 terms on one shared scale — the main Google Trends chart.

• keyword_ideas

  Keyword ideas from what people actually search next: rising and top related queries for up to 5 seed terms, merged.

• keyword_overview

  The whole Google Trends page for one term in a single call: curve, direction, top places, related searches.

• match_trends

  Which current trends touch your subjects — for newsjacking and timely content.

• related_queries

  What else people who search a term also search: the top related queries and the rising ones.

• related_topics

  The topics (people, brands, things) searched alongside a term, top and rising, with their topic ids.

• seasonality

  The yearly rhythm of a term: which months it peaks and dips, how reliably, and when to publish for it.

• share_of_search

  Share of search: your brand's portion of all searches for you and up to 4 competitors, and how it is moving.

• snapshot_trending

  Save the current Trending Now list to the local history, so it can still be searched after Google drops it.

• trend_details

  Everything about one current trend: every query in it, the news behind it, and its hour-by-hour curve.

• trend_momentum

  Is each term growing, fading, flat or exploding — with the numbers behind the verdict.

• trending_across_countries

  Trends that are live in several countries at once — the stories that travel.

• trending_feed

  The top daily search trends with the news stories behind each — Google's public trending feed.

• trending_history

  Search the saved Trending Now history: when something trended, how big it got and how long it lasted.

• trending_now

  What people are searching right now: the full Trending Now list for a country or region.

• watchlist_addwrite action

  Put terms on the watchlist so watchlist_report tracks their direction over time.

• watchlist_removewrite action

  Take terms off the watchlist. Blank geo removes them from every location; their past readings are kept.

• watchlist_report

  The watchlist measured now: each term's direction, what changed since the last report, and whether it is trending today.

• Code scan17 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Google Trends: common questions

Is Google Trends MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Google Trends safety report

How do I install Google Trends?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Google Trends need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Google Trends maintained?

The last commit was 11 days ago (2026-10-02). The latest release is v0.1.1.