CodeCompass 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_repository_infoA | š Get basic repository metadata, statistics, and key information. Atomic tool focused purely on repository-level data without file content analysis. |
| get_file_treeA | š³ Get complete directory structure and file listing with filtering options. Focused on file system structure without content analysis. |
| search_repositoryC | Search for patterns, text, functions, or classes across the entire repository with advanced filtering options. |
| get_file_contentB | š Retrieve content of specific files with smart truncation and batch processing capabilities. ā ļø FEATURES: ā¢ Batch processing with concurrent file retrieval ā¢ Automatic file validation and security checks ā¢ Rich metadata extraction (file type, language, size, line count) ā¢ Configurable processing limits and error handling ā¢ Support for multiple file formats with type detection |
| analyze_codebaseC | š¬ Comprehensive codebase analysis combining structure, architecture, and metrics. Provides unified view of code organization, design patterns, complexity, and quality indicators. |
| analyze_dependenciesC | š¦ Comprehensive dependency analysis including external packages, internal dependencies, security vulnerabilities, and version conflicts. |
| review_codeC | š Comprehensive code review combining AI insights with rule-based validation. Provides intelligent analysis, security scanning, and actionable recommendations. |
| explain_codeB | š AI-powered code explanation generating human-readable documentation, tutorials, and architectural insights. Transforms technical analysis into accessible explanations. |
| suggest_improvementsC | š” AI-powered improvement suggestions providing strategic refactoring recommendations, modernization plans, and architectural enhancements. |
| transform_codeB | š§ Apply code transformations including syntax changes, structural reorganization, framework migration, and modernization. Combines syntax-level and structural changes. |
| health_checkC | š„ System Health Check - Monitor server health, performance, and operational metrics. Provides comprehensive monitoring dashboard with real-time insights. |
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 11 tools
Most tools have distinct purposes, but there is some overlap between analyze_codebase and review_code, as both involve code analysis and could be confused for similar tasks. The descriptions help differentiate them, but the boundaries are not perfectly clear.
Tool names mostly follow a consistent verb_noun pattern (e.g., analyze_codebase, get_file_content, search_repository), with minor deviations like health_check (noun_verb) and suggest_improvements (verb_noun_plural). The naming is readable and largely predictable.
With 11 tools, the count is well-scoped for a code analysis and repository management server. Each tool appears to serve a specific function, and the number is reasonable for covering the domain without being overwhelming.
The tool set covers core aspects of code analysis, repository exploration, and AI-powered insights, but there are minor gaps such as no explicit update or delete operations for repository data, which might limit full lifecycle management. However, agents can likely work around this with the provided tools.