MCP DevTools Server
Related Servers
Alternatives to MCP DevTools Server
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseCqualityDmaintenanceAn MCP server that enables persistent memory, structured thinking sessions, and project-based knowledge management for Claude. It includes specialized coding tools for package discovery and reinvention prevention by validating code against existing libraries and APIs.173MIT
- AlicenseCqualityFmaintenanceSingle MCP server providing over 500 developer tools for Claude Code, covering security, testing, documentation, and more.500546 npm3MIT

preflightofficial
AlicenseNot gradedqualityDmaintenanceAn MCP server for Claude Code that catches vague prompts, applies triage and correction pattern learning, and provides semantic search, cross-service contracts, and scorecards to reduce wasted tokens.19 npm13MIT- FlicenseAqualityBmaintenanceMCP server that enables Claude Code to delegate tasks to DeepSeek and other LLMs, offering 20 tools for code review, analysis, testing, and code generation.201-
- -licenseNot gradedqualityNot gradedmaintenanceA universal MCP server that acts as a code quality gate for AI assistants, providing pre-generation guidance, post-generation review, and root cause analysis to improve code quality.-
TDQS
Scored across 71 tools
Most tools are clearly distinguished by language prefixes and specific purposes. Some overlap exists (e.g., multiple test tools), but descriptions and context help agents select correctly.
Tools follow snake_case, but prefixes are inconsistent. Language-specific tools use 'language_action' pattern, while general tools like 'analyze_command' and 'jq_query' lack prefixes, creating a mixed convention.
With 71 tools, the server is extremely large for a single MCP server. It tries to cover too many domains, leading to an unfocused and overwhelming toolset. A more scoped approach would be better.
The toolset covers a wide range of development tasks: linting, testing, building, security, profiling, etc. Minor gaps exist (e.g., no Rust tools), but overall it provides comprehensive support for common workflows.