Graphify

Trace callers, dependencies and change impact across indexed repos from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Graphify connector does

The Graphify MCP server connects Claude to Graphify's knowledge graph of your indexed code repositories. Its 24 tools find symbol definitions, follow callers and callees, trace paths between code, find related tests and estimate a change's impact. It also recalls and saves repository memory. No tool edits your source files.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Graphify tools (24)

  • graph_stats
  • graphify_callees
  • graphify_callers
  • graphify_expand
  • graphify_file_neighbors
  • graphify_find
  • graphify_find_seeds
  • graphify_impact
  • graphify_imports_exports
  • graphify_node
  • graphify_rank_files
  • graphify_references
  • graphify_render_subgraph
  • graphify_tests_for
  • graphify_trace
  • impact_and_risk
  • list_repositories
  • list_workspaces
  • memories_about
  • query_graph
  • recall
  • remember
  • set_workspace
  • shortest_path

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Only as good as the index. The directory says results reflect the indexed graph's coverage, semantic matches are suggestions, and impact and test results are not guarantees of complete coverage.
  • No local changes. The hosted graph does not see uncommitted work.
  • Rate limits. 240 requests per minute per client IP; over that returns a rate_limited 429. Request bodies over 256 KB are refused.
  • Memory is plan-gated. Memory features depend on your workspace plan, per the directory.
  • Your code is indexed by Graphify. The hosted service stores a graph of your repositories; check Graphify's privacy policy before connecting private code.
  • Tool schemas are unverified. We could not read them without signing in, and called no tool.

Frequently asked questions

Why is Graphify connected but Claude does not use it?

The per-chat toggle is usually off. Graphify's docs say to select the plus button in a Claude chat, open Connectors and turn Graphify on, then approve the tool call if Claude asks. If tools appear but cannot run, check that Graphify's tools are enabled in your client. In Claude Code, claude.ai connectors load only when you sign in with a Claude account.

Why does list_repositories come back empty?

You are in the wrong workspace, or the workspace has no indexed repositories. Graphify's docs say to switch with set_workspace, or enable a repository in the console and wait until its status reads Indexed. If only a setup tool appears, finish Graphify's onboarding, enable a repository, wait for indexing, start a new chat and reconnect the connector.

Does Graphify MCP see my uncommitted local changes?

No. The hosted server answers from the indexed graph of your repositories, not from your working copy, per Graphify's docs. Changes appear after the repository is indexed again. For uncommitted work, Graphify points to its open-source local MCP server, which builds a graph on your own machine and can run over stdio for a single agent.

Sources

Use it in an agent

Put Graphify to work.

Connect Graphify once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.