Codehelper MCP Server

Codehelper MCP server exists for a simple reason — assistants are far more useful when they can act on Codehelper directly instead of describing what you should do. Local-first code intelligence MCP: symbol graph, impact analysis, 60+ tools.

What you get

Codehelper indexes git repositories on your machine, builds a symbol and call graph, and exposes 60+ MCP tools so Cursor, Claude Code, Codex, and other MCP clients can search, understand, and safely change your code — without uploading the whole repo to a cloud model.

What the assistant can call

Once Codehelper is connected, these are the calls the assistant has available:

• Platform — Install
• Linux — scripts/install.sh
• macOS — scripts/install.sh
• Windows — scripts/install.ps1
• Client — Setup
• Cursor — Per-project .mcp.json via codehelper init
• Codex — Reads generated AGENTS.md
• Layer — Technology
• Indexing — tree-sitter parsers + SQLite symbol/call graph
• Search — BM25 + trigrams + call-graph ranking (optional local semantic rerank — docs/LOCAL_EMBED.md)

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

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. Codehelper's toolset — Platform, Linux, macOS and 7 more — is a fair guide to whether it matches your workflow. It is maintained by VeyrForge; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Codehelper.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the codehelper mcp server does with a few real requests.