Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Google Trends interest over time, by region, and related queries and topics, as JSON.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
HASDATA_API_KEY, x-api-keyValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"google-trends": {
"command": "npx",
"args": [
"-y",
"@hasdata/google-trends-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http google-trends 'https://mcp.hasdata.com/mcp?apis=google_trends' --header 'x-api-key: your-value'claude mcp add google-trends --env HASDATA_API_KEY=your-value -- npx -y @hasdata/google-trends-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"google-trends": {
"url": "https://mcp.hasdata.com/mcp?apis=google_trends",
"headers": {
"x-api-key": "your-value"
}
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"google-trends": {
"command": "npx",
"args": [
"-y",
"@hasdata/google-trends-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"google-trends": {
"type": "http",
"url": "https://mcp.hasdata.com/mcp?apis=google_trends",
"headers": {
"x-api-key": "your-value"
}
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"google-trends": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hasdata/google-trends-mcp"
],
"env": {
"HASDATA_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
x-api-key secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain hasdata.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: HASDATA_API_KEY, x-api-key
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.0.7) reached the registry 43 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A hosted Google Trends MCP server that gives Claude, Cursor, Windsurf and any other MCP client one Google Trends tool. Pull interest over time, interest by region, and the rising and top related queries and topics for any term, all as structured JSON, with no scraping library to keep alive and no Google account.
1,000 free credits every month, no card required, which is 100 Google Trends calls.
https://mcp.hasdata.com/mcp?apis=google_trends
An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 100 calls a month at the 10-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run and no Google account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/google-trends-mcp on npm and hasdata-google-trends-mcp on PyPI, shown below.
The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.
| Field | Value |
|---|---|
| URL | https://mcp.hasdata.com/mcp?apis=google_trends |
| Transport | HTTP, streamable |
| Auth header | x-api-key: HASDATA_API_KEY |
Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.
Claude Code
claude mcp add --transport http google-trends "https://mcp.hasdata.com/mcp?apis=google_trends" \
--header "x-api-key: HASDATA_API_KEY"
Claude Desktop
Settings, then Connectors, then Add custom connector, then paste https://mcp.hasdata.com/mcp?apis=google_trends and sign in.
For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The @hasdata/google-trends-mcp package is that launcher, and it reads the key from the environment. Add this to claude_desktop_config.json:
{
"mcpServers": { "google-trends": { "command": "npx", "args": ["-y", "@hasdata/google-trends-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }
For Python instead of Node, swap the launcher for the PyPI package, which uvx runs without a manual install:
{
"mcpServers": { "google-trends": { "command": "uvx", "args": ["hasdata-google-trends-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }
Cursor
~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:
{
"mcpServers": { "google-trends": { "url": "https://mcp.hasdata.com/mcp?apis=google_trends", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
Windsurf
~/.codeium/windsurf/mcp_config.json. Windsurf calls the field serverUrl, not url:
{
"mcpServers": { "google-trends": { "serverUrl": "https://mcp.hasdata.com/mcp?apis=google_trends", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
VS Code
.vscode/mcp.json in the workspace:
{
"servers": { "google-trends": { "type": "http", "url": "https://mcp.hasdata.com/mcp?apis=google_trends", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }
Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 10 credits.
Chart interest in "cold brew coffee" in the US over the past 12 months and tell me which weeks it peaked.
*One call, 10 credits. The weekly series comes back in a single request.*
For "cold brew coffee" in the US, give me the rising related queries and flag the ones marked Breakout.
*One call, 10 credits.*
Compare interest in "cold brew" against "iced coffee" worldwide over five years and say which one is growing.
*One call, 10 credits. The tool takes several terms in one timeseries request.*
Show me interest in "sunscreen" by US state over the past 90 days so I can see where demand is highest.
*One call, 10 credits. This is the interest-by-region view at state granularity.*
A comparison across terms rides in one timeseries call. Region breakdowns, related queries and related topics are each their own dataType, so a prompt that wants a chart plus its rising queries is two calls.
| Tool | What it returns |
|---|---|
hasdata_google_trends_search_getTrendsData | Interest-over-time series, geo-level breakdowns, and rising/top related topics/queries with relative scores. 10 credits a call |
One tool, read-only. The sample below is trimmed from a real call, and the numbers move as the trend moves. Read it as a shape. The tool name links to its endpoint reference, which carries the full parameter list.
The sample is the payload, not the whole response. A tools/call result carries one text block, and that text is itself JSON holding url, status, text and json, with the scraped data under json. From a raw JSON-RPC response the path is result.content[0].text, parsed, then .json. A chat client unwraps that for you and code talking to the endpoint directly does not.
hasdata_google_trends_search_getTrendsData
Interest over time, by region, or the related queries and topics for a term.
| Parameter | Type | Required | Notes |
|---|---|---|---|
q | string | yes | The search term. timeseries and geoMap take up to 5 comma-separated terms to compare, and a sixth is rejected with a 400 |
dataType | string | timeseries by default, plus geoMap, relatedTopics and relatedQueries. The two related types take a single term only | |
date | string | A window such as now 7-d, today 12-m, today 5-y or all, or a custom yyyy-mm-dd yyyy-mm-dd range | |
geo | string | A location code such as US or US-CA. Worldwide when empty | |
region | string | Granularity for geoMap only: country, region (subregion), dma (metro) or city. The default depends on geo, country worldwide and finer once a geo is set | |
cat | string | Category id to narrow the term. 0 is all categories | |
gprop | string | The Google property: images, news, froogle (Shopping) or youtube. Web search when empty | |
tz | number | Time-zone offset in minutes, default 420 (PDT). Shifts how hourly ranges are bucketed |
The response key depends on dataType. timeseries returns interestOverTime.timelineData, geoMap returns interest by region, and the related types return relatedQueries or relatedTopics, each split into rising and top. Read the key that matches the type you asked for.
timeseries (the default) returns a value from 0 to 100 for each point, both as a string and pre-parsed in extractedValue. The most recent point often carries isPartial: true, meaning the week is still filling in. Drop it before you compute a trend, or the last bar reads as a dip that is not real.
{
"interestOverTime": { "timelineData": [ { "date": "Apr 12 – 18, 2026", "timestamp": "1775952000", "isPartial": false, "values": [{ "query": "cold brew coffee", "value": "100", "extractedValue": 100, "hasData": true }] }, { "date": "Aug 23 – 29, 2026", "timestamp": "1787443200", "isPartial": true, "values": [{ "query": "cold brew coffee", "value": "44", "extractedValue": 44, "hasData": true }] } ] } }
relatedQueries splits into rising and top. A rising entry reads as a percentage like +300%, or Breakout for a jump too large to score, and extractedValue gives the number behind it. A Breakout comes back with a sentinel extractedValue well above any real percentage, so sort on the string label, not on the raw number.
{
"relatedQueries": { "rising": [ { "query": "organic cold brew coffee", "value": "+300%", "extractedValue": 300, "link": "https://trends.google.com/trends/explore?q=organic+cold+brew+coffee&date=today+12-m&geo=US" } ], "top": [ { "query": "how to cold brew coffee", "value": "100", "extractedValue": 100, "link": "https://trends.google.com/trends/explore?q=how+to+cold+brew+coffee&date=today+12-m&geo=US" } ] } }
The endpoint reference lists every geo, cat and date format the tool accepts.
The server ships one prompt, a ready-made workflow a client can offer instead of making the user compose a tool call.
| Prompt | What it does |
|---|---|
google_trends | See how interest in a topic changes over time. |
Alongside them the server exposes 5 resources, one per parameter whose accepted values are a fixed list. Reading one is cheaper than learning the vocabulary from a rejected call, and it costs no credits. Each URI is hasdata://google_trends/ .
| Parameter | Values | What it selects |
|---|---|---|
geo | 3517 | Specifies the location for the search. Defaults to Worldwide if not set or empty. |
region | 4 | Used to get more specific results when using "Interest by region" data type. Other data types do not accept this parameter. The default value depends on the geo location that is set. Available options: - country: Country - region: Subregion - dma: Metro - city: City Note: Not all region options will return results for every geo location. |
| dataType | 4 | Defines the type of search to perform. Available options: - timeseries: Interest over time (default). Accepts both single and multiple queries per search. - geoMap: Interest by region. Accepts both single and mul
Only the beginning is shown; read the rest in the repo