QuotaQueue CLI and MCP server

Use the QuotaQueue REST API from a terminal or any agent that supports the Model Context Protocol (MCP). Both executables are zero-dependency Node.js programs and use the same API keys as the REST API.

Authentication

Create a read-only Claude or OpenAI key in QuotaQueue → Integrations, or a general key in Settings → API keys, then provide it through the environment:

export QUOTAQUEUE_API_KEY=qq_live_your_key_here

The key never needs to be placed in an agent prompt. Its read, write, or admin permissions are enforced by the API.

Install

Install the supported zero-dependency commands from npm (Node.js 20 or newer is required):

npm install -g quotaqueue

Run quotaqueue --version after installation. The package provides both quotaqueue and the optional quotaqueue-mcp executable.

For a checkout of https://github.com/ryanfsgtm/quotaqueue-agent-tools, install without a network download:

QUOTAQUEUE_SOURCE_DIR="$PWD" sh install.sh

CLI

quotaqueue get /organization
quotaqueue get /deals --query limit=25
quotaqueue post /calculate --data '{"payPeriodId":"..."}'
quotaqueue endpoints --tag Statements

Agent-friendly discovery and diagnostics are built in:

quotaqueue auth status
quotaqueue doctor
quotaqueue whoami
quotaqueue capabilities
quotaqueue robot-docs guide

All operational commands emit JSON on stdout and diagnostics on stderr. quotaqueue capabilities documents the stable command and exit-code contract.

Use --data @request.json to read a request body from a file. Requests default to the production API at https://quotaqueue.com/api/v1; its OpenAPI document is available at https://quotaqueue.com/api/v1/openapi.json. Set QUOTAQUEUE_BASE_URL only when targeting a non-production deployment.

When an agent creates plan rules through the REST API, it should send the full config whenever the user specified terms and then read the created rule back. Rule-config percentages use decimals (0.10 means 10%), while money uses the organization's minor currency unit. Omitting config deliberately selects that rule type's platform defaults.

For example, create and verify a 10% flat-rate rule:

quotaqueue post /plans/PLAN_ID/rules --data '{"type":"flat_rate","name":"10% Commission","config":{"rateType":"percentage","rate":0.10,"appliesTo":"deal_amount"}}'
quotaqueue get /plans/PLAN_ID/rules

MCP

The MCP server communicates over stdio and exposes two tools:

• quotaqueue_list_endpoints discovers API methods, paths, and required permission levels.
• quotaqueue_request performs an authenticated API request.

Example MCP client configuration after running the installer:

{
  "mcpServers": {
    "quotaqueue": {
      "command": "/home/you/.local/bin/quotaqueue-mcp",
      "env": {
        "QUOTAQUEUE_API_KEY": "qq_live_your_key_here"
      }
    }
  }
}

Treat API keys as secrets. Prefer your MCP client's environment/secret configuration rather than committing a key to a shared config file.

Claude Code and Codex plugin

The shared skills keep API access in the local CLI and default to read-only operations. Install the CLI first, then add the public marketplace.

Claude Code:

claude plugin marketplace add ryanfsgtm/quotaqueue-agent-tools
claude plugin install quotaqueue@quotaqueue

Codex and the ChatGPT desktop app:

codex plugin marketplace add ryanfsgtm/quotaqueue-agent-tools

Restart the ChatGPT desktop app and install QuotaQueue from the Plugins Directory.

Releases

The source remains proprietary (UNLICENSED). Maintainers publish a new CLI release by updating package.json, committing the change, and pushing the matching vX.Y.Z tag. The release workflow uses npm trusted publishing and contains no long-lived npm token.