Error Debugging MCP Server
Related Servers
Alternatives to Error Debugging MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides real-time debugging, code quality monitoring, and performance insights for React/Next.js applications with features including Chrome DevTools integration, breakpoint management, complexity analysis, and live error streaming.20 npm1-
- AlicenseNot gradedqualityDmaintenanceProvides AI-powered development tools including code generation, refactoring, debugging, performance optimization, and test generation, along with smart prompts for code analysis and documentation, and a built-in knowledge base of coding best practices.MIT
- AlicenseAqualityDmaintenanceAn intelligent debugging assistant that automates the debugging process by analyzing bugs, injecting HTTP-based debug logs into code across multiple environments (browser, Node.js, mobile, etc.), and iteratively fixing issues based on real-time feedback.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI to automatically diagnose bugs by querying logs, tracing call chains, and analyzing code across multiple log platforms like Elasticsearch and Loki.MIT
- AlicenseBqualityAmaintenanceProvides a universal developer operations and diagnostics toolkit with sandboxed code execution, algorithm stress testing, security secret scanning, AST-based code fixes, and a visual dashboard for ERD, port/process inspection, and differential testing.2826 npm3MIT
- FlicenseAqualityDmaintenanceEnables LLMs to automatically diagnose coding errors through codebase search, test execution, and live debugger integration (DAP/V8 CDP). Provides a secure, policy-gated environment for investigating failures while preventing destructive operations.9-
TDQS
Scored across 2 tools
detect-errors (finding errors across sources) and analyze-error (deep analysis of a specific error) have fairly distinct purposes and reasonable boundaries. There is some conceptual overlap since both operate on errors, but the detect-then-analyze split is understandable.
Both tools follow a consistent hyphenated verb_noun pattern (detect-errors, analyze-error). The only minor deviation is singular ('error') vs plural ('errors'), which does not harm readability.
Two tools is thin for a debugging server, though each earns its place. The scope feels borderline minimal—a couple more operations would round out the surface.
Detect and analyze cover discovery and diagnosis, but there are notable gaps: no way to resolve, suppress/ignore, or list/track errors, leaving the error lifecycle incomplete.