CodebaseAgent-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codebase_list_librariesA | Return the public names of local libraries/codebases available for analysis. |
| codebase_start_job_related_files_searchA | Start async related-file discovery. Find files relevant to single entity/action before |
| codebase_start_job_analysisA | Start async codebase analysis. Analyze single entity/action only. Return detailed analysis, recommendations, implementation guidance, usage examples. Prefer |
| codebase_get_job_statusA | Get async analysis job status. Checks the progress of both the |
| codebase_get_job_resultA | Return the final result, error, or latest partial output for an analysis job. You must poll using |
| codebase_cancel_jobA | Request cancellation of a queued or running analysis job. |
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 6 tools
Each tool has a unique, clearly defined purpose: listing libraries, starting a related-file search, starting an analysis, checking status, fetching results, and cancelling. The two start_job tools are distinct (search vs analysis) and their descriptions explicitly differentiate them.
All tool names follow a consistent codebase_verb_noun pattern using snake_case. The start_job_* prefix is uniform, and get_job_status/get_job_result/cancel_job are intuitive and predictable.
With 6 tools, the count is well-scoped for a codebase analysis server. Each tool maps to a necessary step in the async job lifecycle, with no redundancy or bloat.
The core workflow (list libraries, start jobs, poll, retrieve, cancel) is fully covered. A minor gap is the lack of a way to list active or past jobs, which would help recover a lost job ID, but agents can work around this by storing IDs returned from start calls.