Skip to main content
Glama
ethanasm

mcp-queue-doctor

by ethanasm

Related Servers

Alternatives to mcp-queue-doctor

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables comprehensive PostgreSQL database monitoring, analysis, and management through natural language queries. Provides performance insights, bloat analysis, vacuum monitoring, and intelligent maintenance recommendations across PostgreSQL versions 12-17.
      34
      160
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Diagnoses and manages PostgreSQL logical replication including slot WAL retention, walsender lag, stuck subscriptions, and provides gated remediation tools for safe AI-driven operations.
      13
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets an LLM like Claude inspect and control an automation job queue — list jobs, check status, trigger new runs, retry failures, and pull queue-wide stats through natural language.
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      Facilitates management and optimization of PostgreSQL databases, offering analysis, setup guidance, and debugging, while ensuring secure and efficient database operations.
      3
      7 npm
      23
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Read-only PostgreSQL performance auditing via MCP. Collects metrics from PostgreSQL system views, applies deterministic checks for index, query, vacuum, configuration, and connection issues, and returns structured findings for MCP clients.
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM assistants to analyze PostgreSQL query execution plans with EXPLAIN and receive structured reports highlighting performance bottlenecks, all through read-only database access.
      3
      MIT

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo issues