MCP server

@getworkbench/mcp — let Cursor, Claude Desktop, Zed, and Continue inspect and operate BullMQ queues via your running dashboard.

The MCP server is a thin local proxy. It speaks JSON-RPC over stdio to your editor and HTTP to a running Workbench dashboard. The dashboard's auth and readonly flag are the source of truth.

Code

Cursor / Claude Desktop ──┐
Zed / Continue.dev ───────┼──▶ workbench-mcp (stdio) ──▶  https://your.app/jobs  ──▶  Redis
any MCP client      ──────┘

Install

Shell

npx @getworkbench/mcp

Verify it starts:

Shell

WORKBENCH_URL=http://localhost:3000/jobs \
WORKBENCH_USERNAME=admin \
WORKBENCH_PASSWORD=hunter2 \
npx @getworkbench/mcp

Environment variables

Variable	Required	Description
`WORKBENCH_URL`	Yes	Dashboard URL, e.g. `http://localhost:3000/jobs`
`WORKBENCH_USERNAME`	No	Basic auth username
`WORKBENCH_PASSWORD`	No	Basic auth password
`WORKBENCH_TOKEN`	No	Bearer token (overrides basic auth)

Don't append /api to WORKBENCH_URL — the MCP adds /api/... automatically.

Cursor

Add to ~/.cursor/mcp.json or your project's .cursor/mcp.json:

JSON

{
  "mcpServers": {
    "workbench": {
      "command": "npx",
      "args": ["-y", "@getworkbench/mcp"],
      "env": {
        "WORKBENCH_URL": "http://localhost:3000/jobs",
        "WORKBENCH_USERNAME": "admin",
        "WORKBENCH_PASSWORD": "hunter2"
      }
    }
  }
}

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

JSON

{
  "mcpServers": {
    "workbench": {
      "command": "npx",
      "args": ["-y", "@getworkbench/mcp"],
      "env": {
        "WORKBENCH_URL": "http://localhost:3000/jobs"
      }
    }
  }
}