mcp-queue-doctor
Related Servers
Alternatives to mcp-queue-doctor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to diagnose a Python backend stack — Postgres, Celery, Redis and logs — in a single tool call, returning findings, a merged timeline of events, and possible cause-effect chains. All checks are strictly read-only, so an assistant can inspect blocked queries, missing workers, queue backlogs, Redis memory pressure and log error spikes without ever modifying anything.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to monitor and operate PostgreSQL databases through natural language queries, covering performance analysis, bloat detection, lock/deadlock monitoring, autovacuum and schema inspection, and maintenance recommendations with read-only, extension-optional workflows across PostgreSQL 12–18.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect and monitor PostgreSQL databases using natural language, covering performance analysis, bloat detection, lock/deadlock monitoring, autovacuum, schema inspection, and maintenance recommendations across PostgreSQL 12–18 without requiring extensions.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect and monitor PostgreSQL 12-18 databases through natural language, covering performance analysis, slow-query identification, bloat and lock detection, autovacuum health, replication/WAL status, and schema exploration. All operations are read-only and work without requiring any extensions, though pg_stat_statements and pg_stat_monitor optionally enhance query analytics.-
- AlicenseAqualityAmaintenanceOffline PostgreSQL diagnostics: reviews SQL, risky migrations, candidate indexes and EXPLAIN JSON plans without database credentials or executing statements.589 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect and monitor PostgreSQL 12–18 databases through natural language, covering performance and slow-query analysis, table bloat detection, connection/lock and deadlock monitoring, autovacuum and VACUUM effectiveness, replication/WAL status, and schema and relationship discovery. All operations are read-only and production-safe, working with regular user permissions on RDS/Aurora, with optional pg_stat_statements and pg_stat_monitor extensions for deeper query analytics.-
TDQS
Scored across 8 tools
Each tool targets a clearly distinct concern: aggregate diagnosis, server/schema info, queue-level health, failed jobs, stuck jobs, schedule listings, missed schedules, and individual job records. The only near-overlap (schedule_status vs missed_schedules) is resolved by one being the full set and the other a filtered diagnostic view.
Tool names are uniformly lowercase snake_case and mostly follow a descriptive noun-phrase pattern like failed_jobs, queue_overview, and schedule_status. The single verb-only name diagnose breaks the pattern slightly, but it is still consistent with the diagnostic domain and not confusing.
Eight tools is a well-scoped size for a queue diagnosis server. Each tool covers a distinct diagnostic need without redundancy or filler, and the count is squarely in the comfortable mid-range.
The tool surface covers the full diagnostic workflow: server health, per-queue health, failed/stuck jobs, schedule monitoring, missed schedule detection, and deep-dive job details. There are no obvious dead ends; the diagnose tool ties the narrower tools together, and job_detail lets an agent follow up on any surfaced error.