MCP server quickstart: serve your graph to any agent

graphify-mcp reads graphify-out/graph.json and exposes it as MCP tools. Your agent can then ask for a subgraph, a node, a path, or the pull requests a change affects, instead of reading files to find out.

Use the MCP server when your client supports MCP but not skills, or when several people or agents should read one graph. For a graph hosted and refreshed for you, use the hosted MCP server.

Before you start

Build a graph first with the CLI quickstart, then install the MCP extra:

uv tool install "graphifyy[mcp]"

Connect one agent over stdio

Use an absolute path. GUI clients often start in a different folder from your terminal.

Claude Code
Cursor and JSON clients
Codex

claude mcp add --transport stdio graphify -- graphify-mcp /absolute/path/to/repo/graphify-out/graph.json

{
  "mcpServers": {
    "graphify": {
      "command": "graphify-mcp",
      "args": ["/absolute/path/to/repo/graphify-out/graph.json"]
    }
  }
}

codex mcp add graphify -- graphify-mcp /absolute/path/to/repo/graphify-out/graph.json

Serve a team over HTTP

graphify-mcp graphify-out/graph.json --transport http --port 8099 --api-key "$GRAPHIFY_API_KEY"

graphify MCP server (streamable-http) on http://127.0.0.1:8099/mcp - api-key required

Clients send the key as Authorization: Bearer <key> or X-API-Key: <key>. A request without it gets 401. The server binds to 127.0.0.1 by default and warns if you bind 0.0.0.0 without a key.

Flag	Default	Purpose
`--transport`	`stdio`	`stdio` or `http` (streamable HTTP)
`--host`	`127.0.0.1`	Interface to bind
`--port`	`8080`	HTTP port
`--path`	`/mcp`	Endpoint path
`--api-key`	`GRAPHIFY_API_KEY`	Required key for HTTP requests
`--stateless`	off	No session state, for load-balanced replicas
`--json-response`	off	Plain JSON responses instead of SSE
`--session-timeout`	`3600`	Seconds before an idle session closes; `0` disables

Tools your agent gets

Tool	Use it to
`query_graph`	Get a token-budgeted subgraph for a question (`mode`: `bfs` or `dfs`, `depth` 1–6, `token_budget` default 2000)
`get_node`	Read one node by label or ID
`get_neighbors`	List a node’s connections, optionally by relation
`get_community`	Read every node in one community
`god_nodes`	List the most connected nodes
`graph_stats`	Count nodes, edges, communities, and confidence labels
`shortest_path`	Find the path between two nodes (`max_hops` default 8)
`list_prs`, `get_pr_impact`, `triage_prs`	See which open pull requests touch which parts of the graph

The server also publishes resources such as graphify://report (the GRAPH_REPORT.md text) and graphify://god-nodes.

Verify the connection

Reload MCP servers in your client and ask it to call graph_stats. Then try:

{"question": "cluster leiden", "token_budget": 1500}

For HTTP, check the endpoint from a terminal:

curl -s -o /dev/null -w "%{http_code}\n" -X POST http://127.0.0.1:8099/mcp \
  -H "Authorization: Bearer $GRAPHIFY_API_KEY" \
  -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

A 200 means the server is up and your key works.

graphify-mcp: command not found

The MCP extra isn’t installed in the environment on your PATH. Run uv tool install --reinstall "graphifyy[mcp]", or use python -m graphify.serve from the virtual environment where Graphify is installed.

Does the server see graph updates?

Yes. It reloads graph.json when the file changes, so graphify update . or a git hook keeps answers current.

What’s next

Self-host with Docker

Run the HTTP server in a container.

Vibe coding with Graphify Local

Make your agent use the graph by default.

Try it in Graphify

We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.

Get started

Features

Configuration

Support

MCP server quickstart: serve your graph to any agent

Before you start

Connect one agent over stdio

Serve a team over HTTP

Tools your agent gets

Verify the connection

What’s next

Self-host with Docker

Vibe coding with Graphify Local

Try it in Graphify

​Before you start

​Connect one agent over stdio

​Serve a team over HTTP

​Tools your agent gets

​Verify the connection

​What’s next

Self-host with Docker

Vibe coding with Graphify Local

Try it in Graphify

Before you start

Connect one agent over stdio

Serve a team over HTTP

Tools your agent gets

Verify the connection

What’s next