Deploy Graphify | Team MCP Server with Auto-Updated Code Knowledge Graph
Shared code knowledge graph MCP for Claude Code, Cursor and Codex
graphify-railway
Just deployed
/data
Deploy and Host Graphify | Team MCP Server with Auto-Updated Code Knowledge Graph on Railway
Graphify turns a codebase into a queryable knowledge graph that AI coding assistants can navigate. This template runs it as one shared MCP server: it maps your Git repository, keeps the map up to date with every new commit, and lets your whole team connect Claude Code, Cursor or Codex to a single URL protected by an API key.
About Hosting Graphify | Team MCP Server with Auto-Updated Code Knowledge Graph
The template deploys one service and a volume. On start it clones your repository (public, or private with a read-only token), builds the graph with Graphify's code-only mode, which parses the code locally with tree-sitter and needs no LLM API key, and serves it over MCP Streamable HTTP on /mcp. Every request must carry the generated API key. Every hour (configurable) it pulls the repository and rebuilds the graph when the commit changed; the server reloads the new graph on the next request, so connected assistants never lose their session. The last good graph stays on the volume, so restarts are instant even if the repository is briefly unreachable.
Common Use Cases
- Give every developer's AI assistant the same up-to-date map of a large codebase without installing Graphify locally
- Let Claude Code, Cursor or Codex answer architecture questions: where is this used, what depends on it, shortest path between two modules
- Review pull request impact with Graphify's PR tools from any MCP client
- Onboard new team members and agents faster on an unfamiliar repository
Dependencies for Graphify | Team MCP Server with Auto-Updated Code Knowledge Graph Hosting
- A Git repository reachable over HTTPS (GitHub, GitLab, Bitbucket...)
- For private repositories, a read-only access token (GitHub fine-grained token with Contents: Read)
- An MCP client that supports Streamable HTTP with headers (Claude Code, Cursor, Codex and others)
Implementation Details
Connect Claude Code after deploying:
claude mcp add --transport http graphify https://YOUR-SERVICE.up.railway.app/mcp \
--header "Authorization: Bearer YOUR_GRAPHIFY_API_KEY"
Tools exposed: query_graph, get_node, get_neighbors, get_community, god_nodes, graph_stats, shortest_path, list_prs, get_pr_impact, triage_prs.
Security: the token is passed to git per command as an HTTP header, never written to disk or logs; the API key is passed through the environment, never on the command line. Graphify is pinned to a tested release in the Dockerfile.
Source and full guide: https://github.com/jean82290/graphify-railway. Graphify: https://github.com/Graphify-Labs/graphify (Apache-2.0). Unofficial template, not affiliated with Graphify Labs.
Why Deploy Graphify | Team MCP Server with Auto-Updated Code Knowledge Graph on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Graphify | Team MCP Server with Auto-Updated Code Knowledge Graph on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
graphify-railway
jean82290/graphify-railwayREPO_URL
HTTPS URL of the Git repository to map, e.g. https://github.com/your-org/your-repo

