Arbor MCP Server

The Graph-Native Intelligence Layer for Code.

Local serverstdioPython

What is the Arbor MCP server?

Most developer tooling work still happens through a UI a human drives. Arbor MCP server moves it into the conversation instead. The Graph-Native Intelligence Layer for Code.

The short version

Simulated replay — the arbor commands and their output are real (tokio @ 178k LOC). Methodology: BENCHMARKS.md

The tools it exposes

The server publishes 5 tools. What each one is for:

  • Tier — Tools
  • Orientation — get_map
  • Surgical — list_entry_points · get_callers · get_callees · search_symbols · get_file_graph · get_node_detail
  • Broad — get_logic_path · analyze_impact · find_path · get_knowledge_path
  • Agent-native — get_blast_radius · explain_symbol · audit_security · get_architecture_overview · batch_query

What it needs from you

Configuration is passed through the environment: GITHUB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

@anandb71/arbor-cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Arbor's toolset — Tier, Orientation, Surgical and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Anandb71; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
TierTools
Orientationget_map
Surgicallist_entry_points · get_callers · get_callees · search_symbols · get_file_graph · get_node_detail
Broadget_logic_path · analyze_impact · find_path · get_knowledge_path
Agent-nativeget_blast_radius · explain_symbol · audit_security · get_architecture_overview · batch_query

How to install the Arbor MCP server

### Cursor / VS Code

```json
{
  "mcpServers": {
    "arbor": {
      "type": "stdio",
      "command": "arbor",
      "args": ["bridge"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GITHUB_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Arbor to Tier.
  • Use Arbor to Orientation.
  • Use Arbor to Surgical.

Frequently asked questions

It connects Arbor to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (Tier, Orientation, Surgical, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Arbor directly.