code-intel
Click on "Install 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., "@code-intelreview this diff and give a risk score"
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.
code-intel
code-intel is a persistent MCP bridge for code exploration and diff-aware review. It keeps one CodeGraph MCP connection alive for the lifetime of the outer MCP server and exposes a deliberately small interface:
explore: relevant source, call paths, and blast radius.review: diff parsing, changed-symbol mapping, impact collection, explainable risk scoring, and a structured report.
The npm package is @team-harness/code-intel. It installs CodeGraph as an exact dependency; end users do not need a separate global CodeGraph installation.
Install
npm install -g @team-harness/code-intel
code-intel install --target codex,claude
cd /path/to/project
code-intel initinstall registers the code-intel MCP server globally for the selected agents.
It also adds a marker-delimited guidance block to Codex ~/.codex/AGENTS.md
and Claude ~/.claude/CLAUDE.md, directing both agents to use explore for
code discovery and review before finalizing changes. Claude receives the
mcp__code-intel__* permission in ~/.claude/settings.json.
The installer preserves unrelated configuration, backs up each changed existing
file as <file>.code-intel.bak, and is idempotent. It does not initialize any
repository. Run code-intel init inside each project to create its local index;
run the same command again to incrementally refresh an existing index. The MCP
process keeps the connection warm and CodeGraph watches indexed source changes
after startup.
Related MCP server: graphward
MCP configuration
{
"mcpServers": {
"code-intel": {
"command": "npx",
"args": [
"-y",
"@team-harness/code-intel",
"mcp",
"--path",
"/absolute/path/to/project"
]
}
}
}The agent sees only explore and review. Internally, the review module also uses CodeGraph's node and impact tools; they are not exposed on the outer MCP surface.
Review modes
Review the current working tree, including staged, unstaged, and untracked files:
code-intel review /path/to/projectReview a branch or pull-request range:
code-intel review /path/to/project --base origin/main --head HEADGet the structured report:
code-intel review /path/to/project --jsonThe MCP review tool accepts the same base and head, or a caller-supplied unified diff. With no diff or range it reviews the target project's current working tree.
Architecture
Agent / MCP host
|
| stdio MCP: explore, review
v
code-intel (long-lived process)
|
+-- CodeGraphBridge ---- persistent MCP client ---- CodeGraph MCP
|
+-- ReviewAnalyzer
+-- structured unified-diff parser
+-- hunk -> current symbol mapping
+-- node / impact / explore queries
+-- deterministic risk scorer
+-- Markdown + structured JSON reportThe bridge lazily starts CodeGraph on the first tool call, reuses that connection for later calls, and reconnects once if the child exits during a read-only request. CodeGraph may additionally share its own per-project daemon across MCP clients.
Review semantics
Risk scores are deterministic and explainable. Signals currently cover sensitive paths, missing test-file changes, graph impact width, diff size, file count, and deleted files. They prioritize review effort; they are not claims that a bug exists.
Changed hunks are mapped to the nearest preceding symbol in the current CodeGraph index. Deleted files and symbols can be absent from that index, so deletion findings are explicitly treated as uncertain. A future base-revision index can remove that limitation.
Library use
import { CodeIntelClient } from '@team-harness/code-intel';
const codeIntel = new CodeIntelClient({ projectPath: process.cwd() });
try {
const context = await codeIntel.explore('AuthService login');
const report = await codeIntel.review();
} finally {
await codeIntel.close();
}CodeIntelClient is the public library boundary. Its explore() and review()
methods share one persistent CodeGraph connection; the bridge and analyzer are
internal implementation details.
Development
npm install
npm run typecheck
npm test
npm run buildUpstream
This project is powered by @colbymchenry/codegraph, licensed under MIT. code-intel is an independent Team Harness integration and is not an official CodeGraph package.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceMCP server that builds a deterministic, source-traceable knowledge index of any codebase, enabling glossary lookup, code graphs, and exact-token search with every fact linked to its source file and line.241MIT
- Alicense-qualityBmaintenancePrivate, local-first code intelligence MCP server that builds a static graph of repositories and exposes search, architecture, impact analysis, and review tools via MCP.MIT
- Alicense-qualityCmaintenanceA persistent code-intelligence MCP server that builds a queryable knowledge graph of your codebase, enabling AI assistants to perform cross-file structural reasoning, dependency analysis, and blast radius detection.6MIT
- Flicense-qualityBmaintenanceRemote MCP server for code graph analysis, offering tools for repo queries, symbol impact paths, branch context packing, and dependency hotspot reporting.
Related MCP Connectors
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free.
A MCP server built for developers enabling Git based project management with project and personal…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/team-harness/code-intel'
If you have feedback or need assistance with the MCP directory API, please join our Discord server