mcp-repo-mapper
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthD | – |
| scan_repoD | – |
| find_circular_depsD | – |
| language_breakdownD | – |
| detect_frameworkD | – |
| find_entry_pointsD | – |
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
All tool names relate to repository analysis, but without descriptions, the overlap is unclear. Tools like scan_repo could encompass others, and health is generic, making it hard for an agent to distinguish precise purposes.
Most tools follow a verb_noun snake_case pattern (e.g., language_breakdown, detect_framework). The single exception is 'health', which is just a noun, causing a minor inconsistency.
Six tools is a reasonable count for a repository analysis server. It covers multiple analytical aspects without being overly numerous or too sparse.
The tool set covers common analysis tasks like language detection, entry points, circular dependencies, and health. However, it may miss basic repository information such as file listing or size, leaving potential gaps.