code-intel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_exportsA | List all exported symbols (functions, classes, types, consts) from a file or folder. Returns name, signature, file, line number, and total file lines. Use this instead of reading a whole file to discover what it contains. |
| file_outlineA | Get a structural outline of a single file: every function, class, interface, type, enum, and top-level const with line ranges. Shows both exported and non-exported symbols. Use to understand file structure before reading a specific region. |
| read_regionA | Read a specific line range from a file (max 200 lines per call). Returns numbered source lines. Use after list_exports or file_outline to read only the code you need instead of the whole file. |
| find_referencesA | Find all references to a symbol (function, class, variable, type) across a directory using ripgrep. Returns file, line, and matching text. Use to trace call chains and understand usage before modifying. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a clear, non-overlapping purpose: listing exports, file structure outlines, reading specific regions, and finding references. No ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.
Four tools is an ideal size for a code intelligence server, covering essential operations without being too sparse or overwhelming.
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.