Codegraph vs Graphify

A side-by-side look at the Codegraph and Graphify MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Codegraph logoCodegraphKnowledge & Memory · Local subprocess (stdio)Semantic code graph with 34 tools: callers, impact, complexity, AI context, memory. 38 languages.63GoodAuth: not declaredGraphify logoGraphifyKnowledge & Memory · Local subprocess (stdio)Search indexed code, trace dependencies, assess change impact, and recall repository memory.48FairAuth: oauth 2.0

Verdict: choose Codegraph for knowledge & memory work as a local process; choose Graphify for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Codegraph logoChoose Codegraph when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_ai_context, get_edit_context, get_curated_context.
Explore Codegraph

Graphify logoChoose Graphify when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
Explore Graphify

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCodegraph logoCodegraphGraphify logoGraphify
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal63/100 · Good48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1323
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools56Not listed

Tools & capabilities

Codegraph tools 56

  • get_ai_contextPrimary context tool.** Intent-aware (explain/modify/debug/test) with token budgeting. Returns source, related symbols, imports, siblings, debug hints.
  • get_edit_contextEverything needed before editing: source + callers + tests + memories + git history
  • get_curated_contextCross-codebase context for a natural language query ("how does auth work?")
  • analyze_impactBlast radius prediction — what breaks if you modify, delete, or rename
  • analyze_complexityCyclomatic complexity with breakdown (branches, loops, nesting, exceptions, early returns)
  • find_circular_depsDetect circular import/dependency chains across files
  • find_hot_pathsMost-called functions ranked by transitive caller count
  • find_dead_importsFind unused imports — modules imported but never referenced
  • get_module_summaryHigh-level summary of a directory: file count, functions, language breakdown, top complex functions
  • search_by_patternRegex search across function bodies, signatures, names, and docstrings
  • search_by_errorFind functions that throw, catch, or handle specific error types
  • symbol_searchFind symbols by name or natural language (hybrid BM25 + semantic search)
  • +44 more on the listing page

Graphify tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Codegraph

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "codegraph": {
      "command": "npx",
      "args": [
        "-y",
        "@vscode/vsce"
      ]
    }
  }
}

Graphify

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "graphify": {
      "command": "npx",
      "args": [
        "-y",
        "not"
      ]
    }
  }
}

Frequently asked questions

Codegraph is categorized under Knowledge & Memory and uses a local stdio subprocess. Graphify belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Codegraph for knowledge & memory work and Graphify for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Codegraph has no declared pricing — check the project's own site. Graphify has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add codegraph and graphify as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Codegraph has a quality signal of 63/100 (Good) with 1 views, 0 installs and 132 GitHub stars. Graphify has 48/100 (Fair) with 1 views, 0 installs and 3 GitHub stars.