JetBrains MCP: how to connect Graphify
By Steven Van ·
Install the free plugin in a 2025.3 JetBrains IDE and AI Assistant can query repositories already indexed in Graphify Cloud, with browser sign-in.
Graphify MCP is now on the JetBrains Marketplace, so JetBrains AI Assistant can query a repository already indexed in Graphify Cloud. The setup guide says the plugin is listed as free, uses no API key, and does not upload the open project or build the graph locally. It connects to the hosted server at https://api.graphify.com/mcp. Graphify Labs publishes it under the id com.graphify.graphify-mcp.
What is needed first
- A JetBrains IDE on the 2025.3 release. The plugin accepts platform build 253 through 253.*, so it does not install on 2025.2 or a later release.
- JetBrains AI Assistant, with access to MCP.
- A repository indexed in Graphify Cloud, with status Indexed under Repositories and builds.
- Node.js and npm on the IDE's PATH, only for the browser sign-in. The direct connection does not need them.
Connecting
After installing Graphify MCP (Settings, then Plugins), open View, then Tool Windows, then Graphify. From there you pick a sign-in method and click Copy configuration. The window also opens IDE settings, the workspace and the setup guide.
- Browser sign-in: runs mcp-remote@0.14.3 through npx, which opens a browser for Graphify sign-in and stores credentials on the machine. Use it when AI Assistant cannot sign in to a remote server by itself.
- Direct connection: a plain URL entry for clients that can finish Graphify's sign-in themselves. If the browser never opens, switch to the bridge configuration.
Paste the JSON under Settings, then Tools, then AI Assistant, then Model Context Protocol (MCP). Click Add, choose this project or every project, then click OK and Apply. The separate Tools, then MCP Server page is for letting other applications use the IDE, so the configuration does not go there.
Asking questions
Once the MCP settings show the server connected, "List my Graphify repositories." is the suggested first prompt. Follow-ups include finding a function's implementation, or asking what calls a symbol and which tests are linked to it. The guide advises opening any cited file before relying on an answer. Some tools save notes on a repository or change the selected workspace, so requests should be read before approving.
If it fails
The guide lists three fixes. If npx or Node.js is missing, install both and restart the IDE. If an empty repository list comes back, the repository is not yet indexed or sits in another workspace. If the direct connection never signs in, use the bridge configuration. A graph kept on the local machine is a separate setup under Graphify MCP.
