Skip to content
@imqueue logo

@imqueue

Lets Node.js and TypeScript services call each other as local typed methods, routing calls over a Redis-backed message queue.

Actively maintained

Developer toolsFor developersOpen source
imqueue.org ↗GitHub
Open imqueue.orgAlternativesSet it up for my teamIs @imqueue yours? Claim the card →
At a glanceswept Oct 14, 2026

≈ 1visits/mo

Emerging · estimate, read Oct 14, 2026

For
Node.js and TypeScript teams whose services call each other often and want typed calls without HTTP or schema files
Activity
Actively maintainedrelease 3 days ago · site updated 8 days ago
Runs as
SDK
Used for
  • invoke methods on other services using generated typed clients
  • absorb request bursts between services without direct HTTP calls
  • schedule delayed service calls without running a separate job system
Worth knowingcomputed from what we read · each with its source
Your datawhat they publish, each line with its page · read Oct 15, 2026

“We do not sell data, we do not run advertising, and we do not use anything collected here to train machine-learning models.”

privacy policy ↗

These are @imqueue's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

How a program reaches itfound, not claimed · read Oct 15, 2026
  • MCP serverorg.imqueue/mcpverified in the MCP registry
  • Stateanswers, 7 toolschecked 2026-10-15
  • Address to connectmcp.imqueue.org/mcp
  • API docsimqueue.org/api/core/latest/core.imqoptions.safedeliverythe vendor's page ↗
  • MCP docsimqueue.org/mcpthe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare @imqueue with

Pick up to two.

All 10 alternatives to @imqueue →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use @imqueue for?

Sign in to leave a note
Questions this page answers
  • What is @imqueue?

    Lets Node.js and TypeScript services call each other as local typed methods, routing calls over a Redis-backed message queue. It is listed in the Atlas under Developer tools.

  • Who is @imqueue for?

    Node.js and TypeScript teams whose services call each other often and want typed calls without HTTP or schema files

  • Do people use @imqueue?

    Emerging: ≈ 1 visits/mo · estimate, 2026-10 · 1k installs/mo (npm).

  • Is @imqueue still maintained?

    Actively maintained: release 3 days ago · site updated 8 days ago.

  • Does @imqueue train AI on your data?

    No, per its privacy policy (2026-10-15): “We do not sell data, we do not run advertising, and we do not use anything collected here to train machine-learning models.”

  • Is @imqueue safe?

    We do not audit vendors. What @imqueue publishes, read 2026-10-15: on training with your data, “We do not sell data, we do not run advertising, and we do not use anything collected here to train machine-learning models.”.

  • What are alternatives to @imqueue?

    In Developer tools, by use: Scrollport, Microsoft, GitHub, OpenAI, Cloudflare, Super Coloring.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.