repomap-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 |
|---|---|
| helloA | 헬스체크용 인사 반환 / return a greeting for a health check. |
| get_repo_mapA | 레포의 압축 맵을 반환 / return a compressed map of the repo. repo_path: 대상 레포 절대경로 / absolute path to the target repo. token_budget: 출력 토큰 예산(기본 4000) / output token budget (default 4000). focus_files / role / changed_files: Phase 3 역할별 personalization 입력 / Phase 3 inputs for role-based personalization. role="planner": 진입점 가중 / entry-point boost. role="implementer": focus_files 에 텔레포트 질량 집중 / teleport mass on focus_files. role="reviewer": changed_files + 의존자(predecessors) 가중 / changed_files + their dependents (predecessors). 반환 / returns: {repo_map, stats:{files, files_parsed_now, files_from_cache, cache_hit_ratio, moved, deleted, symbols_total, symbols_included, est_tokens, elapsed_ms}, warnings} |
| refresh_cacheA | 캐시를 갱신 / refresh the cache. full=False(기본): 증분 스캔 — 변경분만 재파싱 후 캐시 저장. full=False (default): incremental scan — re-parse only changes, then persist. full=True: 캐시 폐기 후 전체 재빌드(복구용). full=True: discard cache then rebuild from scratch (recovery). 반환 / returns: {reparsed, invalidated, elapsed_ms} reparsed: 이번에 재파싱된 파일 수 / files re-parsed this run. invalidated: 무효화(삭제)된 캐시 엔트리 수 / cache entries invalidated/removed. |
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 3 tools
Each tool has a distinct purpose: get_repo_map returns a repo map, hello is a health check, refresh_cache manages caching. No overlap.
Two tools follow verb_noun pattern (get_repo_map, refresh_cache), but 'hello' is a single word without underscore. Minor inconsistency, but still clear.
3 tools is well-scoped for a focused repo mapping utility. Each tool serves a necessary function without bloat.
Covers core functionality (map retrieval, health check, cache management). Minor gap: no explicit status tool for cache, but refresh_cache covers maintenance.