Syke
See blast radius of AI-suggested edits via dependency graphs, cascades, and optional build gates before merge.
Overview
SYKE MCP is a MCP server for the Ship phase that analyzes AI-driven code change impact with dependency graphs, cascade detection, and build gates.
What is this MCP server?
- Builds dependency graphs for code the agent touched
- Detects cascade paths where a small edit ripples across modules
- Supports build-gate style checks suited to agent-driven workflows
- Free tier runs without SYKE_LICENSE_KEY; Pro unlocks license and optional Gemini semantic analysis
- Ships as @syke1/mcp-server over stdio for local agent integration
- npm package @syke1/mcp-server version 1.5.4, stdio transport
- Optional env: SYKE_LICENSE_KEY (Pro), GEMINI_KEY (Pro semantic analysis)
- Free tier documented as usable without license key
Community signal: 2 GitHub stars.
What problem does it solve?
Agent edits look small in the diff but silently break distant imports, types, or build steps you do not see in chat.
Who is it for?
Solo devs using coding agents on multi-file repos who want pre-merge impact signals beyond lint and unit tests.
Skip if: Pure content or no-code projects with no dependency graph to analyze.
What do I get? / Deliverables
After SYKE is connected, reviews include graph-backed impact and cascade warnings so you merge fewer surprise breakages.
- Dependency graph views for changed code regions
- Cascade risk signals across related modules
- Build-gate guidance agents can act on before merge
Recommended MCP Servers
Journey fit
Canonical shelf is Ship because impact analysis and gates matter when you review changes agents propose, not when you first scaffold features. Review subphase covers pre-merge reasoning about what else breaks when a file or symbol changes.
How it compares
MCP impact-analysis and gate tooling, not a full CI runner or security scanner.
Common Questions / FAQ
Who is SYKE MCP for?
Indie builders and small teams running AI coding agents who need dependency and cascade insight before accepting large or cross-cutting patches.
When should I use SYKE MCP?
In Ship review when an agent proposes refactors or multi-file fixes and you want blast-radius analysis and optional build gates before merge.
How do I add SYKE MCP to my agent?
Register stdio @syke1/mcp-server in your MCP client; set SYKE_LICENSE_KEY for Pro and GEMINI_KEY only if you use Pro semantic features—Free tier needs no license.