agentRamen MCP
Related Servers
Alternatives to agentRamen MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLocal-first code context CLI + MCP server: discover, index, and search repos; generate task-aware context packs, code maps, agent harnesses, and PR-review/merge-readiness gates for coding agents and reviewers.14524 npm3MIT
- AlicenseBqualityDmaintenanceLocal-first codebase context engine that parses code into a ranked dependency graph and serves it to AI tools via MCP for deep structural understanding.518 npm2MIT
- AlicenseCqualityCmaintenanceLocal-first codebase intelligence engine providing AI coding agents with a typed MCP toolset for understanding and navigating code repositories.10054Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLocal-first code intelligence MCP server that enables coding agents to search code, inspect structure, read exact ranges, and explore Git history with explicit token budgets.171Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.15 npm3MIT
- AlicenseNot gradedqualityDmaintenanceA local-first codebase intelligence layer for AI coding agents, providing a persistent, queryable model of a repository via an MCP server and CLI to enable structure queries instead of reading many files.1Apache 2.0
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes, and the memory workflow tools (stage/approve/publish/reject/audit) are sharply separated by lifecycle stage. There is some overlap among the read-only analysis tools — repo_impact, repo_dependencies, and repo_graph all surface dependency information, and repo_explain vs repo_context are close — but descriptions provide enough cues to choose correctly.
All 19 tools share the repo_ prefix and snake_case, with the memory tools clearly following a verb_noun pattern (stage/approve/publish/reject/audit). A few read tools are bare noun phrases (repo_context, repo_status, repo_graph) rather than verb-led, which is a minor deviation but still readable and predictable.
19 tools is at the heavy end of the range for what is essentially a repo-intelligence plus memory-approval server. The surface could likely be consolidated (e.g., merging dependency-related reads), but each tool does map to a specific query or workflow step, so nothing is purely redundant.
Coverage is strong: repository context, search, history, graph/architecture, test discovery, change tracking, and a full memory lifecycle from staging through approval, publishing, audit, and rejection. Minor gaps remain — no way to edit or delete an already published memory, and no explicit listing of one's own staged proposals.