Skip to main content
The Graphify Local repository ships a Dockerfile that runs graphify-mcp over streamable HTTP. Mount a graphify-out/ folder into the container and every agent on your network can query the same graph.
Self-host when your team wants one shared graph but the code must stay on your own infrastructure. If you don’t want to run a server, Graphify hosts the MCP endpoint for you.

​
How the image works

The image is built from Dockerfile in the repository root:
  • It installs only the mcp extra, so the image serves graphs but doesn’t build them.
  • It runs as a non-root user (UID 10001).
  • The default command reads /data/graph.json, so you mount your graphify-out/ folder at /data.
Graphify doesn’t publish a prebuilt image, so you build it yourself.

​
Run it

1

Build a graph

On a machine with Graphify Local installed:
2

Build the image

3

Start the server with a key

Arguments after the image name replace the default command, so repeat the graph path and transport flags when you add --api-key.
4

Point clients at it

For clients that take a URL and headers, such as Cursor:
Clients can also send the key as an X-API-Key header.
Always set --api-key when you bind 0.0.0.0. Without one, anyone who can reach the port can read your graph, and the server logs a warning at start-up. Put the server behind TLS (a reverse proxy or load balancer) before exposing it beyond a private network.

​
Configure

​
Keep the graph fresh

The server reloads graph.json whenever the file changes, so you don’t restart the container. Rebuild the graph on the host and the mounted file updates in place:
To automate this, run graphify hook install in the repository on the host that owns the mount, or run graphify update from a scheduled CI job that writes to the same volume.

​
Verify and troubleshoot

Look for graphify MCP server (streamable-http) on http://0.0.0.0:8080/mcp - api-key required. Then send an initialize request with your key, as shown in the MCP server quickstart. A 200 means it works; 401 means the key is missing or wrong.
The graph path doesn’t exist inside the container. Check that the mount points at a folder containing graph.json and that UID 10001 can read it.
Not as shipped. It installs only the mcp extra. Build graphs on the host or in CI, and use the container to serve them.
Run one container per graph, or merge repositories into one graph first with graphify merge-graphs.

​
What’s next

MCP server quickstart

Every tool and flag the server exposes.

Vibe coding with Graphify Local

Make agents reach for the graph first.

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.