CKB

Queries, analyzes, and secures codebases with semantic search, blast-radius analysis, ownership, and dead-code detection via MCP.

javascript

51

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "simplyliz-codemcp": {
      "command": "npx",
      "args": [
        "@tastehub/ckb",
        "mcp"
      ]
    }
  }
}

CKB is a knowledge-backed code assistant you connect to via MCP. It lets you query your codebase, understand impact, discover owners, and detect dead code, all through a unified MCP-enabled interface. You can drive it from a command line, an HTTP API, or AI assistants to ship changes with confidence and safety.

How to use

You use CKB by connecting an MCP client to the local MCP server and then sending high-level requests that combine multiple questions into a single step. Start an MCP session in your editor or CI/CD tool, choose a preset toolset that fits your workflow, and begin exploring code symbols, call graphs, ownership, risk, and tests. The system provides blast radius, reviewer suggestions, dead code detection, and architecture explanations, all tailored to the code you are examining.

How to install

Follow these steps to install and start using the MCP server with a supported client.

Configuration and usage notes

The MCP integration supports multiple clients through standard stdio connections. You configure a local MCP server by running the command shown in setup examples and then connecting your MCP-enabled tool to the local stdio transport.
When you are ready, initialize the project, index the codebase for faster queries, and connect to Claude Code or other AI assistants via MCP. You can opt into presets to reduce token usage while retaining essential capabilities.

Available tools

hotspots

Identify risky areas in the codebase based on historical usage and current changes.

diff-summary

Analyze what changed and project potential impacts across modules.

audit

Scan for exposed secrets and misconfigurations with predefined patterns.

arch

Provide an overview of architecture, dependencies, and module relationships.

status

Check system health, readiness, and current state of the MCP session.

ownership

Resolve file ownership using CODEOWNERS, git blame, and drift detection.

explore

Area exploration combining symbols, dependencies, and hotspots.

understand

Symbol deep-dive with references, callers, and explanations.

prepareChange

Pre-change analysis including impact, tests, and risk assessment.

batchGet

Fetch multiple symbols in a single request for efficiency.

batchSearch

Run several symbol searches in one call.

findDeadCode

Detect unused or unreachable code paths.

compareAPI

Evaluate API compatibility and breaking changes.

doctor

Check tooling and environment readiness with recommended actions.

findReferences

Locate all references to a symbol with real-time progress.