Quick start
Requirements
Section titled “Requirements”- Node.js 22+
Install
Section titled “Install”AgentGate is published on npm as mcp-agentgate; the installed command is agentgate:
npm i -g mcp-agentgate # installs the `agentgate` command# or run it without installing:npx mcp-agentgate scan1. Scan
Section titled “1. Scan”Audit every MCP server your clients (Claude Desktop, Claude Code, Cursor, VS Code, Codex, OpenCode, Windsurf, Cline, Gemini CLI, Kiro, Roo Code, Kilo Code, Zed, Continue.dev, Amp, Warp, LM Studio, Trae, Qoder, Amazon Q Developer, Qwen Code, GitHub Copilot CLI, JetBrains Junie, Factory Droid, Antigravity, Goose, Crush) are configured to run — config paths are discovered automatically:
agentgate scan # static config analysis, terminal tableagentgate scan --live # also connect to servers (stdio + remote) and audit their live tool surfaceFor OAuth-protected hosted servers, log in once with agentgate auth login <server-name> — live scans pick up the cached tokens automatically.
Machine-readable output:
agentgate scan --format json -o report.json # open it in the report vieweragentgate scan --format sarif -o report.sarif # for GitHub code scanningDrop report.json into the report viewer for a visual, filterable report.
You can also scan an MCP server repo for source-level issues:
agentgate scan path/to/repo2. Lock
Section titled “2. Lock”Pin the tool surface your agent sees — every tool’s name, description, and input schema — into agentgate.lock:
agentgate lockgit add agentgate.lockCommit the lockfile. It is your reviewed, approved baseline (format: lockfile spec).
3. Gate
Section titled “3. Gate”Fail the build when anything drifts from the baseline or a severe finding appears:
agentgate diff # exit 1 + human-readable diff on any driftagentgate ci --fail-on high # drift OR high-severity findings → non-zero exitGitHub Actions:
name: mcp-gateon: [push, pull_request]jobs: gate: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: wookat/agentgate/packages/action@main with: command: ci args: --fail-on highRecipes for GitLab CI, CircleCI, Jenkins, and Azure Pipelines: CI integration guide.
Next steps
Section titled “Next steps”- CLI reference — every command and flag.
- Rule reference — what each scan rule detects.
- Threat model — what AgentGate defends against, with real incidents.
- Advisory database — known-bad MCP packages, cross-checked on every scan.