sove-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOVE_MCP_ALLOW_WRITES | No | Set to 'true' to enable the generate_documentation tool, which can write to source files. Defaults to false. | false |
| SOVE_MCP_ALLOWED_ROOTS | No | Path-separator delimited list of allowed roots that the server may read. Defaults to the working directory. | . |
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 |
|---|---|
| analyze_repositoryA | Builds a dependency graph for a codebase and returns a summary: file count, import edges, entry points, circular dependencies and the most complex modules. Use this instead of reading every file when you need architectural context. |
| find_entry_pointsA | Lists the modules nothing else imports — where execution starts. Useful for orienting in an unfamiliar codebase before reading any source. |
| find_circular_dependenciesA | Detects import cycles using Tarjan's algorithm. Returns each cycle with a severity based on how many modules it spans. |
| most_complex_filesA | Ranks modules by cyclomatic complexity so you can find refactoring targets without reading the codebase. |
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 targets a distinct analysis aspect, but analyze_repository overlaps by summarizing entry points, cycles, and complexity, which are also covered by the specialized tools. The descriptions clarify that the summary is high-level, while the other tools provide deeper dives.
Three tools use verb_noun naming (analyze_repository, find_entry_points, find_circular_dependencies), but most_complex_files is an adjective phrase, breaking the pattern. All names use snake_case, maintaining readability despite the inconsistency.
Four tools is well-scoped for a code analysis server, falling within the ideal 3-15 range. Each tool serves a distinct purpose in architectural analysis, and the count feels neither thin nor bloated.
The set covers the key aspects of codebase analysis: overall summary, entry points, circular dependencies, and complexity. Minor gaps exist (e.g., dependency depth, module coupling), but the core workflows for architectural understanding are complete.