ChatGPT Plugin

Durabull: BullMQ & Redis Admin

Manage queues. Retry jobs.

Brand: Unknown

Category: Pending
Primary Subcategory: Observability, Monitoring & Incident Response

Integration details

Description

Administer BullMQ queues and monitor Redis health directly from your conversation. Built for developers and operators running background jobs, Durabull helps you diagnose backlogs, investigate failures, and recover work. Find jobs across queues, inspect redacted payloads, results, logs and stack traces, and review throughput, workers and recurring schedules. Check Redis memory, CPU, fragmentation, clients and health history. Review incidents and notification delivery, acknowledge or resolve alerts, and snooze alert rules. When you request a change, retry failed jobs, promote delayed jobs, or pause and resume queues. Supported MCP Apps hosts provide interactive queue, job, schedule, alert and health views. Connect Durabull Cloud or your self-hosted installation with scoped OAuth access. You need a Durabull account and permission to access the relevant connections. The plugin supports queue operations and Redis health diagnostics; it does not execute arbitrary Redis commands, edit keys or job payloads, delete jobs, purge queues, scale workers, or create or edit schedules and alert rules.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Observability, Monitoring & Incident Response
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-10-29
Tool count: 30
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Observability, Monitoring & Incident Response

View Category

Listed in alphabetical order

Primary Subcategory

API Status CheckComing soonGet notified

AverthComing soonGet notified

Better StackComing soonGet notified

BiggyComing soonGet notified

BirdieComing soonGet notified

Durabull: BullMQ & Redis AdminComing soonGet notified

Tools

30 tools agents can invoke

Acknowledge a firing alert event on behalf of the signed-in user. The event stays open and still auto-resolves. Only delegated (user) principals can acknowledge; service accounts receive validation_error. Requires scope: mcp:failures:write.
acknowledge_alert_event
One-call health check for a connection: discovery status, aggregated job counts across up to 100 queues, paused queues, queues with backlog but no workers, top queues by failed and waiting jobs, total workers, and (when scopes allow) open alert counts and the latest Redis health sample. Use it first when asked "how is this system doing". Requires scope: mcp:jobs:read. Optional scopes that add detail: mcp:failures:read, mcp:diagnostics:read.
get_connection_overview
Deterministic failure triage for one job: picks the strongest signal (failedReason, latest stacktrace, or last log lines), lists related alert events, and rates confidence. Stacktraces and logs need mcp:logs:read; related alerts need mcp:failures:read. Missing evidence is reported in skippedSources rather than failing the call. Requires scopes: mcp:diagnostics:read, mcp:jobs:read. Optional scopes that add detail: mcp:logs:read, mcp:failures:read.
explain_job_failure
Locate a job by id when the queue is unknown. Scans up to 100 discovered queues on the connection and returns every queue containing that job id. Prefer get_job when the queue is already known. Requires scope: mcp:jobs:read.
find_job
Redis server health for a connection: latest sample (memory %, CPU %, fragmentation, clients, blocked clients, evictions/min, rejected connections/min), active redis_health alert thresholds, and a bounded time series aggregated by max per bucket. Requires scope: mcp:diagnostics:read.
get_redis_health
Detail for one alert event including acknowledgement, notification timing, and notification deliveries (channel, status, attempts, last error, external link). Delivery targets are omitted. Requires scope: mcp:failures:read.
get_alert_event
Detail for one alert rule plus its five most recent events. Requires scope: mcp:failures:read.
get_alert_rule
Open alert counts for a connection split by acknowledgement, broken down by queue and by rule, plus rule state counts (active, snoozed, disabled). Cheap first call when asked "is anything alerting". Requires scope: mcp:failures:read.
get_alert_summary
Alert events (incidents) for a connection, newest first. Filter by queue, job id, status (firing, resolved, suppressed), acknowledgement, or rule. Suppressed events are informational cooldown records. Requires scope: mcp:failures:read.
get_failure_events
Full detail for one job: state, attempts, payload (data), options, progress, return value, failure reason, and stacktrace count. Sensitive keys and inline secrets are redacted and long strings truncated. Requires scope: mcp:jobs:read.
get_job
Paginated log lines written by the worker via job.log(). Oldest first; use the cursor to page toward the newest lines. Requires scope: mcp:logs:read.
get_job_logs
Stacktraces recorded for each failed attempt of a job, newest attempt first. attemptNumber counts from 1; isLatest marks the most recent failure. Requires scope: mcp:logs:read.
get_job_stacktraces
Detail for one queue: paused state, job counts by state, number of job schedulers, and the workers currently attached (id, address, age, idle time). Requires scope: mcp:jobs:read.
get_queue
Throughput metrics for one queue over a window of up to 1440 minutes: completed/failed counts, success and failure rates, per-minute averages, longest streaks, lifetime totals, estimated drain time, live counts, and worker/scheduler counts. Requires scope: mcp:diagnostics:read.
get_queue_metrics
Detail for one job scheduler including its job template (name, data, options), schedule, next run, and recent failure statistics. Requires scope: mcp:jobs:read.
get_scheduled_job
Workers attached to queues on a connection with age and idle time. Pass queueName for one queue, or omit it to page through every queue (up to 50 queues per call). Requires scope: mcp:jobs:read.
get_workers
Alert rules configured for a connection with type, thresholds (config), queue filters, cooldown, state (active, snoozed, disabled), notification channels (secrets removed), and open event counts. Requires scope: mcp:failures:read.
list_alert_rules
Paginated job summaries for one queue. Filter by state (status), a case-insensitive substring of the job name (name), or an exact job id (jobId). Name filtering scans up to 10,000 jobs, so combine it with status on large queues. Requires scope: mcp:jobs:read.
list_jobs
List discovered BullMQ queues on a connection with paused state and live job counts (waiting, active, delayed, completed, failed, paused, prioritized). Paginated and alphabetical. Requires scope: mcp:jobs:read.
list_queues
BullMQ job schedulers (repeatable jobs) with cron pattern or interval, timezone, next run, iteration count, and recent failure counts. Pass queueName for one queue, or omit it to walk the whole connection (up to 25 queues or pageSize schedulers per page; large queues are split across pages). Requires scope: mcp:jobs:read.
list_scheduled_jobs
Pause a queue so workers stop picking up new jobs. Active jobs finish normally. Safe to call on an already paused queue (changed=false). Requires scope: mcp:queues:pause.
pause_queue
Health check for the MCP transport. Returns the text "pong". Requires only mcp:discover; use it to confirm authentication and connectivity before calling other tools. Requires scope: mcp:discover.
ping
Make a delayed BullMQ job eligible for processing now. Workers, queue pause state and processing limits still determine when it runs. Only jobs in the delayed state can be promoted; other states return conflict. Requires scope: mcp:jobs:promote.
promote_job
List the Redis connections the caller may access, with name, environment, BullMQ key prefix, and organization. Start here to open the interactive queue explorer in MCP Apps hosts, or get a text inventory in other clients. Data tools need a connectionId from this list. Follow nextCursor for all visible connections. Requires scope: mcp:jobs:read.
list_connections
Mark a firing alert event as manually resolved. Suppressed events cannot be resolved. Linked external issues (for example Linear) are closed asynchronously. Requires scope: mcp:failures:write.
resolve_alert_event
Resume a paused queue. Safe to call on an active queue (changed=false). Requires scope: mcp:queues:pause.
resume_queue
Re-enqueue a failed job with its existing payload. Only jobs in the failed state can be retried; other states return conflict. Never modifies job data. Requires scope: mcp:jobs:retry.
retry_job
Silence an alert rule for a number of minutes (1 to 10080). Open incidents stay frozen and re-evaluate when the snooze expires. Does not disable the rule. Requires scope: mcp:failures:write.
snooze_alert_rule
Remove the acknowledgement from a firing alert event so it shows as unhandled again. Requires scope: mcp:failures:write.
unacknowledge_alert_event
Clear a snooze so the alert rule evaluates on the next monitor poll. Requires scope: mcp:failures:write.
unsnooze_alert_rule

FAQs

Durabull: BullMQ & Redis Admin ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Durabull: BullMQ & Redis Admin's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Durabull: BullMQ & Redis Admin alternatives on ChatGPT?

As of 2026-10-29, Durabull: BullMQ & Redis Admin competes with API Status Check, Averth, Better Stack, Biggy, Birdie, Connhex, Datadog, elmah.io MCP and 23 more in ChatGPT Observability, Monitoring & Incident Response, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.