Wisegit MCP Server

If you already use Wisegit, the wisegit mcp server is the piece that lets your assistant work with it directly. Extracts decision intent from git history and protects intentional code from AI modification.

What the server does

When Claude Code (or any MCP-compatible agent) is about to edit a file, wisegit injects a decision manifest showing which functions are frozen, stable, or open — so the AI respects what was intentional, not just what compiles.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• get_file_decisions — Decision manifest for a file — freeze scores, intent history, recovery levels, override status
• get_freeze_score — Score + signal breakdown for a specific function
• get_function_history — Full chronological decision timeline for a function
• get_theory_gaps — Functions with unrecoverable rationale (inactive authors, timeline gaps)
• get_branch_context — Branch merge history — what was migrated and why
• search_decisions — Search past decisions by keyword across the entire repo
• create_override — Override a frozen function (user approves in Claude Code UI)
• extract_intent — Extract intent for NOISE commits using the host LLM — no Ollama needed
• find_similar_functions — Search for existing functions that solve a similar problem before writing new code
• predict_impact — Predict what functions will break if a given function is modified
• get_codebase_conventions — Extract coding conventions for a file's neighborhood
• Prerequisites — The Prerequisites tool exposed by this server

Installation

Installation goes through your MCP client rather than a global install: point it at @sandip124/wisegit 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.

Credentials and setup notes

Configuration is passed through the environment: GITHUB_TOKEN, GITLAB_TOKEN, WISEGIT_DB_PATH, OLLAMA_URL. 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.

• Node.js >= 20 That's it. No Docker, no PostgreSQL, no external services.

Where it fits

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. Wisegit's toolset — get_file_decisions, get_freeze_score, get_function_history and 9 more — is a fair guide to whether it matches your workflow. It is maintained by Sandip124; 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.

Worth knowing first

• 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.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Wisegit.
• 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.