RepoMind-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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| repomind_scan_workspaceA | Recursively scans a workspace directory, mapping its file structure, listing source files, and providing statistics, while ignoring binary/build folders (e.g. node_modules, .git, dist). |
| repomind_get_dependenciesA | Analyzes imports in JavaScript, TypeScript, and Python files within a target path (file or directory) to build a directed dependency graph showing local module relationships. |
| repomind_generate_diagramB | Generates a beautiful visual Mermaid diagram representing the dependency graph of the files. Can group files by their parent directories into subgraphs. |
| repomind_impact_analysisA | Calculates the downstream blast radius (reverse dependents) of modifying a target file or module, showing exactly which files depend on it directly or indirectly. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| architecture-review | Performs a structured review of the codebase architecture based on workspace structure and dependency connections. |
| blast-radius-check | Evaluates the potential downstream blast radius of modifying a target file by executing impact analysis and planning refactoring steps. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| RepoMind Workspace Dependency Graph | Full serialized JSON representation of the current workspace dependency mapping. |
TDQS
Scored across 4 tools
Each tool targets a distinct phase of repository analysis: scanning structure, computing dependencies, generating diagrams, and calculating impact. No overlap or ambiguity exists between them.
All tools follow the consistent pattern 'repomind_<verb>_<object>' with snake_case throughout. The verb-noun construction is uniform and predictable across the set.
Four tools is an ideal size for a focused repository analysis server. Each tool earns its place and there is no bloat or redundancy.
The tool set forms a complete workflow: scan a workspace, extract dependencies, visualize them, and analyze impact. No obvious gaps exist for the stated purpose of repository analysis.