Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@codeintel show findings for beancounter"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
uv tool install --editable /home/hermes/code-intelPuts 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_typeRelated MCP server: graphward
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.
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.
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.
This server cannot be deployed
Repository knowledge graph MCP server for codebase understanding and debugging.
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
