Graphify MCP for VS Code

The Graphify MCP extension registers Graphify’s hosted MCP server in VS Code. Your agent can then search the repositories you have indexed in Graphify Cloud, follow callers and dependencies, and judge what a change reaches. VS Code handles the sign-in, the server trust prompt, and every tool approval. There is no API key to paste and no local process to run.

Before you start

VS Code 1.102 or later.
An agent chat model available in VS Code. The extension does not include one.
A repository indexed in your Graphify workspace. Sign in at app.graphify.com, connect a repository, and wait for its status to reach Indexed. See Repositories and builds.

1. Add the MCP server

Install the extension
Add the endpoint by hand

Install Graphify MCP from the Visual Studio Marketplace, or search for Graphify MCP by Graphify Labs in the Extensions view.The extension registers https://api.graphify.com/mcp over Streamable HTTP. It does not read or upload your local files, and it stores no credentials of its own.

Open the Command Palette (Ctrl + Shift + P, or Cmd + Shift + P on macOS) and run MCP: Open User Configuration. Add the server to mcp.json:

{
  "servers": {
    "graphify": {
      "type": "http",
      "url": "https://api.graphify.com/mcp"
    }
  }
}

Use one path or the other. If you keep this entry and also install the extension, the same tools appear twice.

Start it

Run MCP: List Servers from the Command Palette and select Graphify, then start the server.

Authorize

Your browser opens so you can sign in to Graphify and grant access. Choose the workspace that holds the repository you want to query.

Confirm the tools loaded

Return to MCP: List Servers and check that Graphify is running. Open an agent chat and enable Graphify’s tools.

3. Ask a question

Start by confirming what the connection can see:

List the repositories I can query with Graphify.

Then pick a repository from the answer and ask about its code:

Who calls the function that validates a session token?
Show me how a request reaches the database in this repository.
What does this change affect?
Which tests cover the billing module?
Remember that the retry limit lives in the queue worker.

Answers are graph evidence from the files Graphify indexed, not a verified result. Open the source lines an answer cites before you rely on it. Some tools write workspace memory or switch the selected workspace. Read each tool request and approve it only when that is what you meant.

Commands

Command	What it does
Graphify: Open Dashboard	Opens your workspace in the browser.
Graphify: Open MCP Documentation	Opens the setup instructions and tool reference.

If something fails

What you see	What to do
Graphify is not in MCP: List Servers	Check that VS Code is 1.102 or later, then reload the window.
The tools return nothing for a repository	That repository is not indexed yet, or it is in a different workspace. Check its status in Repositories and builds.
The agent reports an authorization problem	Stop the server in MCP: List Servers, start it again, and complete the browser sign-in.
Every Graphify tool appears twice	You have both the extension and a manual `mcp.json` entry. Remove one.
No tools appear in chat	No agent model is available, or Graphify’s tools are switched off for that chat.

Agents and integrations

Connect other clients from the Cloud workspace and manage its integrations.

Connect the graph MCP server

Run a local MCP server against a graph on your own machine instead.

Integrations

CI integrations

MCP

Graphify MCP for VS Code

Before you start

1. Add the MCP server

3. Ask a question

Commands

If something fails

Agents and integrations

Connect the graph MCP server

​Before you start

​1. Add the MCP server

​2. Start the server and sign in

​3. Ask a question

​Commands

​If something fails

​Related

Agents and integrations

Connect the graph MCP server

Before you start

1. Add the MCP server

2. Start the server and sign in

3. Ask a question

Commands

If something fails

Related