A
licenseNot graded
qualityD
maintenanceAn MCP server that gives AI coding agents structured access to a project's architecture, rules, modules, and technical decisions.
MIT
Leeroopedia MCP Server
Officialby Leeroo-AI
Related Servers
Alternatives to Leeroopedia MCP Server
No user-submitted related servers found.
Related Servers
multivon-mcpofficial
AlicenseAqualityAmaintenanceMCP server that gives AI coding agents direct access to evaluation tools.23Apache 2.0- AlicenseNot gradedqualityCmaintenanceMCP server that bundles curated development rules and tools to teach AI agents universal coding standards, testing, planning, and requirements engineering.18 npmMIT
- AlicenseAqualityDmaintenanceAn intelligent MCP server that serves as a guardian of development knowledge, providing AI assistants with curated access to latest documentation and best practices.485 npm1MIT
- AlicenseBqualityCmaintenanceMCP server that gives AI coding assistants persistent memory, structural code graph analysis, and safe multi-agent coordination, enabling them to answer architectural questions, track decisions across sessions, and coordinate safely in multi-agent workflows.394MIT
- AlicenseAqualityCmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.3763 npm6MIT
TDQS
A3.9/5.0
Scored across 8 tools
Disambiguation4/5
Most tools have clearly distinct purposes: get_page vs search_knowledge vs query_hyperparameter_priors separate retrieval modes, and build_plan/review_plan/verify_code_math/diagnose_failure cover distinct lifecycle stages. However, propose_hypothesis overlaps noticeably with build_plan (both suggest approaches/implementation steps), and query_hyperparameter_priors can be confused with search_knowledge for config lookups.
Naming Consistency5/5
All eight tools use consistent snake_case verb_noun patterns (query_hyperparameter_priors, search_knowledge, build_plan, review_plan, verify_code_math, diagnose_failure, propose_hypothesis). get_page is the only noun-first name but is a common idiom and still clearly readable.
Tool Count5/5
Eight tools is well within the ideal 3-15 range and each maps to a distinct KB-backed capability (search, retrieve, plan, review, verify, diagnose, propose, config lookup). No tool feels redundant or padded.
Completeness4/5
The surface covers the full dev lifecycle from retrieval through planning, review, verification, and diagnosis, which matches the stated KB-assistant purpose well. A minor gap is the absence of any discovery/index tool to browse or enumerate available page IDs, leaving get_page dependent on citations from other tools.
Maintenance
ActivityMaintained
ResponsivenessNo issues