Free tools Windows power users keep installed
One-click scans. No signup required.
Trendzeist is Paulo Henrique’s local Model Context Protocol (MCP) server for using Google Trends in AI-assisted content research. In his September 29, 2026, DEV Community article, Henrique describes a tool that turns Trends observations into structured topic ideas, literal search questions and keyword comparisons. It can help an assistant organize research, but it does not provide search-volume estimates or show whether AI systems cite your site—and its reliance on undocumented Google Trends endpoints makes ongoing compatibility uncertain.
Henrique says he built Trendzeist because he wanted a free, open-source tool that could run locally as part of a content workflow, and he could not find a Google Trends MCP that matched those preferences. He describes it as an MCP layer over pytrends-modern, with request throttling, persistent disk caching, strict input validation, JSON output designed for language models and a ranked topic-discovery workflow.
As an Amazon Associate I earn from qualifying purchases.
Those are the creator’s descriptions, not independently tested results. Henrique’s article is the basis for the product details below: “I couldn’t find a good Google Trends MCP. So I just built one”.
What Trendzeist is meant to do
An MCP server lets a compatible AI application call tools exposed by another program. In this case, Trendzeist is intended to make Google Trends data available to an assistant through operations for discovering topics, mining questions and comparing keywords. Rather than asking the assistant to interpret an unstructured dump, the project aims to return information in a format it can use in a research conversation.
#1 Best Overall
Henrique describes the project as free, MIT-licensed, local, and usable without an API key or account. These are claims in his article; availability and setup were not independently verified. “Local” describes where the MCP server runs, not a guarantee that no data leaves the computer: requests to Google Trends endpoints still require contacting Google.
How the content-research workflow fits together
Start with seed topics
A prompt such as “Give me blog post ideas about home espresso for US readers” gives an assistant a subject and audience. Henrique’s example uses discover_topics to find and rank candidate topics from seeds. This is a way to generate research leads, not evidence that a candidate has a particular monthly search volume or will attract traffic.
Find the questions people phrase literally
The described mine_questions workflow surfaces question wording related to a topic. That can help an editor distinguish an actual question-shaped angle from a broad subject label, then decide whether a guide, troubleshooting page or comparison would answer it. The resulting phrases are prompts for editorial review, not a guarantee of demand or an exhaustive account of what people ask.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Compare candidate terms
compare_keywords is presented as a way to compare search-interest patterns for terms. For example, an assistant could describe which of several espresso-related phrases appears to be gaining relative interest. Such a comparison can help prioritize what to investigate next, but it cannot by itself tell you how many searches a term receives or how many clicks a page might earn.
Bring in your own site data
Henrique also describes combining Trends observations with Google Search Console and Google Analytics. One proposed use is to look for site pages ranking around positions 8 to 20 in Search Console whose topics may be rising, then use Analytics engagement data to help decide which opportunities deserve attention. This is a research workflow, not a demonstrated ranking improvement: a rising Trends signal does not establish that a specific page will benefit, and the article reports no measured performance result.
What the workflow can—and cannot—say about AI answers
Henrique proposes using emerging topics and questions from Trends alongside a site’s relevance in Search Console and visitor engagement in Analytics to identify subjects where the site might become a strong source for AI-generated answers. A prompt he gives is: “Identify topics where my website could become a strong authoritative source for AI-generated answers.”
That identifies a possible content-planning opportunity, not a prediction that a site will gain authority or be cited. Henrique explicitly says Trendzeist does not measure whether ChatGPT, Gemini, Perplexity or other AI systems are currently citing a site. You would need separate evidence about those systems’ answers to assess citations; this tool’s described role is to help find and organize potential subjects.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchInstallation options described by the creator
Henrique lists these ways to run the package:
uvx trendzeist-mcppipx run trendzeist-mcppip install trendzeist-mcp- Docker image:
ghcr.io/phalkmin/trendzeist-mcp
His article includes a Claude Desktop configuration example and says Cursor, VS Code, Codex and other MCP-compatible applications use the same format. The exact configuration and current package availability are not established here, so consult the project’s current setup instructions before choosing a command or pasting a configuration. Installing a package with pip install puts it in the active Python environment; the uvx and pipx run options are intended to run a package without the same manual environment-install step.
Rank #3
Important limits before relying on its output
Trends is relative interest, not search volume
Google Trends reports a normalized index of relative interest, not the number of searches. Henrique says a separate volume tool is still needed to estimate clicks. Treat Trendzeist’s described trend comparisons as directional signals for choosing what to examine—not as demand forecasts, traffic estimates or volume figures.
The data source may change
Henrique cautions that “Trendzeist relies on Google Trends endpoints that aren’t part of a documented public API.” Because those endpoints may change without notice, compatibility is not assured. Throttling and disk caching are described features, but they do not remove that upstream dependency.
Structured output is not editorial judgment
Ranking candidate topics and returning JSON can make assistant workflows easier to scan, but neither feature establishes that an idea is accurate, distinctive or useful to a particular audience. Check the underlying query, region and time period, then validate the angle against the site’s expertise and existing coverage before commissioning content.
When this approach is a good fit
| Consideration | Trendzeist approach, as described | What to keep in mind |
|---|---|---|
| Where it runs | Local MCP server | Local execution does not mean Trends requests stay on the computer. |
| Cost and access | Creator describes it as free and open-source, with no API key or account required | Current availability and setup were not independently confirmed. |
| Assistant workflow | Structured topic discovery, question mining and keyword comparison | Assistant-ready output still needs human validation. |
| Demand measurement | Google Trends relative-interest observations | Not search volume or a click estimate. |
| Upstream stability | Uses undocumented Google Trends endpoints | Endpoints may change without notice. |
| AI citation tracking | Not provided, according to Henrique | The workflow suggests content opportunities; it does not establish current citations. |
Trendzeist is most relevant if you want an assistant to structure exploratory Trends research and are comfortable with an unofficial, potentially changeable data connection. If the decision depends on exact search volume, traffic forecasting, verified AI citations or a documented stable API, the tool as described does not supply that evidence.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




