Coding Standards MCP Server
Related Servers
Alternatives to Coding Standards MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA server providing programming guidelines and coding standards for multiple languages, enabling access and search of best practices for C#, Go, JavaScript, Python, and TypeScript.31 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides Python and FastAPI coding best practices with searchable guidelines, code review capabilities, and actionable improvement suggestions with examples across general coding, performance, and code quality categories.-

vizpilot-mcpofficial
AlicenseNot gradedqualityDmaintenanceAccess 1000+ development protocols and steering rules directly in your IDE for technologies like Django, React, and Vue.MIT- AlicenseCqualityCmaintenanceProvides access to clean code guide documents and enables code quality inspection of external project files based on coding standards and best practices.34 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants and developers to analyze code for language-specific best practices and idiomatic patterns across programming languages, CI automation, and configuration formats.162MIT
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with professional coding standards, development best practices, and context-aware guidance through static documentation and AI-powered custom recommendations. Enables agents to access comprehensive development guidelines including coding rules, debugging techniques, and AI steering instructions.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_best_practices focuses on application-level best practices, get_style_guide on coding style guidelines, and list_templates on available templates. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern (get_best_practices, get_style_guide, list_templates) with clear, descriptive verbs and nouns. The naming is uniform and predictable across all three tools.
With only 3 tools, the server feels thin for a coding standards domain, which might include operations like validating code, applying templates, or managing standards. While the tools are well-defined, the count is borderline low for the apparent scope.
The tool surface has significant gaps for a coding standards server. It lacks CRUD operations for managing standards (e.g., create/update/delete practices or templates), validation tools, or integration with code analysis, which are core to the domain. This will likely cause agent failures in comprehensive workflows.