Available Only to Keyword Tool Pro Subscribers

Connect Keyword Tool To Your AI

Your Keyword Tool Pro subscription gives your AI full access to keyword suggestions, search volume, and competitor analysis through MCP. Set it up in minutes. Your AI gets the same real data you use in the web interface.

MCP Server Endpoint:

https://mcp.keywordtool.io
Easiest

Method 1: Via Connectors

No coding, no config files. Just paste the endpoint URL in your AI client's settings.

1 Open your AI client's Connectors or MCP settings (see table below for the exact menu path)
2 Add a new connector and paste this URL:
https://mcp.keywordtool.io
3 Authorize the connection - a browser window will open to log in with your Keyword Tool Pro account.
AI Client Setup Instructions
Claude Claude Desktop Settings → Connectors → Add custom connector
Claude claude.ai Profile (bottom-left) → Settings → Connectors → Add custom connector
ChatGPT ChatGPT Settings → Apps & Connectors → Advanced → enable Developer Mode → Connectors → Create
Perplexity Perplexity Account Settings → Connectors → Add Connector
1-Click

Method 2: 1-Click Install

Click to auto-configure Keyword Tool in your editor. No file editing needed.

1 Command

Method 3: Terminal Command

For Claude Code - run a single command to add Keyword Tool.

claude mcp add-json keywordtool '{"command":"npx","args":["-y","mcp-remote","https://mcp.keywordtool.io"]}'

On first use, a browser window opens for authorization. Tip: Add --scope user to make it available across all projects.

Manual

Method 4: Config File

Add this JSON to your AI client's MCP configuration file.

Standard config (Claude Desktop, Cursor, Windsurf, and most clients)

{
  "mcpServers": {
    "keywordtool": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.keywordtool.io"
      ]
    }
  }
}

VS Code + Copilot (uses servers instead of mcpServers)

{
  "servers": {
    "keywordtool": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.keywordtool.io"
      ]
    }
  }
}

Windsurf (uses serverUrl instead of command)

{
  "mcpServers": {
    "keywordtool": {
      "serverUrl": "https://mcp.keywordtool.io"
    }
  }
}

Config file locations

AI Client Config File
Claude Desktop ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
%APPDATA%\Claude\claude_desktop_config.json (Windows)
Cursor ~/.cursor/mcp.json (global) or .cursor/mcp.json (project)
VS Code .vscode/mcp.json (workspace) or Command Palette → MCP: Open User Configuration
Windsurf ~/.codeium/windsurf/mcp_config.json

After editing, restart your AI client for changes to take effect. An OAuth window will open on first use - log in with your Keyword Tool Pro account.

More AI Clients

Any MCP-compatible client can connect to Keyword Tool. Use the Connectors method if your client supports it, or add the config file JSON above.

Client Config File Docs
OpenAI Codex CLI ~/.codex/config.toml Docs
Cline cline_mcp_settings.json Docs
Gemini CLI ~/.gemini/settings.json Docs
JetBrains AI Settings → Tools → MCP Server Docs
Amazon Q Developer VS Code / JetBrains plugin settings Docs
Continue.dev config.yaml Docs
Zed settings.json Docs
Roo Code .roo/mcp.json Docs

Troubleshooting

I clicked "Add to Cursor" or "Install in VS Code" but nothing happened
Your browser may be blocking the deep link from opening an external app. Try clicking again and look for an "Open Cursor?" or "Open Visual Studio Code?" popup in your browser's address bar. Some browsers require you to allow the link the first time. If that doesn't work, use the Config File method (Method 4) instead.
My terminal says "command not found: npx" when I try to set up MCP
You need Node.js installed (version 18 or later). This is only required for the Config File and Terminal methods - Connector-based setups (Method 1) don't require you to install Node.js. After installing, verify with node --version.
I set everything up but my AI client doesn't show any Keyword Tool tools

Each client surfaces MCP tools differently:

  • VS Code: You must switch to Agent mode in the Copilot chat panel - MCP tools are invisible in Ask or Edit mode
  • Claude Desktop: Fully quit and reopen the app (just closing the window is not enough - check your system tray or Activity Monitor)
  • Perplexity: Toggle the MCP source on under Sources in your conversation
  • Config file users: Validate your JSON syntax - a single missing comma will silently break it. Try running npx -y mcp-remote https://mcp.keywordtool.io directly in your terminal to see error output
A browser window opened asking me to log in, but the connection still shows as disconnected

This is the OAuth authorization flow. After you approve the connection in the browser, switch back to your AI client - it should now be connected. If it still shows disconnected:

  • Remove the connector, clear the .mcp-auth folder in your home directory, and add it again
  • Check if an ad blocker or privacy extension is blocking the OAuth callback
  • Make sure you are logging in with an active Keyword Tool Pro subscription
I'm seeing "connection refused", "timeout", or "HTTP 400" errors
  • Check the endpoint URL has no typos or trailing slash
  • If you are behind a corporate VPN or firewall, try disabling it temporarily - some networks block outbound MCP connections
  • If using mcp-remote, make sure you are on Node.js 18+ (older versions are missing required APIs like TransformStream)
  • The server may be temporarily unavailable - try again in a few minutes
MCP was working but stopped after I closed my laptop or switched networks

The mcp-remote bridge can lose its connection after laptop sleep/resume or network changes. Restart your AI client to reconnect. If this happens frequently, clear the auth cache by deleting the .mcp-auth folder in your home directory, then reconnect. Using the Connectors method (Method 1) instead of config files avoids this issue entirely since the client manages the connection.

I upgraded to Keyword Tool Pro but my AI is still returning limited results

You likely still have the free Guest MCP endpoint configured alongside the Pro endpoint. Remove the Guest configuration and keep only the Pro endpoint. When both are active, your AI may unpredictably choose the Guest version. In Claude Desktop, check Settings → Connectors for duplicate entries.

I'm on Windows and getting "spawn npx ENOENT" or similar errors

This is a known Windows issue. There are two common causes:

  • Node.js version too old: Upgrade to Node.js 18 or later from nodejs.org. Older versions are missing APIs that mcp-remote requires.
  • Windows can't find npx: GUI applications on Windows often can't locate npx because it's a batch script (.cmd), not a binary. Fix by changing "command": "npx" to "command": "cmd" and adding "/c", "npx" to the start of your args array.

Or use the Connectors method (Method 1) which doesn't require you to install Node.js.

What is the difference between the Connectors method and the Config File method?

Both connect to the same Keyword Tool data. Connectors (Method 1) is the easiest - you paste a URL in your AI client's settings, no coding or Node.js needed. Works with Claude Desktop, claude.ai, ChatGPT, and Perplexity. Config File (Method 4) requires editing a JSON file and installing Node.js, but works with any MCP-compatible client. If your AI client supports Connectors, use that.


Already set up the free guest endpoint? If you previously configured /mcp/guest, remove it before adding the Keyword Tool Pro endpoint. Enable only one at a time. When both are active, your AI may unpredictably choose the guest version, which gives you limited results.

What Is Included With Keyword Tool Pro

Full Keyword Tool access through your AI assistant.

Plan-based requests/day (up to 400 on Agency)
100% accurate search volume data from Google and Bing
Historical data (depending on your plan)
Web Interface, MCP and API (one quota pool)
All 15 platforms
Cost per click & competition, trends, device breakdown

Manage Your MCP Connections

You can view, create, or revoke OAuth clients at any time from your MCP Settings page. If you need to switch accounts, clear the local auth cache and reconnect.

Not Subscribed Yet?

Get Full MCP Access With Keyword Tool Pro

One subscription. Full access through the web interface, API, and MCP.

Your AI gets the same real keyword data you do.

  • Plan-based requests/day and search volume data for up to 400,000 keywords/day
  • 100% accurate search volume data from Google Keyword Planner and Bing Keyword Planner
  • Historical data, cost per click & competition, trends, device breakdown
  • Web Interface, MCP and API included in every plan
  • All 15 platforms
Subscribe Now

30-Day Money-Back Guarantee · Cancel Anytime

Just want to try it? Set up the free version (no signup required).