Quickstart

Run a real local scan in a couple of minutes.

Pick the install path that matches your workflow, run one scan against a real workspace, and inspect the findings before you decide whether Pro adds enough workflow value.

View GitHub quickstart VS Code extension npm package

Release bundle Example report

Recommended first run

Start with a real workspace and keep the first scan non-blocking.

Use --no-exit-code for the first pass so you can evaluate the output without wiring the scan into CI or hooks yet.

npx mcp-preflight scan . --no-exit-code

# repeat local use
npm install -g mcp-preflight
mcp-preflight scan .

Static reviewLocal by defaultReadable rule ids

What to look for

Good early signal

The scan finds concrete config, auth, or text issues that you would not have caught quickly by hand.

Bad early signal

You do not understand the output, or the warnings feel detached from actual MCP setup decisions.

Choose your path

Three entry points. One scanner.

The core scan is the same. Pick the entry point that fits your workflow and comfort level.

1. VS Code extension

Best when you want diagnostics, file-focused scans, fix recipes, and a visible local activity trail in the editor.

MCP Preflight: Scan Workspace
MCP Preflight: Scan Current File

2. npm / npx

Best when you want a fast CLI trial or repeat local scans from the terminal without any hosted dependency.

npx mcp-preflight scan . --no-exit-code

3. Release bundle

Best when npm is not how you want to install the tool. Use the single-file CLI bundle from GitHub Releases.

node mcp-preflight.js scan ./repo --no-exit-code

After the first scan

Read the rules, compare the example output, then decide if Pro matters.

The paid boundary should be clear: Lite proves the core trust review, Pro adds export, CI, hooks, and presets when those save time.

Read the rules See example output Compare Lite vs Pro