Fossil Mcp

What is Fossil Mcp?

Fossil Mcp is a static analysis toolkit purpose-built for projects that use AI-assisted “vibe coding” workflows. It detects dead code, duplicated logic, scaffolding artifacts (like placeholder TODOs and phase comments), and temporary files left behind by AI agents, and it builds a code graph so both developers and AI tools can trace how functions connect. It can run as a standalone CLI, an interactive REPL, a CI/CD check, or a Model Context Protocol (MCP) server that lets AI agents self-check their output.

How to use Fossil Mcp?

Install via the quick install script at fossil‑mcp.com/install.sh (macOS/Linux) or the PowerShell one‑liner for Windows, or download a pre‑built binary from GitHub Releases. Run fossil-mcp with no arguments to scan the current directory and enter the interactive REPL, or use subcommands like fossil-mcp check for CI/CD. To use it as an MCP server, add fossil-mcp (with no arguments) as a command in your AI coding tool’s MCP configuration (e.g., Claude Code, Cursor, VS Code, Windsurf).

Key features of Fossil Mcp

• Detects unreachable functions, unused exports, and orphaned methods.
• Finds code clones (exact, renamed, and structural duplicates).
• Identifies scaffolding artifacts: phase/step comments, TODO/FIXME markers, placeholder bodies.
• Locates temp and backup files (temp_*, backup_*, old_*, phase_*).
• Builds a call graph for tracing, blast radius, and code path analysis.
• Single binary written in Rust, zero configuration, framework‑aware.

Use cases of Fossil Mcp

• Clean up dead functions left behind after an AI refactoring pass.
• Discover structurally similar utility functions scattered across modules.
• Remove stale TODO, “Phase 1”, and placeholder markers accumulated over multiple AI sessions.
• Audit a codebase for temporary files created by AI tools.
• Let an AI agent inspect the call graph and blast radius before proposing a refactoring.

FAQ from Fossil Mcp

What makes Fossil Mcp different from a traditional linter?

Fossil Mcp is not a general linter — it specifically targets dead code, structural duplication, scaffolding artifacts, and temp files that accumulate when AI writes most of the code and humans review less. It also provides a code graph (not just text search) so agents can trace how functions connect.

Does Fossil Mcp require any configuration?

No. It works out of the box with zero configuration. A configuration file is optional if you need custom thresholds or exclusions.

How does Fossil Mcp integrate with AI coding tools?

Fossil runs as an MCP server by default. You add fossil-mcp as a command in your tool’s MCP configuration (e.g., Claude Code, Cursor, VS Code, Windsurf). Once connected, the AI agent gets tools like scan_all, analyze_dead_code, detect_clones, and fossil_trace.

What languages does Fossil Mcp support?

Sixteen languages are supported across polyglot codebases. The README mentions framework awareness for React, Next.js, Django, Spring, and Axum, among others.

How do I install Fossil Mcp on Windows?

Run the following in PowerShell: irm fossil-mcp.com/install.ps1 | iex. Alternatively, download the Windows x86_64 binary from GitHub Releases and add it to your PATH.