Google Keyword Volume & Difficulty MCP server

How an agent would call it

Two steps: search returns refs, then data_fetch opens one of them. The arguments below are the arguments that were sent.

{
  "tool": "search",
  "arguments": {
    "query": "project management software",
    "sources": [
      "google-keywords"
    ],
    "limit": 2,
    "runId": "<from run_begin>",
    "config": {
      "country": "us",
      "language": "en"
    }
  }
}

{
  "tool": "data_fetch",
  "arguments": {
    "sourceId": "google-keywords",
    "ref": {
      "id": "project management software"
    },
    "runId": "<from run_begin>"
  }
}

This runs against an account — send Authorization: Bearer <token> with the call. Get one at app.bedrocktap.com/dashboard/tokens; the free tier needs no card, and it reaches google-keywords like every other source.

What it costs. 6 credits per keyword row returned; a fetch costs nothing, because the row is complete when the search returns it. The search above returned 2 rows and cost 12 credits.

What came back

{
  "ref": {
    "id": "project management software",
    "title": "project management software"
  },
  "text": "project management software: 135000 searches/month, competition 0.03",
  "fetchedAt": "2026-09-12T15:03:18.707Z"
}

Each keyword row carried volume, competition and cpc in its meta. The seed term returned 135,000 monthly searches at a competition score of 0.03; the second row, "project management software ranking", returned 10 — four orders of magnitude apart, which is the whole reason to ask before writing the page. A trend series is carried where the row has one.

Observed 2026-09-12. One call against a live source — ask again tomorrow and the rows move.

What a row contains

One row is one keyword: the phrase itself as both id and title, and meta carrying its monthly search volume, a competition score and a cost-per-click figure. There is no URL, because a keyword is not a page. Volumes are banded estimates rather than counts — treat a figure as an order of magnitude, which is all the planner data behind it claims to be. Set country and language on the call to move the locale.

A question it answers. How many people search for this every month, and what do they type instead?

Routing guidance

What an agent reads to decide whether google-keywords is the right source, and what to reach for when it is not.

Answers

The default choice for keyword volume. One seed keyword at a time, expanded into related suggestions with metrics.

Query shape

A single plain keyword. Do NOT pass a pipe-separated batch — that is `google-keywords-bulk` syntax, and this source will read it as one literal keyword.

Price

Priced in credits, per row, per query or per call depending on the source. Every call is quoted before it runs — `cost_estimate` returns the exact figure and spends nothing. See /pricing.

Latency

Fast.

Prefer instead

`google-keywords-bulk` from roughly 25 keywords upward: it bills one flat call for up to 1,000 keywords, where this bills per keyword. Below that threshold this is much cheaper.

Cannot answer

Live rankings (use `google-serp`), AI-engine citations (use `ai-visibility` or `grounded-answers`), or backlinks — no source here provides them.

Related sources