Ovecc

What ovecc MCP server does

The ovecc MCP server exposes ovecc's CLI commands as agent tools over MCP. It is intended for repository-aware coding workflows where an agent needs to inspect architecture, assess a proposed change, or identify code-quality and security findings. The server works from an index of the repository rather than asking an agent to read every file directly.

Ovecc belongs in the 💻 Developer Tools category and is useful when architecture rules need to be checked consistently by a coding agent, a local developer, or CI. It can report dependency cycles, coupling, impact, dead code, duplicated code, complexity, security patterns, dependency vulnerabilities, hotspots, and architectural contract violations.

How it works

Run ovecc index . to parse and resolve the repository, then persist its model in .ovecc/. The ovecc MCP server can expose the resulting command surface to an agent through standard input and output with ovecc mcp. Analysis is deterministic, runs offline, and does not place an LLM in the analysis loop. DuckDB is bundled with the binary, so no separate database runtime is required.

The indexed model includes files, imports, symbols, and calls. Commands can return text, JSON, NDJSON, or Markdown; SARIF and Code Climate formats are also available for supported reporting workflows. Stable exit codes support CI automation.

Setup and configuration

Install with npx ovecc index ., or install globally with npm i -g ovecc to keep the executable on the system path. Prebuilt binaries are available for Linux x86_64 and aarch64, Windows x86_64, and macOS arm64. The project can also be built from source with stable Rust.

A typical MCP setup first indexes the repository, then starts ovecc mcp from the repository context so an agent can use the indexed commands. No environment variables are documented as required. The macOS browser-downloaded binary may need its quarantine attribute removed; binaries run through npm or curl do not receive that flag.

Architecture rules are stored in .ovecc/architecture.toml. architecture init can draft a contract from the current import graph, while architecture suggest recognizes patterns including Feature-Sliced, bulletproof-react, Clean/Hexagonal, and Nx workspaces. The contract can define component paths, allowed dependencies, slice isolation, denied capabilities, and cyclomatic-complexity limits.

Tools and capabilities

The ovecc MCP server can provide the command set used for:

• Finding change impact and architectural cycles.
• Reviewing a file with findings and suggested fixes.
• Diagnosing named architectural smells with evidence and remediation guidance.
• Checking architecture contracts and gating new violations in CI.
• Inspecting coupling, components, metrics, hotspots, and history.
• Detecting secrets, insecure patterns, weak cryptography, tainted flows, and offline OSV dependency vulnerabilities.
• Finding duplicate code, unused exports, unreachable files, and over-complex functions.
• Exporting a self-contained HTML dependency-graph viewer.

fix can apply supported mechanical fixes and defaults to a dry run. review identifies named defects introduced by a change, while report produces a one-shot architecture report in Markdown or JSON.

Limitations and notes

The supplied material does not identify specific MCP client applications, so client compatibility should be verified in the target agent. Ovecc is CLI-first and requires an index before most repository analysis is useful. Its architecture checks evaluate the rules written in .ovecc/architecture.toml; they do not create an intended architecture automatically unless an initialization or suggestion command is used. The macOS release binary is unsigned and may be quarantined by Gatekeeper when downloaded through a browser.