Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
AI code impact analysis — dependency graphs, cascade detection, and build gates for AI agents
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
SYKE_LICENSE_KEY, GEMINI_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"syke": {
"command": "npx",
"args": [
"-y",
"@syke1/mcp-server"
],
"env": {
"SYKE_LICENSE_KEY": "your-value",
"GEMINI_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add syke --env SYKE_LICENSE_KEY=your-value --env GEMINI_KEY=your-value -- npx -y @syke1/mcp-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"syke": {
"command": "npx",
"args": [
"-y",
"@syke1/mcp-server"
],
"env": {
"SYKE_LICENSE_KEY": "your-value",
"GEMINI_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"syke": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@syke1/mcp-server"
],
"env": {
"SYKE_LICENSE_KEY": "your-value",
"GEMINI_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 khalomsky 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SYKE_LICENSE_KEY, GEMINI_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.5.4)于8个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Fomu MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AI code impact analysis MCP server. SYKE monitors every file your AI touches, maps dependency graphs, detects cascading breakage, and gates builds before damage spreads.
Works with Claude Code, Cursor, Windsurf, and any MCP-compatible AI coding agent.
gate_build to check if all changes are safe.FAIL verdict.SYKE is a safety net, not a gatekeeper. It doesn't block your AI while working — it catches what your AI missed before you ship.
Create ~/.syke/config.json:
{
"licenseKey": "SYKE-XXXX-XXXX-XXXX-XXXX", "geminiKey": "your-gemini-api-key" }
Get your license key at syke.cloud/dashboard. You only need ONE AI key. Supported:
geminiKey,openaiKey,anthropicKey.
Claude Code:
claude mcp add syke -- npx @syke1/mcp-server@latest
Cursor (.cursor/mcp.json):
{
"mcpServers": { "syke": { "command": "npx", "args": ["@syke1/mcp-server@latest"] } } }
Windsurf (~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": { "syke": { "command": "npx", "args": ["@syke1/mcp-server@latest"] } } }
Windows note: If
npxis not found, use the full path:"command": "C:\\Program Files\\nodejs\\npx.cmd"
Add this line to your project's CLAUDE.md (or equivalent AI instruction file):
After completing code changes, always run the gate_build MCP tool before committing or deploying.
This ensures your AI agent automatically runs SYKE's safety check after every task — no manual prompting needed.
SYKE auto-detects your project language and builds the dependency graph on startup. Open http://localhost:3333 to see your live dashboard.
| Tool | Tier | Description |
|---|---|---|
gate_build | Free | Mandatory pre-build check. Returns PASS/WARN/FAIL verdict before any build or deploy. |
check_safe | Free | Quick one-line safety verdict: HIGH/MEDIUM/LOW/NONE risk. |
get_dependencies | Free | Lists internal imports (forward dependencies) of a file. |
analyze_impact | Pro | Full impact analysis with SCC, risk scoring, and git coupling. |
get_hub_files | Pro | Ranks files by PageRank importance score. |
refresh_graph | Pro | Re-scans all source files and rebuilds the dependency graph. |
ai_analyze | Pro | AI semantic analysis (Gemini/OpenAI/Claude) of a file and its dependents. |
check_warnings | Pro | Real-time monitoring alerts for file changes that may break dependents. |
SYKE supports three AI providers for semantic analysis. Bring your own key:
| Provider | Model | Config Key | Env Variable |
|---|---|---|---|
| Google Gemini | gemini-2.5-flash | geminiKey | GEMINI_KEY |
| OpenAI | gpt-4o-mini | openaiKey | OPENAI_KEY |
| Anthropic | claude-sonnet-4-20250514 | anthropicKey | ANTHROPIC_KEY |
Auto-selection: SYKE uses the first available key (Gemini > OpenAI > Anthropic). Force provider: Set aiProvider in config (or SYKE_AI_PROVIDER env var) to override.
SYKE goes beyond simple dependency counting. Five production-grade algorithms work together to deliver precise, fast, and context-rich impact analysis — all running locally with zero AI token cost.
Circular dependencies are the #1 source of misleading impact analysis. SYKE uses Tarjan's algorithm to detect all Strongly Connected Components, condenses them into a clean DAG, then runs topological sort to compute correct cascade levels.
Before: "47 files affected" (inflated by cycles)
After: "3 files in circular cluster (Level 0) → 5 files (Level 1) → 4 files (Level 2)"
Five signals combined into a single 0–1 risk score:
| Signal | Weight | What it measures |
|---|---|---|
| Fan-in | 30% | How many files depend on this one |
| Stability Index | 20% | I = Ce/(Ca+Ce) — lower = foundation file = riskier to change |
| Cyclomatic Complexity | 20% | Internal branching complexity (regex-based, 8 languages) |
| Cascade Depth | 15% | How many layers deep the impact propagates |
| PageRank | 15% | Recursive importance in the dependency graph |
auth_service.ts → Risk: 0.82 (CRITICAL)
Fan-in: 24, Stability: 0.12, Complexity: 47, Cascade: 4 levels, PageRank: 99th
string_utils.ts → Risk: 0.31 (LOW) Fan-in: 18, Stability: 0.85, Complexity: 3, Cascade: 1 level, PageRank: 42nd
AI agents can now make threshold decisions: proceed if < 0.3, warn if 0.3–0.7, block if > 0.7.
Static imports miss hidden dependencies — files that always change together but have no import relationship. SYKE mines your git history (last 500 commits) to find these logical couplings.
auth_service.ts changed →
[Dependency Graph] auth_provider.ts, login_screen.ts [Git Coupling — Hidden Dependencies] config/auth_config.json (85% confidence, 12 co-changes) styles/auth.css (72% confidence, 8 co-changes)
Simple fan-in counts treat all dependents equally. PageRank computes recursive importance — a file imported by many *important* files ranks higher than one imported by many leaf files.
Before: utils.ts ranked #1 (25 dependents — but all are leaf components)
After: auth.ts ranked #1 (20 dependents — 15 of which are core modules)
For large codebases (10K+ files), full graph rebuilds are too slow. SYKE now updates only the changed file's edges and invalidates only the affected cache entries.
Before: 1 file changed → re-parse all 500 files → 2+ seconds
After: 1 file changed → re-parse 1 file → edge diff → 50ms Same file queried again → cache hit → O(1) instant
Auto-detected, zero-config: Dart/Flutter, TypeScript/JavaScript, Python, Go, Rust, Java, C++, Ruby.
Live dependency graph visualization at localhost:3333 with:
SYKE reads from ~/.syke/config.json (primary) with environment variable overrides:
| Config Key | Env Variable | Description | Required |
|---|---|---|---|
licenseKey | SYKE_LICENSE_KEY | Pro license key from dashboard | No (Free tier works without) |
geminiKey | GEMINI_KEY | Google Gemini API key for ai_analyze | No (any one AI key) |
openaiKey | OPENAI_KEY | OpenAI API key for ai_analyze | No (any one AI key) |
anthropicKey | ANTHROPIC_KEY | Anthropic API key for ai_analyze | No (any one AI key) |
aiProvider | SYKE_AI_PROVIDER | Force AI provider: gemini, openai, or anthropic | No (auto-selects) |
port | SYKE_WEB_PORT | Dashboard port (default: 3333) | No |
Full config example (~/.syke/config.json):
{
"licenseKey": "SYKE-XXXX-XXXX-XXXX-XXXX", "geminiKey": "AIza...", "openaiKey": "", "anthropicKey": "", "port": 3333 }
You (developer) AI Agent SYKE
| -- modifies files | |
| -- modifies files | |
| -- modifies files | |
| -- gate_build ---> |
| | |-- scans graph | | |-- checks impact | |<-- PASS/FAIL ----| | | | |<-- "Done. Safe to | | | build." ----------| |
We're giving the first 100 developers full Pro access for 30 days — no credit card, no strings.
What you get:
How to claim:
Spots are limited. Once they're gone, they're gone.
gate_build, check_safe, get_dependencies).Pro and Cortex features (advanced algorithms, AI analysis, real-time monitoring, web dashboard) are included in the npm package as compiled code.Elastic License 2.0 (ELv2)
You can use, modify, and distribute SYKE freely, with two limitations: