Koskamo

Apify Google Keyword Research MCP

An MCP server that integrates the Apify Google Keyword Research Actor, allowing AI agents to extract keyword ideas from Google Autocomplete, People Also Ask, and related searches for SEO and content planning.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Apify Google Keyword Research MCP logo, by ApifyCommunity listingStreamable HTTPOAuth sign-inEndpoint checked 2026-11-09Published by Apify
MCP endpoint (Streamable HTTP)
https://mcp.apify.com/?tools=fguiraud/google-keyword-research
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Find long-tail keywords for specific topics
  • Extract questions from People Also Ask
  • Analyze search intent for SEO
  • Generate keyword ideas via Autocomplete

Source and maintenance

Community listingRegistry 1.0.0
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-09: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
142 ms
95th percentile latency
142 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 142 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http google-keyword-research-mcp https://mcp.apify.com/?tools=fguiraud/google-keyword-research

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add google-keyword-research-mcp --url https://mcp.apify.com/?tools=fguiraud/google-keyword-research

Cursor

Merge this server into .cursor/mcp.json in your project, then enable google-keyword-research-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "google-keyword-research-mcp": {
      "url": "https://mcp.apify.com/?tools=fguiraud/google-keyword-research"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "google-keyword-research-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.apify.com/?tools=fguiraud/google-keyword-research",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start google-keyword-research-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "google-keyword-research-mcp": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=fguiraud/google-keyword-research"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http google-keyword-research-mcp https://mcp.apify.com/?tools=fguiraud/google-keyword-research

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.apify.com/?tools=fguiraud/google-keyword-research

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "google-keyword-research-mcp": {
      "serverUrl": "https://mcp.apify.com/?tools=fguiraud/google-keyword-research"
    }
  }
}

Let your agent find its tools

Find servers like Apify Google Keyword Research MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.