bunqueue v2.7.21

Fixes 4 bugs. MCP setup docs now make the install step explicit: every guide (README, MCP guide, quickstart, server, cron, use-cases) shows bun add bunqueue (or bun add -g bunqueue) before bunx bunqueue-mcp, and a caution box explains the…

To install bunqueue v2.7.21

bun add bunqueue@2.7.21

npm install bunqueue@2.7.21

To upgrade bunqueue

bun add bunqueue@latest

Bugfixes

bunqueue-mcp is a binary bundled inside the bunqueue package, not a standalone npm package. Running bunx bunqueue-mcp (or npx bunqueue-mcp) without bunqueue installed made the launcher try to download a package named bunqueue-mcp, which doesn’t exist → error: GET https://registry.npmjs.org/bunqueue-mcp - 404. The runtime is unchanged; this is a docs/invocation fix.

MCP setup docs now make the install step explicit: every guide (README, MCP guide, quickstart, server, cron, use-cases) shows bun add bunqueue (or bun add -g bunqueue) before bunx bunqueue-mcp, and a caution box explains the 404.
All JSON MCP configs switched to args: ["--package=bunqueue", "bunqueue-mcp"]: copy-paste safe: bunx resolves the bundled binary straight from the bunqueue package with no separate install. The skill configs use the same form; npx was replaced with bunx (the MCP entry’s shebang is #!/usr/bin/env bun).
Removed the misleading bunx bunqueue-mcp --help from troubleshooting, the MCP entry doesn’t parse CLI args (it starts the stdio server immediately).
Repo .mcp.json now runs the local source (bun run src/mcp/index.ts) instead of fetching from npm.

← bunqueue v2.7.20 · Full changelog · All posts