rq-mcp
Related Servers
Alternatives to rq-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to manage BullMQ Redis-based job queues through natural language, supporting operations like job monitoring, queue control, and multi-instance Redis connections. Users can add, retry, promote, and clean jobs while accessing detailed job logs and queue statistics directly within the assistant.20129 npm7MIT
- AlicenseBqualityCmaintenanceEnables AI agents to inspect a live Celery deployment over RabbitMQ or Redis — checking which workers are responding, their pools, concurrency and consumed queues, and how many messages are backed up in each queue — so agents can diagnose stuck or unrouted tasks. Read-only by default, with broker credentials masked in all output.2105 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceLets 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
- AlicenseAqualityAmaintenanceEnables LLMs to safely explore and operate Redis instances, with read-only keyspace inspection, multi-structure data access, memory and big-key analysis, slow query diagnostics, and optional opt-in write operations.473 PyPIApache 2.0
- AlicenseAqualityDmaintenanceEnables AI agents to manage and search data in Redis using natural language. Supports hashes, lists, sets, sorted sets, streams, JSON, and vector search.44MIT
- AlicenseBqualityBmaintenanceEnables AI agents to manage RabbitMQ message brokers through admin APIs, supporting multiple brokers, OAuth authentication, and mutative tools.39534 PyPI42Apache 2.0
TDQS
Scored across 12 tools
Each tool targets a distinct RQ resource or view: environment info, Redis internals, queues, jobs, results, workers, failures, and health. The only close pair is list_jobs with status=scheduled and list_scheduled_jobs, but their return shapes and descriptions make the intended use clear.
The naming is mostly predictable with get_ for single entities and list_ for collections, all in snake_case. summarize_failures and health_check deviate slightly from the get_/list_ pattern but remain readable and consistent in style.
Twelve tools is well-scoped for an RQ monitoring and inspection server. Each tool covers a meaningful part of the domain without unnecessary redundancy or bloat.
The tool surface covers the major RQ monitoring areas: environment, Redis health, queues, jobs by status, individual job details and results, scheduled jobs, workers, failure aggregation, and health diagnostics. For a read-only monitoring server, there are no obvious dead ends or missing core operations.