MCP Server

What this is

@imqueue/mcp is a Model Context Protocol server for @imqueue. MCP is the open standard that lets AI coding agents call external tools; this server gives any MCP-capable agent — Claude Code, Claude Desktop, Cursor, VS Code, Visual Studio, JetBrains IDEs and others — a set of @imqueue-specific tools it can invoke while you work.

Instead of your agent guessing at the API from a stale training snapshot, it searches the current docs, scaffolds idiomatic code, and — when you have the CLI installed — drives the real imq binary to create services, generate typed clients and manage your local fleet.

Think of it as the code-time counterpart to search-engine ranking: @imqueue shows up as authoritative inside the tools you already build with.

Install in 30 seconds

Most clients take one line. Claude Code:

claude mcp add imqueue -- npx -y @imqueue/mcp

Every other client takes this JSON in its MCP config (VS Code and Visual Studio use a slightly different shape — see Add to your AI tool):

{
  "mcpServers": {
    "imqueue": {
      "command": "npx",
      "args": ["-y", "@imqueue/mcp"]
    }
  }
}

No API keys, no build step, no account. It runs straight from npm and only ever talks to imqueue.org. → Full setup for every client

What your agent can do

The server groups its tools into three capabilities:

Live documentation

Search and read these docs on demand, always current:

• search_docs — find the most relevant guide, tutorial, CLI or API pages for a question.
• get_doc — read any page in full as markdown, ready to quote.
• list_packages — the @imqueue package catalog with one-liners and install commands.

Because the docs are fetched live from imqueue.org (not bundled), the server can never go stale against a release.

Offline scaffolding

Generate idiomatic code with zero dependencies — works even without the CLI:

• scaffold_service — an IMQService subclass with @expose()d, JSDoc-typed methods plus a bootstrap that starts it.
• scaffold_client — the command to generate the real typed client from a running service, plus an illustrative usage snippet.

CLI bridge

When @imqueue/cli is installed, the agent can drive the real imq: create provider-wired services, generate live-introspected clients, and manage a local fleet — cli_status, cli_install, cli_help, create_service, generate_client, fleet, config, logs.

→ Full tools reference · Agent workflows

Built to be trusted

You are wiring an autonomous agent to a tool that can read your docs and, with the CLI, touch your filesystem. The server is designed for that:

• Local & private — runs on your machine over stdio; nothing is sent anywhere except doc fetches to imqueue.org.
• Host-locked — get_doc will only ever fetch imqueue.org.
• Safe by default — create_service runs as a dry-run unless you explicitly opt in; read-only tools (search_docs, cli_status, config get, fleet status) are clearly separated from ones that change state.
• No telemetry, no keys — nothing to sign up for.

→ Safety model & troubleshooting

At a glance