Anchor MCP Server

MCP stdio server that serves local repo memory and org memory from GitHub PR history, code, tests, regressions, and cross-repo impact to AI coding

Local serverstdio

What is the Anchor MCP server?

Anchor MCP server exists for a simple reason — assistants are far more useful when they can act on Anchor directly instead of describing what you should do. MCP stdio server that serves local repo memory and org memory from GitHub PR history, code, tests, regressions, and cross-repo impact to AI coding agents.

What you get

Anchor is a local-first, MCP-compatible memory tool that indexes GitHub PR history, local code, tests, regressions, architecture patterns, team rules, and cross-repo impact so AI coding agents can make safer code changes with evidence-backed context.

  • MCP context before edits — anchor_get_context gives Cursor, Claude Code, Codex, VS Code, Antigravity, and generic MCP clients concise, ranked, cited repo and org memory before non-trivial changes
  • GitHub PR history as evidence — merged PR bodies, review comments, issue comments, commits, labels, and regressions become searchable local context
  • Local codebase indexing — current files, symbols, imports, tests, architecture patterns, and test commands are indexed into SQLite
  • Org memory for AI agents — allowlisted repos can be cloned locally and linked through imports, packages, API consumers, schemas, and regressions
  • No SaaS, no CLI telemetry — indexes stay on your machine, GitHub access is read-only, and Anchor does not call remote LLM APIs

Configuration and credentials

You will need one environment variable: GITHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at @pratik7368patil/anchor on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by pratik7368patil; 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.

Before you rely on it

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the anchor mcp server does with a few real requests.

How to install the Anchor MCP server

{
  "mcpServers": {
    "anchor": {
      "command": "npx",
      "args": ["-y", "@pratik7368patil/anchor"],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GITHUB_TOKENCredential the server authenticates with.Yes

Frequently asked questions

It connects Anchor to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Anchor directly.