@imqueue — Claude Code MCP server: docs and scaffolding
Lets your coding agent read the @imqueue docs and generate typed services and clients. Useful when the code has to follow the framework instead of guessing at its API.
claude mcp add --transport http mcp https://mcp.imqueue.org/mcpWhat @imqueue does
A local install exposes 14 tools. Six of them are also on the hosted server: search_docs queries the guides, tutorial, CLI manual and API reference, get_doc pulls a full page, and list_packages plus package_status report versions, licences and the minimum Node release for @imqueue packages. Two scaffolders, scaffold_service and scaffold_client, build an IMQService subclass with @expose()d methods and show how to produce a fully typed client. None of these write anything.
The other eight tools drive the real imq binary, so they change the machine the server runs on. create_service is a dry run unless you pass apply: true. generate_client needs the service already running. Fleet control, CLI config reads and writes, and log dumps round out the set. No imq on your PATH? Use cli_install, or stay with the offline scaffolders.
Node.js ≥ 18 is required and there is no build step — the server runs from npm as is. Docs are fetched live from imqueue.org and imqueue.com, so package versions do not go stale with the server. The host allowlist lives in src/docs.ts and rejects anything else. If you want read-only access and no commands running locally, take the hosted server: seven tools, no side effects.
What it helps with
- find the current @imqueue doc page for a topic
- generate a service stub with typed methods
- get a typed client for a running service
- check a package's version, licence and minimum Node
- start, stop or inspect a fleet of service repos
Example prompts for the agent
- Search the @imqueue docs for how to declare an @expose() method
- Scaffold a service for a notifications queue
- Generate the client for NotificationService
How to install @imqueue
1Platform CLI: remote server
claude mcp add --transport http mcp https://mcp.imqueue.org/mcp2Platform CLI
claude mcp add at-imqueue -- npx -y @imqueue/mcp1Platform CLI: remote server
codex mcp add at-imqueue --url https://mcp.imqueue.org/mcp2Platform CLI
codex mcp add at-imqueue -- npx -y @imqueue/mcpConfig file
{
"mcpServers": {
"at-imqueue": {
"url": "https://mcp.imqueue.org/mcp"
}
}
}{
"mcpServers": {
"at-imqueue": {
"command": "npx",
"args": [
"-y",
"@imqueue/mcp"
]
}
}
}Config file
{
"servers": {
"at-imqueue": {
"type": "http",
"url": "https://mcp.imqueue.org/mcp"
}
}
}{
"servers": {
"at-imqueue": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@imqueue/mcp"
]
}
}
}1Platform CLI: remote server
gemini mcp add -t http at-imqueue https://mcp.imqueue.org/mcp2Platform CLI
gemini mcp add at-imqueue npx -y @imqueue/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about @imqueue
How do I install @imqueue in Claude Code?
For the local server: claude mcp add at-imqueue -- npx -y @imqueue/mcp. For docs only, use the hosted one: claude mcp add --transport http at-imqueue https://mcp.imqueue.org/mcp.
What does @imqueue do?
It hands your agent the @imqueue documentation, offline scaffolders for services and clients, and a bridge to the imq CLI. The agent reads current pages and writes code that matches the framework.
How is the local server different from the hosted one?
Local has all 14 tools, eight of which run imq commands on your machine. Hosted has seven read-only tools: docs, the package catalogue and the scaffolders.
