VibestatVibestat
MCP Serverv1.0.4MIT License

Vibeguard MCP gives agents context before they edit.

An MCP server that helps AI coding agents understand the codebase, inspect blast radius, and run pre-edit safety checks before changing a single line.

npx -y vibeguard-mcp@latest setup --key vg_YOUR_KEY --ide cursor

Context before action

Agents call summarize_project first to understand the tech stack, entry points, and file layout — instead of flying blind.

Blast-radius awareness

find_related_files shows every dependent, import, and sibling so the agent knows what else might break before touching a single line.

Built-in safety checks

pre_edit_check returns a risk level, side-effect warnings, and a review checklist — a guardrail before every edit.

Tools

Three tools, designed to be called in order before any edit.

1summarize_project

Scans the entire project and returns a structured overview: language breakdown, package metadata, directory tree (2 levels), detected entry points, and every code file sorted by size. Call this first — before reading individual files or making any edits.

Parameters

project_pathAbsolute path to the project root directory

Example

summarize_project({
  project_path: "/Users/you/my-app"
})
2find_related_files

Given a target file, finds every other file related to it: files it imports (dependencies), files that import it (dependents that will break if exports change), same-directory siblings, and files with similar names. Use before editing a file to understand the blast radius.

Parameters

project_pathAbsolute path to the project root directory
target_filePath to the file to analyze (absolute or relative to project_path)

Example

find_related_files({
  project_path: "/Users/you/my-app",
  target_file: "src/lib/auth.ts"
})
3pre_edit_check

Runs a safety audit on a file before you edit it. Returns: all exports (the API that dependents rely on), all dependents that import this file, all imports (dependencies), detected side effects (env vars, timers, global writes, singletons…), a risk level (LOW / MEDIUM / HIGH), and a pre-edit checklist. Always call this before modifying shared or core files.

Parameters

project_pathAbsolute path to the project root directory
target_filePath to the file you are about to edit (absolute or relative to project_path)

Example

pre_edit_check({
  project_path: "/Users/you/my-app",
  target_file: "src/lib/auth.ts"
})

Risk Levels

pre_edit_check assigns a risk level based on how many files depend on the target.

LOW

Few dependents — changes are unlikely to break other parts of the codebase.

MEDIUM

Some files depend on this. Double-check export signatures before editing.

HIGH

Many dependents. Changes to exported names or signatures will break other files.

Installation

One command sets up Vibeguard MCP in your IDE. Requires Node.js 18 or newer.

Setup command

npx -y vibeguard-mcp@latest setup --key vg_YOUR_KEY --ide <ide>

Replace vg_YOUR_KEY with your Vibestat API key and <ide> with one of the supported IDEs below. Then restart your IDE.

Supported IDEs

Cursor
--ide cursor
Windsurf
--ide windsurf
Claude Code
--ide claude-code
VS Code
--ide vscode
Zed
--ide zed
Codex CLI
--ide codex

Manual config (JSON-based IDEs)

If you prefer to configure manually, add the following to your IDE's MCP config file:

{
  "mcpServers": {
    "vibeguard": {
      "command": "npx",
    "args": ["-y", "vibeguard-mcp@latest"],
      "env": {
        "VIBEGUARD_API_KEY": "vg_YOUR_KEY"
      }
    }
  }
}

Ready to add context to your AI edits?

Sign up for Vibestat to get your API key and start using Vibeguard MCP today.

Sign In