grafyx-mcp 0.1.1

MCP server that gives AI coding assistants real-time codebase understanding via Graph-sitter

Grafyx

Real-time codebase understanding for AI coding assistants.

---

What is Grafyx?

AI coding tools read raw files with zero architectural understanding -- they don't know what calls what, which classes inherit from where, or how your modules connect. Grafyx fixes this by parsing your entire codebase into a full relationship graph using Graph-sitter (built on tree-sitter), then exposing that graph to any AI assistant through the Model Context Protocol (MCP). Your assistant can trace call chains, map dependencies, find related code by description, detect conventions, and understand your project's architecture -- all in real time, with a file watcher that keeps the graph current as you edit.

---

Quick Start

Claude Code

# Zero-install (recommended)
claude mcp add --scope user grafyx -- uvx --from grafyx-mcp grafyx

# Or install with pip first
pip install grafyx-mcp
claude mcp add --scope user grafyx -- grafyx

Cursor / Windsurf / Cline

Add to your MCP config file:

• Cursor: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
• Windsurf: ~/.codeium/windsurf/mcp_config.json
• Cline: Cline MCP settings in VS Code

{
  "mcpServers": {
    "grafyx": {
      "command": "uvx",
      "args": ["--from", "grafyx-mcp", "grafyx"]
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json:

{
  "servers": {
    "grafyx": {
      "command": "uvx",
      "args": ["--from", "grafyx-mcp", "grafyx"]
    }
  }
}

Using pip instead of uvx? Replace the command with: "command": "grafyx" (no args needed).

---

Available Tools

Tool	Description
get_project_skeleton	Full project structure with stats per module
get_function_context	Everything about a function: callers, callees, deps
get_file_context	File contents, imports, dependencies
get_class_context	Class methods, inheritance, usages
find_related_code	Natural language search across the codebase
find_related_files	Find files relevant to a feature by matching symbols
get_dependency_graph	Impact analysis: what depends on what
get_conventions	Detected coding patterns and conventions
get_call_graph	Call chain tracing upstream and downstream
refresh_graph	Force re-parse of the codebase
get_module_context	Symbols in a directory/package (intermediate zoom)
get_subclasses	Inheritance tree for a base class
get_unused_symbols	Dead code detection
set_project	Switch the served project at runtime

---

How It Works

Your AI Assistant
       |
       | MCP Protocol (stdio)
       v
  +-----------+
  |  Grafyx   |  FastMCP server with 14 tools
  |  Server   |
  +-----------+
       |
  +-----------+     +-----------+     +-------------+
  |  Graph    |---->|  Search   |     | Convention  |
  |  Engine   |---->|  Engine   |     | Detector    |
  +-----------+     +-----------+     +-------------+
       |
       v
  +-----------+
  |  Graph-   |  Tree-sitter based parsing
  |  sitter   |
  +-----------+
       |
  +-----------+
  |  Watchdog |  File watcher for live updates
  +-----------+

1. Startup -- Grafyx detects languages in your project and parses all source files into a semantic graph via Graph-sitter.
2. Serving -- The FastMCP server exposes 14 tools over stdio. Your AI assistant calls them as needed.
3. Live updates -- Watchdog monitors file changes. When you save, the graph is automatically re-parsed after a short debounce.

ML-augmented search

Grafyx ships several small numpy-only MLPs trained on real source data:

• M1 Relevance ranker -- 33-feature MLP scores each search result against the query.
• M3 Source token filter -- suppresses noise tokens (imports, strings, magic methods) from full-text search.
• M4 Symbol importance -- weights symbols by caller count, exports, and structural signals.
• M5 Bi-encoder -- semantic embedding model (BPE tokenizer, FeedForward encoder) for natural-language code search.
• Gibberish detector -- character-bigram MLP that blocks nonsense queries before they hit the index.

All weights ship inside the wheel (~11 MB total). Inference is pure numpy, no PyTorch at runtime.

---

Supported Languages

Language	Extensions
Python	.py, .pyi
TypeScript	.ts, .tsx
JavaScript	.js, .jsx

Languages are auto-detected. To specify manually:

grafyx --languages python,typescript

---

Options

grafyx [OPTIONS]

  --project PATH       Project to analyze (default: current directory)
  --languages LANGS    Comma-separated languages (default: auto-detect)
  --ignore PATTERNS    Additional directories to ignore
  --no-watch           Disable file watching
  --verbose, -v        Debug logging
  --version            Show version

Default ignored: node_modules, .git, __pycache__, .venv, venv, .env, dist, build, .tox, .mypy_cache, .pytest_cache, .ruff_cache, egg-info, .eggs, .next, .nuxt, coverage, .coverage, .nyc_output

---

Multi-Agent Support

Grafyx works with agent teams. A single Grafyx instance serves all agents connected to the same project. When one agent modifies code, the file watcher updates the graph automatically, so other agents immediately see the changes.

---

Contributing

git clone https://github.com/bilal07karadeniz/Grafyx.git
cd Grafyx
pip install -e ".[dev]"
pytest

---

Troubleshooting

Windows: Graph-sitter requires Linux. Use WSL and configure your MCP client to launch via wsl:

{
  "mcpServers": {
    "grafyx": {
      "command": "wsl",
      "args": ["-e", "bash", "-c", "source ~/your-venv/bin/activate && grafyx"]
    }
  }
}

---

License

MIT -- see LICENSE for details.