reprox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Path to the repository. If not provided, uses current 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 |
|---|---|
| search_memoryA | Call when you need repository context relevant to a question or task. Returns matching memories grouped by architecture, files, dependencies, packages, repository, commits, and gaps. |
| list_gapsA | Call when you want to find known missing, risky, or incomplete parts of the repository. Returns all gap memories ordered by severity with their location. |
| get_gapA | Call when you need the full context for one known gap. Returns that gap and every memory it explicitly references. |
| get_relatedA | Call when you need context connected to a particular memory. Returns memories it references and memories that reference it. |
| get_architectureA | Call when you need a broad structural overview of the repository. Returns every architecture and repository memory. |
| get_timelineA | Call when you need repository history, releases, or recent change context. Returns commit, release, and timeline memories ordered newest first. |
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
Each tool has a clear, distinct purpose: search for context, list/get gaps, get related memories, get architecture, and get timeline. Overlap with the generic search is acceptable because the specific getters are clearly scoped to particular memory types.
All tool names use snake_case and an imperative verb prefix like search_, list_, or get_. The only minor deviation is get_related, which uses an adjective rather than a clear noun object, but the pattern remains highly predictable.
With six tools, the server is well-scoped for a repository-context memory retrieval service. Each tool covers a meaningful access pattern without unnecessary redundancy or bloat.
The tool surface covers the full read-only retrieval lifecycle: broad search, specific gap lookup, relationship traversal, architecture overview, and timeline/history access. No significant missing operation is apparent for the stated purpose.