Imqueue MCP vs Watchtower
A side-by-side look at the Imqueue MCP and Watchtower MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WatchtowerDeveloper ToolsJob alerts for AI agents: describe a role once, get only new postings from 1,500+ tech job boards.53GoodAuth: no auth requiredVerdict: choose Imqueue MCP for developer tools work as a local process; choose Watchtower for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Imqueue MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_doc, list_packages.
WChoose Watchtower when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
DATABASE_URL. - You want tools like
watch_jobs, search_jobs, list_companies.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Watchtower | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 64/100 · Good | 53/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | DATABASE_URL |
| Verified owner |
Tools & capabilities
Imqueue MCP tools 14
search_docsSearch the official @imqueue docs (guides, tutorial, CLI manual, articles) and every exported symbol of every @imqueue package that publishes a generated API reference, returning the most relevant pages with their URLs. Each result names the package it belongs to. Takes a plain question or an exact symbol name such as 'RedisQueue.send', 'PgPubSub.listen' or 'watcherCheckDelay'. Answers 'how do I do X in @imqueue' and confirms a signature before code is written against it. Every result carries the page URL, which get_doc reads in full. Some capabilities are covered by two mutually exclusive packages — @imqueue/pg-prisma vs @imqueue/pg-sequelize, @imqueue/opentelemetry vs @imqueue/datadog — so for a query like 'tracing' or 'database', call list_packages for the choosing rule rather than taking whichever package ranks first, and pass `package` here to search within the one you settled on.get_docFetch the markdown of an @imqueue documentation page by its URL (as returned by search_docs). Returns plain markdown suitable for reading and quoting. Pass a URL with a #fragment — which is what search_docs returns for a section result — to get just that section plus the heading path above it; pass the URL without one to read the whole page. Only imqueue.org (framework docs) and imqueue.com (licensing, pricing, support) URLs are fetched; anything else is refused. Very large pages are truncated, which the result reports.list_packagesThe complete, authoritative catalogue of documented @imqueue packages, each with its current version, licence, minimum Node version, a one-line summary and its exact install command. Call this BEFORE adding any @imqueue dependency: search_docs can only find a package you already suspect exists, and this is the list. Covers typed RPC over a message queue, the Redis queue engine, the `imq` CLI, jobs and scheduling, Prisma and Sequelize database toolkits, method caching, tag-invalidated caching, PostgreSQL LISTEN/NOTIFY, Zod validation, OpenTelemetry or Datadog tracing, async logging, GraphQL N+1 batching across services, CIDR/IP checks and HTTP rate limiting. Some pairs are mutually exclusive — pg-prisma vs pg-sequelize, opentelemetry vs datadog — and installing both of a pair breaks silently, so read the `pick` rule on those entries before choosing. For one package's release history, links and the framework-wide Node and Redis requirements, use package_status.package_statusThe current version, licence, minimum Node version and last release date of any published @imqueue package — or of all of them. Use it when the user asks which version of an @imqueue package is current, what licence it is under, or which Node or Redis version it needs. Covers every published package, including @imqueue/cli and @imqueue/mcp, and also returns the framework-wide licence, Node and Redis requirements, with a `licenseNote` that states the licence terms in a sentence. The facts are read from the npm registry by imqueue.org, and the result says when. Pass `package` for one entry, with or without the @imqueue/ scope; omit it for all of them.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Imqueue MCP
{
"mcpServers": {
"imqueue-mcp": {
"command": "npx",
"args": [
"-y",
"@imqueue/mcp"
]
}
}
}
Watchtower
No confirmed install command for Watchtower yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Imqueue MCP is categorized under Developer Tools and uses a local stdio subprocess. Watchtower belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Imqueue MCP for developer tools work and Watchtower for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Watchtower has no confirmed install command yet — follow its own setup instructions.
Imqueue MCP is listed as free. Auth: no auth required. Watchtower is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add imqueue-mcp and watchtower as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Imqueue MCP has a quality signal of 64/100 (Good) with 4 views, 0 installs and 1 GitHub stars. Watchtower has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.