Last updated: April 28, 2026
SYKE is an open-source MCP (Model Context Protocol) server that gives AI coding tools — like Claude Code, Cursor, Windsurf, and Copilot — dependency awareness of your codebase. It builds a live dependency graph and exposes tools your AI can call to check impact before modifying files, run a mandatory build gate, detect hub files, and perform optional BYOK AI analysis.
Run SYKE with npx @syke1/mcp-server@latest and add it to your AI tool's MCP configuration file. Once running, your AI agent automatically discovers the available tools via the MCP protocol. When the AI is about to modify a file, it calls tools like check_safe or gate_build. SYKE analyses your local file system, computes the dependency graph, and returns a verdict — all on your machine. If you add your own Gemini, OpenAI, or Anthropic key, optional AI tools can use that provider directly.
Yes. SYKE performs 100% local structural analysis. Your source code, file paths, dependency graph, and analysis results are not sent to SYKE's servers. If you configure a Gemini, OpenAI, or Anthropic key, only the optional AI prompt payload goes directly from your local SYKE process to that provider. See the Security page for the current data flow summary.
This is usually one of three issues:
npm install -g npx in a terminal to install it globally.Set-ExecutionPolicy RemoteSigned -Scope CurrentUser.BYOK means Bring Your Own Key. SYKE does not sell model access. If you want optional AI tools like ai_analyze or scan_project, generate a key from the provider you want to use and add it to your local configuration. SYKE currently supports Gemini, OpenAI, and Anthropic keys.
No. The SYKE MCP server is open source and publicly available with no subscription paywall. Local analysis features are free to run. If you use optional AI analysis, any model usage is billed by your chosen provider, not by SYKE.
No license key is required for the local MCP server. A website account may still be useful for optional dashboard or account features, but installing and running SYKE locally does not depend on a paid license flow.
SYKE supports 8 languages with zero configuration required: TypeScript, JavaScript, Dart, Python, Go, Rust, Java, C++, and Ruby. Language detection is automatic based on file extensions. You do not need to specify your stack anywhere.
Yes. SYKE implements the standard MCP protocol, which is supported by any MCP-compatible AI tool. This includes Claude Code, Cursor, Windsurf, and any other editor or agent that supports MCP servers. The configuration format (an mcp.json or equivalent settings file) may vary slightly between tools, but the server itself is fully compatible.
Yes. The dependency graph, impact analysis, build gate, hub-file discovery, warnings, and dashboard can run without any AI provider key. BYOK is only needed for the optional semantic-analysis and onboarding-document workflows.