codeintel
MCP server that provides code intelligence by indexing configured repositories, extracting deterministic facts, and enabling graph queries, drift checks, and maps via Kuzu-backed MCP tools.
README
codeintel
codeintel is a uv-managed Python 3.12 code-intelligence platform. It reads configured repositories without modifying them, extracts deterministic fact JSON, and loads those facts into an embedded Kuzu graph for canned queries, raw Cypher, drift checks, maps, and MCP access.
Outputs live under out/<target>/; target repositories stay read-only.
Install (system-wide)
uv tool install --editable /home/hermes/code-intel
Puts codeintel on PATH (~/.local/bin), runnable from any directory. Editable: platform
changes take effect without reinstalling. Targets can be referenced by name or root path:
codeintel findings ~/beancounter
codeintel brief ~/beancounter --about classify_scan_type
Quickstart
codeintel targets
codeintel index beancounter # or: codeintel index ~/beancounter
codeintel query beancounter files-by-component
codeintel refresh beancounter
codeintel findings beancounter
codeintel mcp beancounter
(Inside the repo, uv run codeintel … works too and always uses the project venv.)
The query graph uses one Node table and one Edge relationship table. Contract kinds such as File, Route, Dependency, CALLS, and HANDLED_BY are stored in the kind property.
Docs
- Usage: install, index, refresh, and validated Cypher examples.
- New Target: target YAML schema and component guidance.
- Extending: adding extractors and deterministic fact rules.
- Schema: implemented node and edge kinds.
v1 Status
The v1 surface is intentionally thin: extractors write facts, the loader rebuilds a local Kuzu graph, and query tools read that graph. The richer extractors are optional registry modules, so a target can still index when a specific extractor is absent or fails. Drift snapshots are written by refresh; facts themselves remain timestamp-free for deterministic diffs.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.