Codebase Explorer MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_structureA | Get a high-level overview of a codebase: languages, file count, entry points, and directory tree. |
| find_featuresC | Detect features, API routes, controllers, components, and patterns in the codebase. Optionally filter by type (e.g. 'API Route', 'Controller', 'Component', 'Test'). |
| search_symbolsC | Search for symbols/patterns across the codebase using regex. Optionally filter by file extension (e.g. 'py', 'js', 'ts'). |
| get_feature_detailC | Get detailed code context around a feature by name. The feature name is matched against detected routes, controllers, services, etc. |
| list_project_typesA | List all project types and frameworks this server can detect. |
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 distinct purpose: overview, feature detection, detailed context, project type listing, and symbol search. No overlapping functionality.
All tool names follow a consistent verb_noun pattern (e.g., analyze_structure, find_features, get_feature_detail).
With 5 tools covering overview, feature detection, detail, types, and symbol search, the set is well-scoped for codebase exploration.
Covers core exploration tasks but lacks direct file content or listing operations, which may be needed in some workflows.