Log inSubmit server
Imqueue MCP logo

Imqueue MCP

by imqueue

Searches @imqueue documentation, scaffolds typed services and clients, and operates the local imq CLI.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Imqueue MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "imqueue-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@imqueue/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 14 tools correctly (1mo ago).

Overview

imqueue/mcp MCP server gives coding agents searchable @imqueue documentation, package metadata, typed service and client scaffolding, and access to the imq CLI. Its local npm installation provides read-only documentation tools plus CLI-backed operations for creating services, generating clients, managing service fleets, configuration, and logs. A hosted endpoint offers documentation and scaffolding without installation, but excludes tools that need access to the local machine. Reach for it when an agent needs current @imqueue API details or must generate and manage @imqueue projects.

Use cases

  • Search @imqueue API documentation before writing code
  • Scaffold a typed @imqueue service
  • Generate a client from a running service
  • Check and manage local @imqueue service repositories
  • Inspect package versions and installation commands

Key features

  • Searches official @imqueue documentation and API references
  • Generates typed service and client scaffolding
  • Reports package versions, licenses, and Node requirements
  • Runs the imq CLI for service and fleet management
  • Provides a read-only hosted MCP endpoint

Tools14

What Imqueue MCP lets your agent do. Expand a tool for its parameters.

Verified live~3.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

21/21 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @imqueue/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed14Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Imqueue MCP works

What imqueue/mcp MCP server does

The imqueue/mcp MCP server connects coding agents to the @imqueue ecosystem. It can search official guides, tutorials, CLI documentation, articles, and generated API references, then retrieve the relevant page as markdown. Search results include package names and URLs, making it possible to verify an API symbol or hand a result directly to the document reader.

It also exposes package catalog and release-status information. Agents can check current versions, supported Node versions, licenses, release dates, and package-specific installation commands before adding an @imqueue dependency. The catalog identifies mutually exclusive package choices, including the Prisma versus Sequelize database toolkits and the OpenTelemetry versus Datadog tracing packages.

How it works

The local server runs through Node and communicates with an MCP client over standard input and output. Documentation is fetched from approved imqueue.org and imqueue.com sources, including machine-readable indexes and page mirrors. URLs outside those hosts are rejected, and oversized pages report when their content was truncated.

Two offline tools return generated text without writing files: one produces an IMQService subclass, bootstrap code, and type declarations where needed; the other explains the exact command and usage pattern for generating a typed client. The generated client depends on a running service when the real CLI command is used.

CLI-backed operations invoke the installed imq executable on the machine hosting the local server. Calls use closed standard input and timeouts, so commands requiring unanswered interactive prompts fail rather than waiting indefinitely.

Setup and configuration

Install the imqueue/mcp MCP server with Node.js 18 or newer:

Terminal
npx -y @imqueue/mcp

Add that command to an MCP client configuration using a stdio server entry. The README provides configurations for Claude Desktop, Cursor, Windsurf, Codex, and other clients. The local installation can use all documented tools, but CLI-dependent actions require @imqueue/cli to be installed and available as imq. The cli_install tool can install that CLI globally.

A remote deployment is available at https://mcp.imqueue.org/mcp. It needs no local package installation and supplies seven read-only tools, including a guide for setting up the local server. It cannot operate on local files, processes, service repositories, or CLI configuration.

Tools and capabilities

The imqueue/mcp MCP server includes capabilities for:

  • Searching documentation and fetching complete or section-specific pages.
  • Listing documented packages and checking package status.
  • Generating service and client source as text without side effects.
  • Checking, installing, and querying the imq CLI.
  • Creating services, with dry-run behavior by default and optional file writes.
  • Generating a client from a running service.
  • Starting, stopping, restarting, or inspecting service repositories.
  • Reading or changing CLI configuration and dumping or cleaning fleet logs.

Limitations and notes

The hosted endpoint intentionally omits every CLI-backed tool. Local service creation can write files only when explicitly requested with apply=true; the default is a dry run. Client generation requires the target service to be running because the CLI introspects it over the message queue. The offline scaffolders do not create projects or execute commands.

Package versions and license details are obtained from imqueue.org feeds rather than hard-coded values.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Imqueue MCP

Run `npx -y @imqueue/mcp` with Node.js 18 or newer, then add the command as a stdio MCP server in your client configuration.

Yes. Add a stdio entry running `npx -y @imqueue/mcp` to the Claude Desktop MCP configuration.

Yes. `scaffold_client` explains the generation command without running it, while `generate_client` runs `imq client generate` and requires the target service to be running.

The local installation can create services, manage service repositories with `imq ctl`, read or change CLI configuration, and dump or clean logs. The hosted endpoint cannot access your machine.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewImqueue MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/imqueue-mcp?style=directory)](https://allmcps.com/mcp/imqueue-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/imqueue-mcp"><img src="https://allmcps.com/api/badge/imqueue-mcp?style=directory" alt="Imqueue MCP on AllMCPs" /></a>