Skip to main content
Glama
dothinh115

code-intel-mcp

by dothinh115
README.md
# code-intel-mcp

MCP server for efficient codebase exploration by coding agents. List exports, get file outlines, read targeted regions, and find references — without loading whole files into context.

## Tools

| Tool | Input | Output | When to use |
|---|---|---|---|
| `list_exports` | path (file/folder), filter?, depth? | Name + signature + line + totalLines | Discover what a file/folder contains |
| `file_outline` | path (file), exportedOnly? | All symbols with line ranges | Understand structure before reading |
| `read_region` | path, start, end (max 200 lines) | Numbered source lines | Read only the code you need |
| `find_references` | symbol, path (dir), filePattern?, maxResults? | File:line + context | Trace call chains and usage |

## Recommended agent workflow

```
1. list_exports(path, filter) → discover what exists and where
2. file_outline(file) → understand structure and line ranges
3. read_region(file, start, end) → read only the relevant ±30 lines
4. find_references(symbol, dir) → trace who calls it before modifying
```

## Setup

### Any MCP-compatible client (via npx)

No local install needed. Point your MCP client at:

```
command: npx
args: ["-y", "@dothinh/code-intel-mcp"]
```

### Codex (desktop app / CLI)

Add to `~/.codex/config.toml`:

```toml
[mcp_servers.code-intel]
command = "npx"
args = ["-y", "@dothinh/code-intel-mcp"]
```

### Cursor

Add to `.cursor/mcp.json` (project-level) or global MCP settings:

```json
{
  "mcpServers": {
    "code-intel": {
      "command": "npx",
      "args": ["-y", "@dothinh/code-intel-mcp"]
    }
  }
}
```

### Claude Code

```bash
claude mcp add code-intel -- npx -y @dothinh/code-intel-mcp
```

### Windsurf / Cline / Continue / other MCP clients

Use the same `npx` command and args in your client's MCP server configuration. The server communicates over stdio using newline-delimited JSON-RPC.

## Requirements

- Node.js >= 20
- `rg` (ripgrep) on PATH — used by `find_references`

## Supported languages

TypeScript, JavaScript, Vue SFC, and Svelte for export detection and file outlines. `find_references` works with any text file that ripgrep can read (Python, Go, Rust, etc.).

## Local development

```bash
git clone git@github.com:dothinh115/code-intel-mcp.git
cd code-intel-mcp
yarn install
yarn build
node dist/index.js   # starts MCP server on stdio
```

## License

MIT

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a clear, non-overlapping purpose: listing exports, file structure outlines, reading specific regions, and finding references. No ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.

Tool Count5/5

Four tools is an ideal size for a code intelligence server, covering essential operations without being too sparse or overwhelming.

Completeness5/5

The set provides a complete workflow for code exploration: discover exports, understand structure, read code, and find usages. No obvious gaps for its intended purpose.

Maintenance

ActivityStale
ResponsivenessNo issues