Serve a graph over HTTP - Graphify

The same ten tools can run over MCP Streamable HTTP. A local HTTP server is useful when a client connects by URL instead of launching a stdio process.

Start on localhost

graphify-mcp /absolute/path/to/graphify-out/graph.json --transport http --port 8080

The endpoint is http://127.0.0.1:8080/mcp. The default host is loopback-only. Set GRAPHIFY_API_KEY in the server environment using your secret manager. Then start with the intended bind address:

graphify-mcp /data/graph.json --transport http --host 0.0.0.0 --port 8080

Clients authenticate with Authorization: Bearer <key> or X-API-Key. Use a private network or an authenticated TLS proxy for traffic beyond the local machine. A graph can contain proprietary source context.

Server options

Option	Default	Purpose
`--transport`	`stdio`	Select `stdio` or `http`.
`--host`	`127.0.0.1`	HTTP bind address.
`--port`	`8080`	HTTP port.
`--path`	`/mcp`	HTTP endpoint path.
`--api-key`	`GRAPHIFY_API_KEY`	Require a client key; prefer the environment variable to placing a secret in shell history.
`--json-response`	Off	Use JSON responses rather than SSE streams.
`--stateless`	Off	Disable per-session state.
`--session-timeout`	`3600`	Idle session timeout in seconds; `0` disables reaping.

Docker

The source repository includes a Dockerfile. Build it from that checkout:

docker build -t graphify .
docker run --rm -p 127.0.0.1:8080:8080 \
  -v "$PWD/graphify-out:/data:ro" \
  -e GRAPHIFY_API_KEY \
  graphify /data/graph.json --transport http --host 0.0.0.0

This example publishes to localhost and mounts the graph read-only. Set GRAPHIFY_API_KEY before running it. Make deliberate network and authentication choices before exposing the endpoint to other hosts.