ContextBolt SEO in JetBrains IDEs (2026 Setup)

JetBrains IDEs were among the last major editors to get full streamable HTTP support, which meant JetBrains users spent a long time watching the MCP ecosystem from the outside. That gap has closed. AI Assistant now connects to remote MCP servers over streamable HTTP directly, so ContextBolt SEO works in IntelliJ IDEA, WebStorm, PyCharm, PhpStorm, GoLand, RubyMine, and Rider with one config entry and no bridge.

One config, every IDE

Use https://seo.contextbolt.app/mcp and complete the browser sign-in if your client supports remote MCP with OAuth. Enter your SEO account email and email code, then allow the connection. For a client that cannot complete that flow, use the personal-URL compatibility configuration shown here. Copy the full private URL from your ContextBolt SEO welcome email and replace the example URL with it.

The MCP panel lives inside AI Assistant rather than in any individual IDE, which is genuinely useful if you work across several. The same server entry lights up WebStorm for front-end work and PyCharm for the backend, and you configure it once.

Go to Settings, then Tools, then AI Assistant, then Model Context Protocol (MCP), and click Add:

{
  "mcpServers": {
    "contextbolt-seo": {
      "type": "streamable-http",
      "url": "https://seo.contextbolt.app/mcp/YOUR_TOKEN",
      "headers": {}
    }
  }
}

Because your token sits in the URL path, the headers block stays empty. It is there for servers that expect a bearer token instead.

The hyphen that breaks configs

JetBrains expects streamable-http. Goose expects streamable_http. VS Code just wants http. All three describe the same transport, which means a config copied from a working setup in another tool looks entirely correct and quietly does nothing.

If you have pasted a config and the tools never appear, check that value before you check anything else. It accounts for most failed JetBrains MCP setups.

Recent releases also added auto-reconnect across all transports, so a dropped network connection no longer means re-adding the server by hand.

What this changes for backend-heavy teams

JetBrains users tend to be underserved by MCP content, because the ecosystem writes for VS Code and its forks. The practical effect is that SEO work gets done somewhere else entirely, in a dashboard, by a different person, usually after the page has shipped.

Having the tools in the IDE moves that decision earlier. You are building a marketing page in WebStorm, you ask what it should target, and you write the copy against a real query instead of a guess. When it ships, you ask for an audit and fix what comes back in the same session.

Plan before you build: keyword research and difficulty scoring, while the file is open.

Audit after you ship: point page_audit at the live URL and work the fix list.

Read your own data free: the Search Console tools never spend credits, so checking what moved this month costs nothing.

The full tour is in the ContextBolt SEO guide, and the background on how an SEO MCP server works is worth ten minutes before you set one up.