Install SEO Gets MCP

If SEO Gets isn't showing up after setup:

• Check your plan. MCP is only available on Core and Pro plans. Free plan users will see a subscription prompt instead of the connector.

• Complete the consent flow. Make sure you finished all authorization steps after saving the connector.

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

If SEO Gets is listed but Claude still doesn't query your data:

1. Be specific in your prompt. Claude won't automatically route every question through SEO Gets. Try: "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 SEO Gets, and set each tool to Always Allow. This removes approval prompts, but you still need to reference SEO Gets in your prompt.

MCP access requires a paid plan. If you're on the Free plan, you'll see a subscription message when the MCP tools try to run. Upgrade to a Core or Pro plan to restore access. You can change your plan from Billing settings.

Claude doesn't let you edit a connector directly — you remove the old one and add it again with updated details. That's why an old local or remote SEO Gets entry can block a fresh install.

• Remote connector: In Claude, go to Customize → Connectors, find SEO Gets, and choose Remove from the three-dot menu. Team owners remove organization-level connectors from Organization settings → Connectors.

• Old manual local setup: If you configured SEO Gets through the manual Claude Desktop method, the connection lives in claude_desktop_config.json under mcpServers. Delete the SEOGets block, save the file, and quit and restart Claude Desktop completely for the change to take effect.

Then add the connector again with the name SEO Gets and server URL https://app.seogets.com/mcp, and complete the consent flow.

In Claude Team and Enterprise organizations, only the Owner or Primary Owner can add a custom connector. If adding SEO Gets fails for you, have your team owner install it.

1. Ask the owner to open Organization settings → Connectors, click Add → Custom → Web, and enter SEO Gets with server URL https://app.seogets.com/mcp.

2. Once it's added, connect to it yourself from Customize → Connectors using Browse, as described in the Connect to an existing SEO Gets connector section above.

Each team member authorizes the connector individually through the consent flow.

The consent step signs you into SEO Gets and asks you to approve access, and it only approves the connector you just added.

• Sign in to SEO Gets first. The consent step redirects to SEO Gets sign-in before showing the approval screen, so sign in and let the flow continue.

• Approve only fresh prompts. If you see a consent prompt at any other time than right after adding the connector, don't approve it — remove and re-add the connector instead.

• Retry after an error. If you see "Something went wrong. Please try again.", open the Custom Connector settings again and repeat the save and consent steps.

When a working connector stops, check the plan, the property, the connector's conversation status, and the network — in that order.

1. Check your plan. The MCP server refuses requests when your SEO Gets team is on the Free plan. If your subscription lapsed, renew it and try again.

2. Check the property. Ask with your exact property name, like "show me top pages for example.com last month". If Claude says you don't have read access or no property matches, check your Google connection and property permissions in Why can't I see my GSC data even with permissions granted?

3. Re-enable the connector for the conversation. Claude activates connectors per conversation. Open the + menu, choose Connectors, and make sure SEO Gets is enabled with its tools set to Always Allow.

4. Check the network. The connector runs from Anthropic's cloud and must reach https://app.seogets.com/mcp. A corporate firewall or VPN can break a working connection, so try from a different network.

If Claude itself shows a connector error, the issue is on Claude's side: remove SEO Gets in Customize → Connectors and add it again with the same name and URL, then complete the consent flow.

This method requires Node.js and manual editing of Claude Desktop's configuration file.

Step 1: Create an MCP key

1. Login to SEO Gets

2. Navigate to Settings → MCP

3. Name your MCP Key and click Create Key

4. Once your key is generated, click Copy and paste it somewhere safe as it won't be shown again.

Step 2: Install Node.js

Install Node.js, which is required to run the MCP server. If you don't have it yet, download and install it from nodejs.org.

Step 3: Configure Claude Desktop

Open the configuration file directly from Claude Desktop:

1. Click Claude in your menu bar (macOS) or go to the app menu (Windows)

2. Select Settings

3. Click the Developer tab

4. Click Edit Config to open the configuration file

The config file is located at:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\\Claude\\claude_desktop_config.json

Add the SEO Gets MCP server under mcpServers:

{
  "mcpServers": {
    "SEOGets": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://app.seogets.com/mcp",
        "--header",
        "Authorization: Bearer ${API_KEY}"
      ],
      "env": {
        "API_KEY": "REPLACE_WITH_YOUR_KEY"
      }
    }
  }
}

Step 4: Restart Claude Desktop

Completely quit and restart Claude Desktop for the new configuration to take effect.

1. Right-click Claude in your dock/taskbar and select Quit

2. Reopen Claude Desktop

Step 5: Verify

Navigate to Settings → Customize to see if SEOGets is listed as a connector under Desktop.

Manual setup troubleshooting

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

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

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

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