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
Method 1: Via Connectors
No coding, no config files. Just paste the endpoint URL in your AI client's settings.
https://mcp.keywordtool.io
| AI Client | Setup Instructions |
|---|---|
|
|
Settings → Connectors → Add custom connector |
|
|
Profile (bottom-left) → Settings → Connectors → Add custom connector |
|
|
Settings → Apps & Connectors → Advanced → enable Developer Mode → Connectors → Create |
|
|
Account Settings → Connectors → Add Connector |
Method 2: 1-Click Install
Click to auto-configure Keyword Tool in your editor. No file editing needed.
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.
Method 4: Config File
Add this JSON to your AI client's MCP configuration file.
Requires Node.js. Config-file methods use npx to run a bridge program. Install Node.js if you don't have it.
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 |
|---|---|
|
|
~/Library/Application Support/Claude/claude_desktop_config.json (macOS)%APPDATA%\Claude\claude_desktop_config.json (Windows)
|
|
|
~/.cursor/mcp.json (global) or .cursor/mcp.json (project)
|
|
|
.vscode/mcp.json (workspace) or Command Palette → MCP: Open User Configuration
|
|
|
~/.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
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.iodirectly in your terminal to see error output
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-authfolder 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
- 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
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.
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.
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-remoterequires. - Windows can't find npx: GUI applications on Windows often can't locate
npxbecause 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 yourargsarray.
Or use the Connectors method (Method 1) which doesn't require you to install Node.js.
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.
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
30-Day Money-Back Guarantee · Cancel Anytime
Just want to try it? Set up the free version (no signup required).