Fossil MCP Server

Most developer tooling work still happens through a UI a human drives. Fossil MCP MCP server moves it into the conversation instead. Static analysis that finds the mess vibe coding leaves behind — dead code, duplicated logic, scaffolding artifacts, and disconnected functions — across 16 languages.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

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

• scan_all — Run all analyses (dead code + clones + scaffolding) on a project
• analyze_dead_code — Detect unreachable code with configurable confidence
• detect_clones — Find duplicated code (Type 1/2/3 clones)
• fossil_refresh — Incremental re-analysis after file changes (fast)
• fossil_inspect — Inspect call graph, data flow, control flow, or blast radius for any function
• fossil_trace — Find call paths between two functions — understand how code connects
• fossil_explain_finding — Get rich context about a specific finding
• fossil_detect_scaffolding — Find AI scaffolding: phased comments, TODOs, placeholders, and temp files
• Updating — The Updating tool exposed by this server
• Modes — The Modes tool exposed by this server
• Commands — The Commands tool exposed by this server
• Configuration — The Configuration tool exposed by this server

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.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Fossil MCP.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

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. Fossil MCP's toolset — scan_all, analyze_dead_code, detect_clones and 9 more — is a fair guide to whether it matches your workflow. It is maintained by yfedoseev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Fossil MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.