Install SEO Gets MCP

Try these steps:

• Check that your JSON syntax is valid (no missing commas or brackets)

• Make sure all file paths are absolute, not relative

• Run your server command directly in a terminal to check for errors

• Verify you fully quit and restarted Claude Desktop

If you've added the config but SEOGets isn't showing under Settings → Customize, try these fixes:

1. Check the config file location. On Windows, make sure you're editing the correct file: %APPDATA%\Claude\claude_desktop_config.json. If you have multiple Claude installations or profiles, you may be editing the wrong one.

2. Verify your JSON is valid. Even a single missing comma or extra bracket will break the config. Paste your config into a JSON validator to catch syntax errors.

3. Force a full restart. Closing the Claude window isn't enough—right-click Claude in your taskbar and select Quit, then reopen. On macOS, use ⌘Q or right-click the dock icon and select Quit.

4. Check the logs. Look at mcp.log in your Claude logs folder for errors. If you see "server not found" or connection failures, the config may not be loading correctly.

If SEOGets shows up under Settings → Customize but Claude still doesn't query SEO Gets when you ask questions, here's what to check:

1. Be specific in your prompt. Claude won't automatically route every question through SEO Gets. Try prompts like: "Using my SEO Gets data, show me top pages for example.com last month" or "What are my striking distance keywords according to SEO Gets?"

2. Set permissions to Always Allow. Go to Settings → Customize, find SEOGets under Desktop, and set each tool to Always Allow. This removes the approval prompt, but note that it doesn't force Claude to use SEO Gets for every question—you still need to reference it in your prompt.

3. Check the MCP logs. Look in %APPDATA%\Claude\logs\mcp.log (Windows) or ~/Library/Logs/Claude/mcp.log (macOS) for errors. If the log shows connection failures or authentication issues, verify your API key is correct and hasn't been revoked.

4. Verify your key is still valid. Go to Settings → API & MCP Keys in SEO Gets and confirm your MCP key exists. If you're unsure, create a new key and update your claude_desktop_config.json.

These errors usually mean the MCP server isn't running or can't be reached. Here's how to debug:

1. Verify Node.js is installed. Open a terminal and run node --version. If you get "command not found," install Node.js from nodejs.org.

2. Check if the server starts manually. Open a terminal and run the server command directly. If you see errors about missing packages or permissions, fix those first.

3. Confirm your MCP key is valid. Go to Settings → API & MCP Keys in SEO Gets and verify the key you created is still listed. If you're not sure, create a new key and update your config.

4. Check your network. If you're behind a corporate firewall or VPN, the MCP server may be blocked. Try connecting from a different network to rule this out.

Claude Desktop logs MCP connection details to help you debug issues:

• macOS: ~/Library/Logs/Claude/

• Windows: %APPDATA%\Claude\logs\

Look for mcp.log for general connection logs and mcp-server-SERVERNAME.log for server-specific errors.

This means the environment variable isn't expanding correctly. Add it to your claude_desktop_config.json in an env block:

{
  "mcpServers": {
    "your-server": {
      "command": "...",
      "args": [...],
      "env": {
        "APPDATA": "C:\\Users\\yourname\\AppData\\Roaming"
      }
    }
  }
}

On Windows, paths with spaces (like C:\Program Files\) can cause issues if not escaped properly. You have two options:

Option 1: Use forward slashes — Windows accepts forward slashes in most cases:

"C:/Users/Your Name/AppData/Roaming"

Option 2: Escape backslashes — Double every backslash:

"C:\\Users\\Your Name\\AppData\\Roaming"

Avoid single backslashes in JSON—they'll break the config.

If Claude Desktop logs show "npx: command not found" or similar, Node.js isn't in your PATH.

1. Reinstall Node.js from nodejs.org and make sure you check Add to PATH during installation.

2. After installing, restart your computer to ensure PATH changes take effect.

3. Open a new terminal and run npx --version to confirm it works.

If npx still doesn't work, you may need to use the full path to Node.js in your config:

"command": "C:\\Program Files\\nodejs\\npx.cmd"