Kaseya Quote Manager MCP Server

Kaseya Quote Manager MCP Server

A Model Context Protocol (MCP) server that gives AI assistants read-only access to Kaseya Quote Manager (Datto Commerce) — quotes, sales orders, purchasing, the product catalog, and customers.

Maintained by Wyre Technology.

Quick Start

Claude Desktop — download, open, done:

1. Download kaseya-quote-manager-mcp.mcpb from the latest release
2. Open the file (double-click or drag into Claude Desktop)
3. Enter your Kaseya Quote Manager API Key when prompted

Claude Code (CLI):

claude mcp add kaseya-quote-manager-mcp \
  -e KASEYA_QUOTE_MANAGER_API_KEY=your-api-key \
  -- npx -y github:WYRE-AI/kaseya-quote-manager-mcp

Authentication

Quote Manager authenticates with a single API key sent in the apiKey header. Generate one in Quote Manager under Settings → API.

Stdio and AUTH_MODE=env read KASEYA_QUOTE_MANAGER_API_KEY. The HTTP transport does not start unless CONDUIT_S2S_SECRET is a real value. Known placeholders (changeme, change-me, secret, example, placeholder, replace-me, your-secret, your-s2s-secret, s2s-secret, replace-with-a-real-secret) are rejected, including when MCP_ALLOW_INSECURE_DEV=1 is set. The process never logs the secret.

HTTP authentication

With MCP_TRANSPORT=http and a configured secret, every /mcp request must include X-Gateway-S2S:

X-Gateway-S2S: t=<unix seconds>,v1=<64 lowercase hex chars>

v1 is HMAC-SHA256 of the exact ASCII string t=<unix seconds> (the same prefix that appears in the header), keyed with CONDUIT_S2S_SECRET, encoded as 64 lowercase hex characters. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401.

In AUTH_MODE=gateway (the container image and Compose default), /mcp also requires X-Kaseya-Quote-Manager-Api-Key. That header is the only credential for the request. A request without it returns 401 and does not fall back to KASEYA_QUOTE_MANAGER_API_KEY.

/health stays unauthenticated, does not require X-Gateway-S2S, and does not return the API key. The stdio transport does not use CONDUIT_S2S_SECRET.

Configuration

Copy .env.example.

Features

• Read-only by design — the Quote Manager API exposes only list/get; no tool can mutate your data.
• 39 entity tools across 5 domains, plus kqm_navigate / kqm_status discovery tools.
• Decision-tree navigation — call kqm_navigate to explore a domain's tools.
• Rate limiting — respects the API's 60 req/min limit, with retry on 429/5xx.
• Dual transport — stdio (local) and HTTP Streamable (gateway/Docker).
• MCPB packaging for one-click Claude Desktop install.

Domains & tools

Tools are named kqm_<entity>_list and kqm_<entity>_get.

list tools accept page, pageSize (max 100), and modifiedAfter where supported, plus entity-specific filters (e.g. quoteNumber, customerID, purchaseOrderID).

Usage example

kqm_navigate { "domain": "sales" }
kqm_quote_list { "page": 1, "pageSize": 50 }
kqm_quote_get { "id": 12345 }
kqm_quote_section_list { "quoteID": 12345 }

Docker

The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode the API key arrives on each request as X-Kaseya-Quote-Manager-Api-Key. It is not read from the environment.

Generate the secret once, export it, and reuse it for the server and for signing requests. -e CONDUIT_S2S_SECRET (name only) passes the exported value without putting it in the docker command line.

export CONDUIT_S2S_SECRET="$(openssl rand -hex 32)"
docker build -t kaseya-quote-manager-mcp .
docker run --rm \
  -e CONDUIT_S2S_SECRET \
  -p 127.0.0.1:8080:8080 \
  kaseya-quote-manager-mcp
# Health: curl localhost:8080/health

Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, does not pass KASEYA_QUOTE_MANAGER_API_KEY, and publishes 127.0.0.1:8080:8080. A project .env is interpolation only — the gateway service has no env_file.

# Reuses the CONDUIT_S2S_SECRET exported above.
docker compose up

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses KASEYA_QUOTE_MANAGER_API_KEY:

docker run --rm \
  -e CONDUIT_S2S_SECRET \
  -e AUTH_MODE=env \
  -e KASEYA_QUOTE_MANAGER_API_KEY=your-api-key \
  -e MCP_HTTP_HOST=0.0.0.0 \
  -p 127.0.0.1:8080:8080 \
  kaseya-quote-manager-mcp

Local HTTP without a secret is development-only. It always binds 127.0.0.1 and logs a warning. A non-loopback MCP_HTTP_HOST is overridden:

MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm run start:http

Sign a gateway request with X-Gateway-S2S and the API key header. Build the header first: v1 is HMAC-SHA256 of the exact ASCII string t=<unix seconds> (no trailing newline), keyed with CONDUIT_S2S_SECRET, as 64 lowercase hex characters. Use the same exported CONDUIT_S2S_SECRET the server was started with.

openssl dgst -hmac takes the key as a process argument, so other local users can see it in the process list while it runs. Only run this example on a trusted single-user machine; elsewhere, sign requests from code that reads the secret from the environment.

: "${CONDUIT_S2S_SECRET:?Set CONDUIT_S2S_SECRET to the server secret}"
: "${KASEYA_QUOTE_MANAGER_API_KEY:?Set KASEYA_QUOTE_MANAGER_API_KEY to the Quote Manager API key}"
timestamp="$(date +%s)"
digest="$(
  printf 't=%s' "$timestamp" |
    openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" |
    awk '{print $NF}' |
    tr '[:upper:]' '[:lower:]'
)"
X_GATEWAY_S2S="t=${timestamp},v1=${digest}"

curl -sS http://127.0.0.1:8080/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -H "x-gateway-s2s: ${X_GATEWAY_S2S}" \
  -H "x-kaseya-quote-manager-api-key: ${KASEYA_QUOTE_MANAGER_API_KEY}" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"kqm_status","arguments":{}}}'

Development

npm install
npm run build
npm test
npm run lint

License

Apache-2.0 © WYRE Technology