A
licenseNot graded
qualityB
maintenanceProvides a quality framework and enforceable conventions for AI coding assistants, ensuring code quality, environment hygiene, and project standards across multiple AI tools.
69 npm
3
-
MCP Standards
by airmcp-com
Related Servers
Alternatives to MCP Standards
No user-submitted related servers found.
Related Servers
- 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.138 npm5MIT
- AlicenseAqualityAmaintenanceA 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.6107 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables automatic knowledge capture and injection of guardrails for AI assistants like Claude and Cursor, improving code quality and preventing recurring mistakes.9 npmMIT
- FlicenseNot gradedqualityDmaintenanceAutomatically enforces team coding standards in AI-assisted development by providing an MCP server that AI assistants can query for language-specific standards, style guides, and best practices.-
TDQS
B3.2/5.0
Scored across 9 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues