repo-map-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 |
|---|---|
| index_repositoryB | Walk root_path, hash/parse changed files, update the .repo-index/index.json map. Returns a summary. |
| get_repo_mapA | Return the JSON repo index for root_path, optionally scoped to dir_prefix. Call this before exploring. |
| search_filesA | Substring search over fileName/description/funcs in the repo index for root_path. |
| get_stale_filesB | Return files in root_path's index whose description is stale (funcs changed), with their funcs. |
| set_descriptionB | Write a one-line description for path in root_path's index and clear its stale flag. |
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 5 tools
Each tool has a distinct responsibility: setting descriptions, indexing, fetching the map, searching, and retrieving stale files. No overlap or ambiguity exists between them.
All tools follow a consistent snake_case verb_noun pattern (set_description, index_repository, get_repo_map, search_files, get_stale_files). Predictable and uniform.
5 tools is a well-scoped size for a focused repository indexing server. Each tool earns its place with a clear role, no redundancy.
The tool surface covers the core workflow: indexing, description management, retrieval, search, and staleness detection. No obvious gaps; the lifecycle is fully addressed.