MCP Standards
Related Servers
Alternatives to MCP Standards
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Codex, Claude Code, and ChatGPT to discover project-scoped working styles and load version-bound task instructions and review criteria on demand, then check work against the same instruction set.220 npmMIT
- FlicenseNot gradedqualityBmaintenanceProvides a quality framework and enforceable conventions for AI coding assistants, ensuring code quality, environment hygiene, and project standards across multiple AI tools.83 npm3-
- FlicenseBqualityDmaintenanceAn MCP server that enables Claude to learn from user corrections by recording them as persistent rules in CLAUDE.md files. It manages project-specific or global guidelines to ensure the assistant avoids repeating the same mistakes in future sessions.24-
- AlicenseAqualityDmaintenanceManages project standards, configurations, and API debugging for AI-assisted development, ensuring unified development practices across teams and machines.1348 npm6MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to retain persistent identity, searchable cross-session memory, and self-evolving behavioral frameworks across conversations. It tracks user corrections as patterns, detects improvement trends, and reflects on accumulated signals to refine judgment over time.6 npmMIT
- AlicenseAqualityBmaintenanceA smart documentation system that helps AI assistants understand and follow your project's conventions by automatically discovering, routing, and managing AI_README.md guide files.6100 npm3MIT
TDQS
Scored across 9 tools
Most tools have distinct purposes, but some potential overlap exists between 'suggest_claudemd_update' and 'update_claudemd' where an agent might need to understand the difference between suggestion and application. The core memory operations (add_episode, list_recent, search_episodes) are clearly differentiated, and export/learning tools serve separate functions.
All tools follow a consistent verb_noun naming pattern with snake_case throughout. The naming convention is predictable and readable, with clear action-object relationships (e.g., add_episode, search_episodes, update_claudemd). No mixed conventions or style deviations are present.
With 9 tools, the count is well-scoped for a knowledge/standards management server. Each tool appears to serve a specific purpose in the workflow (memory management, export, learning, standards generation), and none seem redundant or unnecessary given the domain.
The tool set covers core workflows for knowledge management (add, list, search), learning from corrections, and standards generation/updating. A minor gap exists in direct memory modification beyond adding episodes (e.g., no update/delete episode tools), but agents can likely work around this through the learning system. The export and auto-generation tools provide good coverage for the stated purpose.