Integration Guides8 min read

MCP Integration Guide: JetBrains IDEs (IntelliJ, PyCharm, WebStorm) in 2026

Step-by-step guide to configuring MCP servers in JetBrains IDEs. Learn how to set up Model Context Protocol in IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains tools for AI-powered development.

By MyMCPTools Team·

JetBrains IDEs — IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider, and others — are the tools of choice for millions of professional developers. With JetBrains' native MCP support, you can connect these IDEs to any MCP server, giving your AI coding assistant access to databases, repositories, issue trackers, and more directly inside your development environment.

This guide walks through the complete setup process for MCP in JetBrains IDEs, from installation to advanced configuration.

Prerequisites

  • JetBrains IDE version 2024.2 or later (MCP support requires the AI Assistant plugin)
  • JetBrains AI Assistant subscription (available via JetBrains Toolbox or IDE settings)
  • Node.js 18+ or Python 3.10+ installed (required for most MCP servers)

Step 1: Enable the AI Assistant Plugin

MCP support in JetBrains IDEs is provided through the AI Assistant plugin. To enable it:

  1. Open your JetBrains IDE (IntelliJ, PyCharm, WebStorm, etc.)
  2. Go to Settings / Preferences → Plugins
  3. Search for "AI Assistant" in the Marketplace tab
  4. Click Install, then restart the IDE
  5. After restart, sign in to your JetBrains account when prompted

If you already have the AI Assistant plugin installed, verify you're running version 2.0 or later — MCP support was added in this release.

Step 2: Access MCP Server Configuration

JetBrains stores MCP server configuration in the AI Assistant settings:

  1. Open Settings / Preferences (Ctrl+Alt+S on Windows/Linux, ⌘, on macOS)
  2. Navigate to Tools → AI Assistant → Model Context Protocol (MCP)
  3. You'll see the MCP server configuration panel with an "Add Server" button

Alternatively, MCP servers can be configured via the mcp.json configuration file, which JetBrains IDEs read from the same location as Claude Desktop:

  • macOS: ~/Library/Application Support/JetBrains/AIAssistant/mcp.json
  • Windows: %APPDATA%\JetBrains\AIAssistant\mcp.json
  • Linux: ~/.config/JetBrains/AIAssistant/mcp.json

Step 3: Configure Your First MCP Server

The filesystem MCP server is the recommended starting point — it gives the AI Assistant access to your project files beyond what's already indexed by the IDE.

In the MCP configuration panel, click Add Server and enter:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/your/projects"
      ]
    }
  }
}

Replace /path/to/your/projects with the root directory of your project workspace. You can specify multiple directories:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/yourname/projects",
        "/Users/yourname/documents"
      ]
    }
  }
}

Step 4: Add the GitHub MCP Server

For developers using GitHub, the GitHub MCP server dramatically improves the AI Assistant's ability to reason about issues, PRs, and code changes across your repositories.

First, create a GitHub Personal Access Token with repo and read:org scopes at github.com/settings/tokens.

Then add to your MCP configuration:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/your/projects"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

With this configured, you can ask the AI Assistant things like "What's the status of PR #847?" or "Create an issue for the bug I just found" directly from the IDE chat.

Step 5: Add a Database MCP Server

JetBrains IDEs already have excellent database tooling (DataGrip integration is built in), but the PostgreSQL MCP server gives the AI Assistant the ability to reason about your database schema when writing queries, generating migrations, or debugging data issues.

{
  "mcpServers": {
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"],
      "env": {
        "POSTGRES_CONNECTION_STRING": "postgresql://user:password@localhost:5432/mydb"
      }
    }
  }
}

Security note: The MCP PostgreSQL server defaults to read-only mode. Never use a superuser or write-access account for MCP — create a dedicated read-only database user for AI access.

Step 6: Add Jira or Linear for Issue Context

One of the most powerful JetBrains MCP configurations is connecting your issue tracker, so the AI Assistant can reference ticket requirements when you're implementing features or fixing bugs.

For Jira (requires API token from id.atlassian.com/manage-profile/security/api-tokens):

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-jira"],
      "env": {
        "JIRA_HOST": "https://yourcompany.atlassian.net",
        "JIRA_EMAIL": "you@yourcompany.com",
        "JIRA_API_TOKEN": "your_api_token"
      }
    }
  }
}

For Linear (requires API key from linear.app/settings/api):

{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-linear"],
      "env": {
        "LINEAR_API_KEY": "your_api_key"
      }
    }
  }
}

With an issue tracker connected, you can say "Implement the requirements from PROJ-1234" and the AI will pull the ticket description, acceptance criteria, and linked design specs directly into its context.

Complete Configuration Example

A typical professional developer setup with JetBrains MCP:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/dev/projects"
      ]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..."
      }
    },
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"],
      "env": {
        "POSTGRES_CONNECTION_STRING": "postgresql://readonly:pass@localhost:5432/appdb"
      }
    },
    "linear": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-linear"],
      "env": {
        "LINEAR_API_KEY": "lin_api_..."
      }
    }
  }
}

Using MCP in the AI Assistant Chat

Once configured, MCP servers appear as available tools in the AI Assistant chat panel (View → Tool Windows → AI Assistant). The AI automatically selects relevant MCP tools based on your prompts — you don't need to specify which server to use.

Effective prompts for JetBrains MCP workflows:

  • "What issues are assigned to me in Linear right now?" — Pulls your current sprint tasks
  • "Implement the feature described in LINEAR-456" — Reads the issue and generates code
  • "This query is slow — can you check the schema and suggest optimizations?" — Reads database schema to inform suggestions
  • "What changed in this repo since last week?" — Uses Git/GitHub MCP to summarize recent activity
  • "Write a migration for adding the columns described in this PR" — Combines GitHub + database schema context

IDE-Specific Notes

IntelliJ IDEA (Java/Kotlin)

The Maven and Gradle build tool integrations in IntelliJ work well alongside MCP — the AI can read your pom.xml or build.gradle via filesystem MCP to understand dependencies when answering questions about library versions or upgrade paths.

PyCharm (Python)

PyCharm users benefit most from combining filesystem MCP with the PostgreSQL server for data science and web development workflows. The AI can read your requirements.txt and cross-reference it with database schema when generating SQLAlchemy models.

WebStorm (JavaScript/TypeScript)

WebStorm's Node.js debugging integration pairs well with MCP — use the GitHub server to pull PR context and the filesystem server to navigate your component library when writing new features.

Troubleshooting

MCP server not appearing in AI Assistant: Restart the IDE after changing the MCP configuration file. JetBrains reads MCP config on startup.

"Command not found" errors: Ensure Node.js is installed and available in the system PATH. On macOS, if you installed Node via nvm, you may need to add the full path to the command field: /Users/yourname/.nvm/versions/node/v20.0.0/bin/node.

Database connection refused: Verify your PostgreSQL connection string is correct and that the database server allows connections from localhost. Check that SSL mode settings match your database configuration.

Token authentication failures: GitHub tokens expire. Regenerate at github.com/settings/tokens and update your MCP config. Jira API tokens don't expire but require the correct email-token pair.

Next Steps

With the core MCP servers running in JetBrains, explore the full MCP server directory for additional integrations relevant to your stack. Popular additions for JetBrains users include Jira for project management, Slack for team communication, and specialized language-server MCP tools for framework-specific assistance.

For other editor setups, see our guides on Cursor, VS Code, and Claude Desktop MCP integration.

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

💻

JetBrains

Work on your code with JetBrains IDEs: IntelliJ IDEA, PhpStorm, etc.

Local
💻

GitHub MCP Server

authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.

Auth required📘
💻

Git

Tools to read, search, and manipulate Git repositories. Full Git operations support.

Local
📁

Filesystem MCP Server

sandboxed read, write, edit, move and search access to an explicit whitelist of local directories, and it is the reference implementation most other filesystem MCP servers are modelled on. Shipped by Anthropic in the official modelcontextprotocol/servers monorepo (89,000+ stars, actively maintained), it is a Node.js server published to npm as @modelcontextprotocol/server-filesystem. The part worth understanding before you install is the access-control model, because there are now two ways to grant directories and they do not compose. Method one is command-line arguments: `npx -y @modelcontextprotocol/server-filesystem /path/one /path/two`. Method two, and the one the maintainers recommend, is MCP Roots — a client that supports the roots protocol sends its roots at initialization, and those roots COMPLETELY REPLACE any directories passed on the command line, then get replaced again on every `notifications/roots/list_changed`. That means allowed directories can change at runtime without restarting the server, but it also means a roots-capable client silently overrides your CLI arguments. If the server starts with no arguments and the client either does not support roots or sends an empty list, initialization throws an error. The tool surface is broad: `read_text_file` (with mutually exclusive `head`/`tail` line windows), `read_media_file` returning base64 image/audio content blocks, `read_multiple_files` which keeps going when individual reads fail, `write_file`, `edit_file`, `create_directory`, `list_directory`, `list_directory_with_sizes`, `move_file`, `search_files`, `directory_tree`, `get_file_info` and `list_allowed_directories`. `edit_file` is the one to learn — it does line-based and multi-line pattern matching with indentation detection and preservation, returns a git-style diff with context, and supports `dryRun: true` so you can preview a change before applying it; the maintainers recommend always running a dry run first. Every operation is refused outside the allowed set, and `list_allowed_directories` is the fastest way to confirm what the server actually believes it can touch.

Local
🗄️

PostgreSQL MCP Server

The PostgreSQL MCP server was the Model Context Protocol reference server for Postgres, and it is retired: the source now sits in modelcontextprotocol/servers-archived — a repository GitHub reports as archived, described as "Reference MCP servers that are no longer maintained" — and the npm package @modelcontextprotocol/server-postgres carries a deprecation notice reading "Package no longer supported." It still installs and still runs, which is why most third-party setup articles have not caught up. What it provides is deliberately small: a single tool, query, which executes read-only SQL inside a READ ONLY transaction, plus per-table schema information exposed as MCP resources at postgres://<host>/<table>/schema, with column names and data types discovered from database metadata. There is no index advice, no health check, no separate schema-listing tool, and no write mode. Install is npx @modelcontextprotocol/server-postgres with a postgres:// connection string as the argument. For active work against Postgres, the maintained alternative is Postgres MCP Pro (crystaldba/postgres-mcp), which exposes nine tools including index tuning against hypothetical indexes and a database health check, and has an explicit restricted access mode; if your database is hosted on Supabase or Neon, their platform servers add branching and logs that a raw Postgres connection cannot see. Reach for this archived server only when you want the smallest possible surface — one process, one read-only query tool, nothing else.

Local📘
📋

Jira MCP Server

The Jira MCP server is Atlassian's official Remote MCP Server, giving AI assistants like Claude and Cursor direct, enterprise-grade access to Jira Software project management through natural-language interactions. Powered by Atlassian's Teamwork Graph and hosted on Cloudflare infrastructure, it requires no local process to run — authentication is handled via OAuth 2.1, making it the most secure way to connect AI to Jira in corporate environments. With this MCP server, product managers, engineers, and team leads can ask their AI to create and update Jira issues, transition ticket statuses through workflow stages, search with JQL (Jira Query Language), summarize sprint progress, view open epics and their child issues, retrieve assignee workloads, and bulk-triage backlogs. AI assistants can connect sprints to related Confluence documentation through Atlassian's graph layer, giving richer context for planning and retros. Enterprise customers including AT&T, NVIDIA, and Pfizer use Atlassian's MCP integration in production. Connect from Claude Desktop via Settings > Connectors, or add it to Claude Code with: `claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2`. Cursor and Windsurf users add the remote URL to their MCP config file. No install command needed — it's a fully hosted remote MCP server.

Auth required📘
📋

Linear MCP Server

The Linear MCP server connects your AI assistant directly to Linear's project management platform via an officially hosted remote endpoint at mcp.linear.app — no local installation required. This is Linear's own first-party server, authenticated with OAuth 2.1 and centrally managed so you always run the latest version without updates. Available tools let you search issues by keyword, team, cycle, or filter; create new issues with title, description, and assignee; update status, priority, labels, and comments; and navigate Linear's project and cycle structure. In Claude Code, add it with: `claude mcp add --transport http linear-server https://mcp.linear.app/mcp`, then run /mcp to complete the OAuth flow. For older clients, use the mcp-remote bridge for backwards compatibility. Claude Desktop and Claude.ai users can connect via Settings > Connectors. Cursor and Codex have native support via their MCP config. Linear is used by thousands of engineering and product teams to plan, track, and ship software — the Linear MCP server brings that data into every AI-powered workflow without copy-paste or context-switching.

Auth required📘

📚 More from the Blog