codebase-context-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 |
|---|---|
| index_codebaseA | Parse a directory into symbols and chunks, building a searchable index. Supports TypeScript, JavaScript, Python, CSS, JSON. |
| search_symbolsB | Find functions, classes, types, and other symbols by name or pattern in an indexed codebase. |
| search_codeA | BM25 full-text search across all files in an indexed codebase. Returns ranked results with matching lines. |
| get_file_outlineA | Get the structure of a file: functions, classes, imports, exports with line numbers. |
| get_project_summaryA | Get an overview of an indexed project: tech stack, file counts by language, directory structure. |
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 5 tools
Each tool has a clearly distinct purpose: indexing, symbol search, full-text search, file outline, and project summary. There is no overlap between tools, so an agent can easily select the right one.
All tool names follow a consistent verb_noun pattern (index_, search_, get_), making the set predictable and easy to navigate.
With five tools, the server is well-scoped for its purpose of providing codebase context. Each tool is necessary and there is no bloat.
The domain of codebase context is well-covered with indexing, two complementary search methods, file outline, and project summary. A tool to fetch full file content would be a minor addition, but the current set is functional and does not have critical gaps.