queue-inspector-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDIS_URL | No | Redis connection string. Default: redis://localhost:6379 | redis://localhost:6379 |
| BULL_PREFIX | No | Key prefix BullMQ was configured with. Default: bull | bull |
| ASYNQ_PREFIX | No | Key prefix Asynq was configured with. Default: asynq | asynq |
| QUEUE_INSPECTOR_BACKENDS | No | Restrict which backends are scanned. Default: asynq,bullmq | asynq,bullmq |
| QUEUE_INSPECTOR_READ_ONLY | No | Set to '1' to omit mutating tools. Default: unset |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_queuesA | List every queue the inspector can see, tagged with its backend (asynq or bullmq). |
| queue_statsA | Report the number of jobs in each state for a queue, using the backend's own state names. |
| list_jobsA | List jobs in a given state (paged). Returns id, type, attempts and a truncated last error. Valid states depend on the backend: asynq uses pending/active/scheduled/retry/archived/completed; bullmq uses waiting/active/delayed/prioritized/waiting-children/paused/completed/failed. |
| get_jobA | Fetch full detail for one job: payload, attempts, retry ceiling, last error and timestamps. Binary payloads are returned base64-encoded and flagged. |
| retry_jobA | Move a failed or dead job back to the pending/wait queue so it runs again. Faithfully replicates the backend's own retry (asynq Inspector.RunTask, bullmq Job.retry). |
| delete_jobA | Permanently delete a job from a queue. Active jobs cannot be deleted. Faithfully replicates the backend's own delete (asynq Inspector.DeleteTask, bullmq Job.remove). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yusufihsangorgel/queue-inspector-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server