Keyword Research MCP: autocomplete, search volume, difficulty and Google Trends

Name: Keyword Research MCP: autocomplete, search volume, difficulty and Google Trends
Author: fairfetch-data

by fairfetch-dataversion 1.0.0i★ –iRuns in the cloud

Registry nameio.github.fairfetch-data/keyword-research-mcp

Install

Overview

Description from the maker (original English)

Pay-per-call keyword research via Apify: autocomplete, volume, CPC, difficulty, ideas, Google Trends

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Search & AI memory
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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.

Run this in your terminal

claude mcp add --transport http keyword-research 'https://mcp.apify.com/?tools=fairfetch/keyword-research-mcp' --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "keyword-research": {
      "url": "https://mcp.apify.com/?tools=fairfetch/keyword-research-mcp",
      "headers": {
        "Authorization": "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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "keyword-research": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=fairfetch/keyword-research-mcp",
      "headers": {
        "Authorization": "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.

Values you fill in

Authorization secret HTTP header
Bearer , or leave empty and sign in with OAuth. Token: https://console.apify.com/settings/integrations

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account fairfetch-data, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 118 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7271 servers in this category
Published to the registry more recently than 76% of the other 7271 servers in this category
Basic checks equal to or better than 100% of the other 7271 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Keyword Research MCP: autocomplete, search volume, difficulty and Google Trends safe?

It passed 3 of 3 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.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 11 days ago.

Which apps can use it?

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.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

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.

Keyword Research MCP: autocomplete, search volume, keyword difficulty and Google Trends for AI agents

A remote MCP server with six read-only keyword research tools that Claude, Cursor, VS Code and other MCP clients and AI agents can call: Google, YouTube and Bing autocomplete; keyword search volume, CPC, competition, keyword difficulty and search intent; keyword ideas; and Google Trends (interest over time, related queries, trending searches).

It runs on Apify as the Actor fairfetch/keyword-research-mcp, published by fairfetch, an independent developer on Apify Store. You pay per call through your Apify account. There is no subscription, and you don't need an Ahrefs, Semrush, Google Ads or DataForSEO account.

This repository holds only the listing: this README, server.json for the MCP Registry, and the icon. The server's source code is not published.

Tools and prices

Tool	What one call returns	Price
`search_suggestions`	Autocomplete suggestions from Google, YouTube and Bing for 1-10 seeds, optionally expanded with a-z/0-9 or question words	$0.002 per query (one seed on one engine = 1 query; a-z expansion = 37 queries per seed and engine)
`keyword_metrics`	Search volume, CPC, competition, keyword difficulty, search intent and trend for 1-200 keywords	$0.10 per 25 keywords with data (1-25 keywords = 1 block, 26-50 = 2 ...)
`keyword_ideas`	Up to 200 keyword ideas for one seed (longer keywords that contain it, or Google's related searches) with the same metrics	$0.12 per 50 keywords returned
`google_trends_interest`	Google Trends interest over time for 1-5 terms on one scale, optionally by region	$0.02 per call
`google_trends_related`	Google Trends top and rising related queries for one term	$0.02 per call
`google_trending_now`	Trending searches in a country or region in the last 4, 24, 48 or 168 hours	$0.01 per call

Prices as read from the Apify API on 27 Oct 2026; the pricing on the Actor's Apify page is authoritative. Failed calls, invalid arguments and calls without data cost nothing, and keywords without data are not counted. Arguments, output fields and examples of every tool are documented on the Actor's Apify page.

Example	Charges
Autocomplete for 5 seeds on Google	$0.01
Autocomplete for 1 seed on Google, YouTube and Bing with a-z expansion (111 queries)	about $0.22
Search volume and difficulty for 20 keywords	$0.10
Search volume and difficulty for 100 keywords	$0.40
50 keyword ideas for one seed	$0.12
Google Trends: compare 5 terms over 5 years	$0.02
A research session: 3 autocomplete calls, 40 keywords checked, 50 ideas, one Trends comparison, related queries	about $0.37

Apify platform usage, on top of these prices. The server runs in Apify's Standby mode, and for Standby Actors Apify bills your account for the server's platform usage:

The server starts when your MCP client connects to it, and most clients connect when they start or when a chat starts, even if no tool is used. It stops 5 minutes after the last request. Each start came to about $0.005 at 256 MB in our tests, the 5-minute tail included.
Each start also costs Apify's start fee of $0.00005 and one small request through Apify's residential proxy that prepares Google Trends (about $0.0001).
Every Google Trends call adds about $0.00015 of proxy traffic.
If your client sends more than 8 requests at the same moment, Apify starts a second server, which adds its own 5-minute tail (about $0.0045).

Cost control: read this before giving an agent these tools

Each call is bounded by the tool's own argument limits. The most a single call can cost at today's prices:

Tool	Largest single call	Cost
`search_suggestions`	120 queries, the per-call maximum	$0.24
`keyword_metrics`	200 keywords, all with data (8 blocks)	$0.80
`keyword_ideas`	200 ideas (4 blocks)	$0.48
`google_trends_interest`	one call	$0.02
`google_trends_related`	one call	$0.02
`google_trending_now`	one call	$0.01

An agent that keeps calling is not stopped by these limits. What limits its spending:

Every tool description includes its price, so the agent sees what a call costs, and an answer is billed only when it has data.
Every run has a maximum charge. For this MCP server Apify sets it itself (in our test it matched the account's remaining usage limit). A call that would go over it is refused before anything is fetched, and the error says how much is left.
Set your Apify usage limit to what you are willing to spend, in Apify Console under Billing > Limits (Custom usage limit), up to your plan's maximum. Apify suspends the account's services when the limit is reached. On the Free plan the limit is your monthly free usage (the Free plan includes $5 of usage per month, pricing); to allow more, upgrade or wait for the next billing cycle.
A running server keeps the maximum it started with. After raising the limit, close or disconnect your MCP client for 5 minutes, so that a new server starts with the new limit.
Remove or disable the server in clients and projects where you don't use it. A connected client can start the server (about $0.005 each time) without calling any tool, for example each time the client starts or opens a new chat.

Connect

Option 1: Apify's hosted MCP server (sign in with Apify, no token to copy)

Add this URL as a remote MCP server (Streamable HTTP). Your client then asks you to sign in to Apify (OAuth) in your browser:

https://mcp.apify.com/?tools=fairfetch/keyword-research-mcp

Claude Code

claude mcp add --transport http keyword-research "https://mcp.apify.com/?tools=fairfetch/keyword-research-mcp"

Then run /mcp in Claude Code, pick keyword-research and sign in to Apify (or run claude mcp login keyword-research).

Claude apps: Settings > Connectors > Add custom connector, then paste the URL.

Cursor (~/.cursor/mcp.json, or .cursor/mcp.json in a project):

"mcpServers": { "keyword-research": { "url": "https://mcp.apify.com/?tools=fairfetch/keyword-research-mcp" } } }

VS Code: run MCP: Add Server, choose HTTP and paste the URL, or add to .vscode/mcp.json:

"servers": { "keyword-research": { "type": "http", "url": "https://mcp.apify.com/?tools=fairfetch/keyword-research-mcp" } } }

Through this URL the tools appear as fairfetch--keyword-research-mcp--search_suggestions and so on. Apify's OAuth sign-in gives the client access to your Apify account (Apify's OAuth offers a single scope, full API access). Clients without a browser can send the header Authorization: Bearer to this URL instead.

Option 2: the server's own endpoint, with an Apify API token

For headless agents and SDKs. This endpoint accepts an Apify API token only (no OAuth sign-in). Get a token in Apify Console > Settings > API & Integrations and send it as Authorization: Bearer :

https://fairfetch--keyword-research-mcp.apify.actor/mcp

Claude Code

claude mcp add --transport http keyword-research https://fairfetch--keyword-research-mcp.apify.actor/mcp \

--header "Authorization: Bearer YOUR_APIFY_TOKEN"

Cursor:

"mcpServers": { "keyword-research": { "url": "https://fairfetch--keyword-research-mcp.apify.actor/mcp", "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" } } } }

VS Code (.vscode/mcp.json; VS Code asks for the token and stores it securely):

"inputs": [ { "type": "promptString", "id": "apify-token", "description": "Apify API token", "password": true } ], "servers": { "keyword-research": { "type": "http", "url": "https://fairfetch--keyword-research-mcp.apify.actor/mcp", "headers": { "Authorization": "Bearer ${input:apify-token}" } } } }

Here the tool names have no prefix (search_suggestions ...), and a misspelled argument gets a free error that names it. Apify's hosted server (option 1) drops arguments a tool doesn't declare before it calls this server.

Data sources

Tool	Source
`search_suggestions`	Google's and YouTube's suggestion service (the one Chrome's address bar uses) and Bing's OpenSearch suggestions
`keyword_metrics`, `keyword_ideas`	DataForSEO Labs (Google): monthly Google Ads search volumes, CPC and bids from DataForSEO's keyword database, updated monthly; keyword difficulty and search intent are DataForSEO's estimates
Google Trends tools	Google Trends' public web endpoints, through Apify's residential proxy (see Legal)

Keyword metrics and ideas cover 94 countries (not China or Russia); autocomplete and Google Trends work for any country (Bing: 34 markets).

Legal

The tools read public search suggestions and Google Trends statistics, and keyword statistics retrieved through the DataForSEO API. They do not log in anywhere or solve CAPTCHAs, and they collect no personal data. Suggestions and trending searches are generated from what many people search for and can include names of public figures and, rarely, other text you should handle with care.

How the Google Trends tools reach Google. Their requests go through Apify's residential proxy (Apify's datacenter proxy if residential isn't available) with a Chrome browser User-Agent, one at a time per IP address and about a second apart. When Google throttles a request (HTTP 429 or 403, or a redirect to its "unusual traffic" page), the request is retried from another IP address, up to 5 times. If neither proxy is available, the requests come from the server's own IP address instead, about 5 seconds apart, and a throttled request waits up to about a minute before each retry. Each IP address is also replaced after 30 requests, so that no single address carries a long series of requests. Google's cookies are kept when the IP address changes, and a connection whose cookie is still new can be given a cookie that Google has already accepted on another of the tools' connections. trends.google.com's robots.txt disallows only its /explore pages (/explore? and /trends/explore?), not the endpoints these tools use (/trends/api/..., /_/TrendsUi/data/batchexecute and /trending/rss).

The services' terms restrict automated access and reuse:

Google and YouTube (suggestqueries.google.com, which has no robots.txt; trends.google.com): Google's Terms of Service prohibit automated access that ignores machine-readable instructions such as robots.txt, and YouTube's Terms of Service prohibit automated access without YouTube's prior written permission (except for public search engines).
Bing (api.bing.com, whose robots.txt does not load): the Microsoft Services Agreement says the text and other material available on Bing and MSN is for noncommercial, personal use only, and that using it to build your own products is allowed only as far as Microsoft or the rights holders specifically authorize (section 14.f.i, "Bing and MSN Materials"). It also prohibits circumventing restrictions on access to its services, including "impermissible scraping" (section 3.a.vi).

Amazon, eBay and DuckDuckGo autocomplete are not offered: their robots.txt or terms exclude automated or AI-agent access. You are responsible for how you use the data and for complying with the terms of these services and the laws that apply to you.

Not affiliated with or endorsed by Google, YouTube, Microsoft/Bing, DataF

Only the beginning is shown; read the rest in the repo

Keyword Research MCP: autocomplete, search volume, difficulty and Google Trends

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Keyword Research MCP: autocomplete, search volume, keyword difficulty and Google Trends for AI agents

Tools and prices

Cost control: read this before giving an agent these tools

Connect

Option 1: Apify's hosted MCP server (sign in with Apify, no token to copy)

Option 2: the server's own endpoint, with an Apify API token

Data sources

Legal