Developer Tools

imqueue.org

Provides documentation search, package listing, and scaffolding for @imqueue RPC services and clients.

1 endpoint7 known toolsFirst detected August 3, 2026Last detected September 6, 2026

ENDPOINT 1

https://mcp.imqueue.org/mcp

No auth detected

MCP server metadata

Name: imqueue
Version: 3.7.8

Capabilities

tools.listChanged

Server instructions

Do not recall @imqueue from memory — it is decorator-driven, and the mistakes below compile cleanly. 1. Call search_docs before writing or changing @imqueue code, and get_doc to read a page in full. Never infer an API name or signature; the docs win over recall. 2. Call list_packages before adding an @imqueue dependency: some pairs are mutually exclusive (pg-prisma/pg-sequelize, opentelemetry/datadog) and installing both breaks silently. 3. Every remotely callable method needs @expose() and a complete typed JSDoc block: JSDoc is the only runtime type source, so an undocumented parameter is published as `any`. 4. A class crossing the RPC boundary needs @classType() on the class and @property() on every field, or the generated client types it `any`. 5. Clients are generated from a running service with `imq client generate` — never hand-written. 6. Cite the page URL for any fact from these tools.

Known tools 7

search_docs

Search 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.

Inferred read-only

get_doc

Fetch the markdown of an @imqueue documentation page by its URL (as returned by search_docs).

Inferred read-only

list_packages

The 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.

Potential side effects

package_status

The current version, licence, minimum Node version and last release date of any published @imqueue package — or of all of them.

Inferred read-only

scaffold_service

READ-ONLY: returns generated source code as text and writes nothing to disk, creates no project and runs no command.

Potential side effects

scaffold_client

READ-ONLY: returns text and writes nothing to disk, and does NOT run the command it shows you.

Potential side effects

local_install_guide

Return the setup instructions for running the full @imqueue MCP server on your own machine.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.imqueue]
url = "https://mcp.imqueue.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "imqueue": {
      "type": "http",
      "url": "https://mcp.imqueue.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: imqueue
Remote MCP URL: https://mcp.imqueue.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "imqueue": {
      "url": "https://mcp.imqueue.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "imqueue": {
      "type": "http",
      "url": "https://mcp.imqueue.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "imqueue",
  "transport": "streamable-http",
  "url": "https://mcp.imqueue.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for imqueue.org was fetched 2026-08-24T03:39:47.939Z.

Trust status Neutral

imqueue.org is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.