← Back to directory
C

CKB

Community
Know your code. Change it safely. Ship with confidence.
Category
Dev Tools #327 of 438
Stars
★ 110 Popular
Transport
stdio (local process)
Runtime
Node.js 16+
Credentials
No credential needed
License
Other / unspecified
Last commit
Tools
39
43FMRS · D

CKB is a feature-rich code intelligence MCP server offering a comprehensive toolset (80+) covering navigation, impact analysis, architecture, security, ownership, and quality. Its compound operations and presets significantly reduce AI token consumption. The main strengths are static analysis and multi-language support, though quality varies (Go best, PHP experimental). It requires indexing, which can become stale, and does not handle dynamic behavior. Overall, it is highly useful for refactoring, review, and AI-assisted development, but be mindful of static analysis limitations and index maintenance.

Strongest · Setup experience 12/20 Weakest · Reliability 5/20

Reliability
5/20
Security and permissions
8/20
Maintenance
6/20
Documentation
12/20
Setup experience
12/20
Why each score
Reliability 5/20
Only the manifest, README, and metadata were supplied; no source, CI, or tests are available, so the MCP startup, init handshake, and declared tool behavior cannot be verified. The manifest repository points to SimplyLiz/CodeMCP instead of ckb, the manifest version 8.0.3 conflicts with README's v9.3.0, and tool counts (80+ vs 110) are inconsistent, so the score is conservatively low.
Security and permissions 8/20
No red-line issues such as malware, credential theft, or real secrets in install examples were found. The documentation claims token scopes, secret scanning, and allowlists, but the source is unavailable to verify credential storage, least privilege, or confirmation of dangerous operations. The HTTP service and optional LIP daemon enlarge the attack surface, and missing implementation evidence prevents a higher score.
Maintenance 6/20
The repository is not archived and has open issues; the README mentions an npm package and changelog, but the license is NOASSERTION, leaving licensing unclear. Commits, release cadence, dependency updates, and security-response channels cannot be verified from the supplied material, and the repository/version inconsistencies further reduce confidence.
Documentation 12/20
The README broadly covers installation, CLI, HTTP API, MCP client setup, presets, limitations, and wiki links, forming a layered documentation base. However, tool parameters, troubleshooting, and cost details rely on external wiki pages without reviewable evidence, and conflicting version/tool-count statements reduce credibility.
Setup experience 12/20
The install path looks clear: one npm/npx command, client configuration examples for multiple assistants, Windows wrapping, and environment variable notes. However, no CI or test evidence in the static material proves this path executes successfully, and the manifest repository URL differs from the README clone URL, creating traceability confusion. Given the static calibration cap of 15, a conservative score of 12 is given.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local files

Best for

  • Developers using AI assistants who want them to have precise code awareness
  • Teams with large codebases needing efficient navigation
  • Anyone doing refactoring who wants to understand impact
  • Code reviewers who need the full picture of changes
  • Tech leads tracking architectural health over time

Not for

  • Dynamic dispatch or runtime behavior analysis (use a debugger)
  • Generated code that isn't indexed
  • Code generation, linting, or formatting
  • Cross-repo calls (use federation for this)

Required permissions

  • Read access to codebase files and git history
  • Generate and maintain SCIP indexes (local files)
  • Execute the MCP server process via stdio
  • Optionally create API tokens for authentication when using the index server
  • Optional network access for HTTP API server

Risks and side effects

  • SCIP indexes may become stale, leading to inaccurate references or impact analysis
  • Indexing large codebases can be time and disk intensive
  • Dynamic or reflective code may be misanalyzed
  • Requires installing SCIP indexers, and language support quality varies
  • Inputs are not sanitized, so verify outputs

Setup

Before you start

Runtime:Node.js 16+

Other optional settings (1)
CKB_REPO optional Path to the repository to analyze; only required for clients without project context such as Claude Desktop. Set it to your own repo path.

Options: 1) npm (recommended): npm install -g @tastehub/ckb; 2) Homebrew (macOS/Linux): brew tap SimplyLiz/ckb && brew install ckb; 3) Build from source: git clone https://github.com/SimplyLiz/CodeMCP.git && cd CodeMCP && go build -o ckb ./cmd/ckb. After installation, run ckb init in your project directory, optionally ckb index to generate SCIP index, then ckb setup to connect Claude Code. You can also manually add npx @tastehub/ckb mcp to your MCP config.

claude_desktop_config.json
{
  "mcpServers": {
    "ckb": {
      "command": "npx",
      "args": [
        "@tastehub/ckb",
        "mcp"
      ]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "ckb": {
      "command": "npx",
      "args": [
        "@tastehub/ckb",
        "mcp"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add ckb -- npx @tastehub/ckb mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

Run ckb init and ckb index in your project, then start the server with npx @tastehub/ckb mcp; tools like explore, understand, and impactAnalysis should appear in the client's tool list, and asking "what calls this function?" should return indexed results.

Troubleshooting

  1. Run `ckb status` to check system health
  2. Run `ckb doctor --tier standard` to check language tools
  3. If index is outdated, run `ckb index` or use `ckb mcp --watch` for auto-refresh
  4. For TypeScript monorepos, may need `--infer-tsconfig` flag
  5. C/C++ requires `compile_commands.json`
  6. For best search quality, install LIP daemon manually: `cargo install lip-cli` and start with `lip daemon --socket ~/.local/share/lip/lip.sock`

Things to try

Once connected, you can ask your AI assistant things like:

  • What calls the HandleRequest function?
  • What's the blast radius if I change UserService?
  • Who owns the internal/api module and who should review changes there?
  • Scan this repo for exposed secrets and credentials

Tools 39

explore read-only
Area exploration: symbols, dependencies, hotspots
understand read-only
Symbol deep-dive: refs, callers, explanation
prepareChange read-only
Pre-change analysis: impact, tests, risk
batchGet read-only
Fetch up to 50 symbols at once
batchSearch read-only
Run up to 10 searches at once
searchSymbols read-only
Semantic search for symbols
findReferences read-only
Find all references to a symbol
callGraph read-only
Generate call graph
Show 31 more tools
traceUsage read-only
Trace usage of a symbol
findEntrypoints read-only
Find code entrypoints
impactAnalysis read-only
Analyze impact scope of changes
riskScore read-only
Compute risk score
affectedTests read-only
Identify affected tests
compareAPI read-only
Compare API backward compatibility
blastRadius read-only
Determine blast radius
architecture read-only
Get architecture overview
moduleOverview read-only
Get module overview
adrs read-only
Retrieve architecture decision records
dependencyGraph read-only
Generate dependency graph
explainOrigin read-only
Explain origin of a symbol
findDeadCode read-only
Detect dead code
couplingAnalysis read-only
Analyze coupling
complexity read-only
Compute code complexity
hotspots read-only
Identify hotspot areas
ownership read-only
Find code ownership
reviewerSuggestions read-only
Suggest reviewers
driftDetection read-only
Detect ownership drift
detectSecrets read-only
Detect exposed secrets
scanCredentials read-only
Scan for credentials
securitySensitive read-only
Identify security-sensitive code
docSymbols read-only
Doc-symbol linking
docStaleness read-only
Check doc staleness
docCoverage read-only
Doc coverage metrics
federation read-only
Cross-repo queries
openTelemetry read-only
OpenTelemetry integration
observedUsage read-only
Observed usage in production
streamReferences read-only
Stream references
streamSearch read-only
Stream search results
expandToolset read-only
Dynamically expand toolset

Use cases

Semantic code navigation in AI-assisted development (Claude Code, Cursor, etc.)
Impact analysis and risk scoring before refactoring
Identifying affected tests to narrow down test runs
Code ownership tracking and reviewer suggestions via CODEOWNERS and git blame
Dead code detection and tech debt tracking
Secret scanning and credential detection for security
Architecture mapping and module understanding
CI/CD integration for PR review and quality gates

Supported clients

Claude Desktop
Claude Code
Cursor
Windsurf
VS Code
OpenCode
Grok

Listed from the project's documentation, not tested by this site.

Overview

CKB (Code Knowledge Backend) transforms your codebase into a queryable knowledge base. It provides 80+ MCP tools, CLI, and HTTP API for symbol navigation, impact analysis, architecture mapping, dead code detection, secret scanning, code ownership, and more. Leveraging SCIP indexes, LSP, Git, and optional LIP semantic embeddings, it offers precise code intelligence for AI assistants or as a backend for CI/CD and custom tooling. It features compound operations like explore, understand, and prepareChange that reduce AI tool calls by 60-70%, and presets that cut token usage by up to 77%. CKB has tiered language support, with Go, TypeScript, JavaScript, and Python being best.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

Source revision 768a194c14fb Data synced 2026-10-12 Read the FMRS scoring method