@imqueue MCP server
online · 100% uptimeorg.imqueue/mcp·v3.7.9·1 starsSearch @imqueue docs and scaffold typed services & clients from your AI coding agent.
1 stars148 downloads/wk
Reviews
Write oneNobody has reviewed @imqueue yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
@imqueue tools (7)
write = sends, deletes, buys or postsget_docFreeFetch 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_packagesFreeThe 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.
local_install_guideFreeReturn the setup instructions for running the full @imqueue MCP server on your own machine. The local server adds the CLI-backed tools, which act on your project files and running services and so cannot be offered by a hosted server. Returns instructions only — it installs nothing.
package_statusFreeThe 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.
scaffold_clientFreeREAD-ONLY: returns text and writes nothing to disk, and does NOT run the command it shows you. Explains how to generate and use the fully-typed client for an @imqueue service: @imqueue generates the real client from a running service via `imq client generate`, so this returns that exact command plus an illustrative usage snippet. The generated file exports a single namespace holding the client class, so the import shape is not the obvious one — take it from `namespace` rather than guessing. Use generate_client (local install only) if you want the command actually run.
scaffold_serviceFreeREAD-ONLY: returns generated source code as text and writes nothing to disk, creates no project and runs no command. Generates an idiomatic @imqueue/rpc service (an IMQService subclass with @expose()d, JSDoc-typed methods) plus a bootstrap that starts it. Provide the methods you want, or omit them for a starter template. Any non-primitive parameter or return type also gets a types.ts with the required @classType()/@property() declarations — without those the generated client types it `any`, which compiles. Use create_service (local install only) if you want files actually written.
search_docsFreeSearch 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.
Public scan report
scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it
- Code scan18 source files scanned25/25
- Live reliabilityremote reachable in 883ms20/20
- Tool poisoning7 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10
How @imqueue compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 95/100
- higher than 96% of 1,301 Productivity servers
- Tools
- 7
- the typical Productivity server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Productivity server answers 100%
- Response time
- 290 ms
- faster than 55% of 656 Productivity servers
- GitHub stars
- 1
- more than 50% of 855 Productivity servers
- Downloads a week
- 148
- more than 65% of 433 Productivity servers with a package
What its tools let an agent do: 7 read
Release history: 2 versions in the registry since 2026-08-30, latest 2026-09-18, typically one every 20 days.
Install @imqueue in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp https://mcp.imqueue.org/mcp
What the publisher says
From the @imqueue repository's README, as published. We do not edit it. Read it on GitHub
@imqueue/mcp
A Model Context Protocol server for @imqueue. It lets AI coding agents (Claude Code, ChatGPT, Codex, Cursor, VS Code, JetBrains, …) search the @imqueue documentation, scaffold typed services & clients, and drive the imq CLI — so they generate correct, idiomatic @imqueue code instead of guessing.
📖 Full documentation: imqueue.org/mcp — per-client setup, complete tools reference, agent workflows and the safety model.
Tools
Two surfaces, and they are not the same. The local server (npx -y @imqueue/mcp) has all 14 tools. The hosted server (mcp.imqueue.org/mcp) has seven, all read-only — see below for why.
Hosted + local
All six are read-only: they fetch or generate text and write nothing.
All five also declare an MCP outputSchema and return structuredContent alongside the human-readable markdown, so a client can consume results as data — take results[0].url from searchdocs and hand it to getdoc, or write scaffoldservice's files[] straight to disk — instead of parsing prose and code fences. For the scaffolders and the catalogue the markdown is rendered from* that same structure, so the two can't drift.
getdoc's schema is metadata only, on purpose — and that turns out to be the more interesting design than having no schema at all. A schema obliges the server to send structuredContent, but nothing says structuredContent must repeat what is in content: it describes the structured part* of the answer. So the page travels once, in content, and the schema carries url (the mirror actually fetched, which is not always the URL you passed), mimeType, bytes (so a caller can decide before reading) and truncated. Putting markdown in there as well would have doubled the largest response the server can produce — measured on /api/rpc/latest/, 16.6 kB of text plus 16.6 kB of structure for one read. The absence of a body field is itself self-describing: a caller reading the schema sees no content field and knows the page is in content, which is where every client already looks.
The CLI-backed tools have no schema: they return imq stdout, which has no shape worth promising.
CLI-backed tools — local only (require @imqueue/cli on PATH)
These drive the real CLI, so they act on the machine the server runs on. They exist in the local install only; the hosted server does not register them.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
@imqueue: common questions
- Is @imqueue MCP server safe?
- Yes, by our scan: it is graded A (95/100). Read the @imqueue safety report
- How do I install @imqueue?
- It runs remotely at mcp.imqueue.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does @imqueue need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is @imqueue maintained?
- The last commit was 35 days ago (2026-10-01). The latest release is v3.7.9.
- Is @imqueue up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of @imqueue?
- Servers from other publishers that do the same job: WTFM MCP server, Livewire Flux MCP server and Context7 MCP server.
- How does @imqueue compare with other Productivity MCP servers?
- safety score 95/100 (higher than 96% of 1,301 Productivity servers); tools 7 (the typical Productivity server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to @imqueue
Same job from other publishers: the closest match first, then the best rated.
- WTFMYour coding agent writes the user docs from your codebase, screenshots included.not reviewedGrowingA
- Livewire FluxFlux UI component and layout docs for AI coding agents. Live from fluxui.dev, Pro-tier aware.not reviewedGrowingA
Context7Up-to-date docs for AI agentsnot reviewedWidely usedA- ArgentDrive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agentnot reviewedWidely usedA
- Svelte MCPThe official Svelte MCP server providing docs and autofixing tools for Svelte developmentnot reviewedWidely usedA