Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
AI code impact analysis — dependency graphs, cascade detection, and build gates for AI agents
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
SYKE_LICENSE_KEY, GEMINI_KEYLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"syke": {
"command": "npx",
"args": [
"-y",
"@syke1/mcp-server"
],
"env": {
"SYKE_LICENSE_KEY": "your-value",
"GEMINI_KEY": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add syke --env SYKE_LICENSE_KEY=your-value --env GEMINI_KEY=your-value -- npx -y @syke1/mcp-serverCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"syke": {
"command": "npx",
"args": [
"-y",
"@syke1/mcp-server"
],
"env": {
"SYKE_LICENSE_KEY": "your-value",
"GEMINI_KEY": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"syke": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@syke1/mcp-server"
],
"env": {
"SYKE_LICENSE_KEY": "your-value",
"GEMINI_KEY": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub khalomsky, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: SYKE_LICENSE_KEY, GEMINI_KEY
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.5.4) llegó al registro hace 8 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, HotCodePush
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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: