reprox-mcp
Related Servers
Alternatives to reprox-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides coding agents with persistent repository context, including code maps, specs, timeline, team memory, and past session history, through MCP tools.265 PyPIApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to retrieve compact, cited repository maps through MCP tools such as search, symbol inspection, flow investigation, and deep context loading.1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.24 PyPI2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to retrieve and manage code context with hybrid search, project memory, and observability via MCP tools.29MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to persistently store and retrieve conversation history with hybrid semantic and keyword search, cross-encoder reranking, session filtering, and archiving through MCP tools.-
- AlicenseNot gradedqualityBmaintenanceProvides persistent memory for AI coding agents, enabling them to save, search (hybrid vector/BM25/concept graph), list sessions, and forget memories via MCP tools.11 npmApache 2.0
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.