graphify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRAPHIFY_BIN | No | CLI path | graphify |
| GRAPHIFY_HOST | No | Bind host for HTTP transports | 127.0.0.1 |
| GRAPHIFY_PORT | No | Bind port for HTTP transports | 8000 |
| GEMINI_API_KEY | No | Optional API key for Google Gemini backend naming. | |
| OPENAI_API_KEY | No | Optional API key for OpenAI backend naming. | |
| GRAPHIFY_OUT_DIR | No | Output folder name | graphify-out |
| GRAPHIFY_TIMEOUT | No | CLI timeout (seconds) | 600 |
| ANTHROPIC_API_KEY | No | Optional API key for Anthropic backend naming. | |
| GRAPHIFY_TRANSPORT | No | stdio | streamable-http | sse | stdio |
| GRAPHIFY_PROJECT_DIR | No | Project root to extract the graph from | . |
| GRAPHIFY_RESTRICT_PATHS | No | Confine graphify_build's path to the project dir (auto-on for HTTP) | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| graphify_buildA | Build or update a knowledge graph from a folder. (Writes to graphify-out/.) Args: path: Folder to extract the graph from (relative to the project dir or absolute). mode: "deep" -> more aggressive INFERRED edges; empty -> default. update: True -> re-extract only changed files and merge into the existing graph. cluster_only: True -> rerun clustering only, without re-extraction. no_viz: True -> skip the HTML visualization (faster for development). |
| graphify_queryA | Run a natural-language query against the graph. Args: question: Natural-language question, e.g. "what connects attention to the optimizer?" dfs: True -> trace a specific path in depth. budget: If >0, cap the number of tokens returned (e.g. 1500). |
| graphify_pathB | Find the exact path between two nodes (e.g. "DigestAuth" -> "Response"). |
| graphify_explainC | Return everything Graphify knows about a node. |
| graphify_addA | Add an external source to the graph (arXiv paper, tweet, etc.). http/https only. Args: url: Source URL to add. author: Original author tag (optional). contributor: Tag for who added it (optional). |
| graphify_overviewA | One-shot orientation: call this FIRST. Returns graph size, top god nodes, community count, surprise-edge count and suggested starting questions — enough to plan further exploration cheaply. |
| graphify_god_nodesB | List the highest-degree (most connected) 'god nodes'. |
| graphify_surprisesC | List unexpected cross-file/cross-domain connections (surprise edges). |
| graphify_communitiesB | Summarize Leiden communities with sizes and sample members. |
| graphify_sampling_statusA | Capability test: how can semantic naming be produced in this session? Reports whether the connected client supports host-LLM sampling (so the server needs no API key), whether a backend API key is configured as a fallback, and which method graphify_label_communities will pick. |
| graphify_label_communitiesA | Give the Leiden communities human-readable names. Args:
method: "auto" -> host-LLM sampling if the client supports it, else a
configured backend key (graphify CLI), else "Community N" placeholders.
"sampling" -> force host-LLM sampling (no API key needed).
"cli" -> force the graphify backend (GEMINI_API_KEY/OPENAI_API_KEY/...
or a local ollama). "placeholder" -> no LLM at all.
limit: Only the largest |
| graphify_searchB | Search nodes by text in their name/label (case-insensitive). |
| graphify_neighborsC | List the direct (1-hop) neighbors of a node, with relations. |
| graphify_subgraphA | Extract a BFS subgraph around a node, capped at a token budget. This is the token-cheap way to hand the model just the relevant slice of a large codebase instead of the whole graph. Args: node: Center node (exact or fuzzy match). hops: BFS depth from the center. budget_tokens: Approximate cap on returned size; expansion stops when hit. |
| graphify_node_detailsC | Show a node's full metadata: type, source file/line, docstring, community. |
| graphify_freshnessA | Check whether graph.json is stale relative to the current git HEAD. Prefers the commit graphify recorded the graph was built from
( |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| onboard | Orient yourself to this codebase using the knowledge graph. |
| trace_bug | Investigate a bug symptom by tracing it through the graph. |
| explain_flow | Explain how a named flow or feature works end to end. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| report | GRAPH_REPORT.md — core nodes, surprises and suggested questions. |
| graph_json | graph.json — the persistent, queryable graph (raw JSON). |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yasinyaman/graphify-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server