Skip to main content
Glama
MSPbotsAIFramework

Kaseya Quote Manager MCP Server

Kaseya Quote Manager MCP Server

An MCP server for the Kaseya Quote Manager API (v1), the quoting and procurement tool MSPs use to quote, sell and order hardware, software and services. It lets an AI agent read quotes with their sections and lines, sales orders with lines and payments, purchase orders with lines and costs, suppliers, the product catalog, and customers with their contacts and addresses. The API is read-only, so every tool is too.

  • Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

  • Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first tools/list

  • Also provides three MCP prompts: quote-pipeline-review, quote-detail (quote_number), purchasing-summary

  • Python 3.12, uv, FastMCP, httpx

  • License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →


MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

MSPbots Connector

Visible

Every tool call is logged: who, which vendor, when. Usage dashboard, CSV export, SIEM streaming.

Controlled

Role-based, per-tool allowlist. Deny by default.

Protected

Credentials encrypted per record. AI clients never see your vendor passwords or tokens.

MSP-native

Built for the MSP stack only: RMM, PSA, documentation, security, finance.

Quick start

  1. Sign up at connect.mspbots.ai.

  2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

  3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

  4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

  5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

  • One MCP URL for all your AI clients

  • 150+ connectors across the MSP stack

  • Custom MCP servers supported, free

  • Authorization happens on each vendor's own page; the AI never sees passwords or tokens

  • Bring your own credentials: use the vendor API keys you already have

  • Multiple accounts per app; connect once, reuse across AI clients

  • Tool search: finds the right action for the task

  • One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

  • Audit log for every tool call (who, which vendor, when)

  • Usage dashboard: call volume, top vendors, error rate, per-user activity

  • Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

  • Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

  • Per-role, per-tool allowlist, deny by default

  • owner / admin / member roles

  • SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

  • Credentials encrypted one record at a time (AES-256-GCM, per-record key)

  • AI clients authenticate with OAuth 2.1 + PKCE

  • Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

  • Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai


Related MCP server: CyberQP MCP Server

Authentication headers

Header

Required

Type

Default

Allowed values

Description

Example

X-Kaseya-Quote-Manager-Api-Key

Yes

string

none

-

Kaseya Quote Manager API key

your-api-key

Where to get it: in Kaseya Quote Manager open My account (profile icon) > Developer API.

How the key is sent: every call goes to https://api.kaseyaquotemanager.com/v1/... with the key in the apiKey request header (never in the URL, so it stays out of access logs).

A request to /mcp without the header gets HTTP 401.

Tools

All tools return a JSON string. Lists take page (from 1) and pageSize (max 100) and return {count, page, has_more, next_page, offset, next_offset}; most also take modifiedAfter (ISO date-time) to return only records changed since then. Lists also take offset (0-based record position, overrides page): pass next_offset from the previous result to continue, because when a page is cut to fit the response size limit, next_offset starts right after the last record returned, while the rest of that page is on no other page number. Every _get tool takes id.

Area

Tools

Overview

kqm_navigate (domain: sales, procurement, catalog, crm, org), kqm_status

Sales

kqm_quote_list (quoteNumber), kqm_quote_get, kqm_quote_section_list (quoteID), kqm_quote_section_get, kqm_quote_line_list (quoteSectionID), kqm_quote_line_get, kqm_sales_order_list (orderNumber), kqm_sales_order_get, kqm_sales_order_line_list (salesOrderID), kqm_sales_order_line_get, kqm_sales_order_payment_list (salesOrderID), kqm_sales_order_payment_get

Procurement

kqm_purchase_order_list (orderNumber), kqm_purchase_order_get, kqm_purchase_order_line_list (purchaseOrderID), kqm_purchase_order_line_get, kqm_purchase_order_cost_list (purchaseOrderID), kqm_purchase_order_cost_get, kqm_supplier_list, kqm_supplier_get, kqm_product_supplier_list (productID), kqm_product_supplier_get

Catalog

kqm_product_list (manufacturerPartNumber), kqm_product_get, kqm_product_image_list (productID), kqm_category_list, kqm_category_get, kqm_brand_list, kqm_brand_get

CRM

kqm_customer_list, kqm_customer_get, kqm_customer_address_list (customerID), kqm_customer_address_get, kqm_contact_list (customerID), kqm_contact_get

Organisation

kqm_employee_list, kqm_employee_get, kqm_warehouse_list, kqm_warehouse_get

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "Kaseya Quote Manager returned HTTP 401 for quote", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. Requests are retried with backoff on 429, 5xx and network errors. Kaseya Quote Manager allows 60 calls per minute and 20,000 per day.

Run locally

uv sync
uv run python -m kaseya_quote_manager_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t kaseya-quote-manager-mcp:dev .
docker run --rm -p 8080:8080 kaseya-quote-manager-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Kaseya-Quote-Manager-Api-Key: your-api-key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# quotes changed this month
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Kaseya-Quote-Manager-Api-Key: your-api-key" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"kqm_quote_list","arguments":{"modifiedAfter":"2026-10-01T00:00:00Z"}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

  • Tool count (41) and prompts (3). Kept as is because the names are an existing contract; the parameters of every tool match the earlier version and the official API, plus offset on the list tools (handled here, see paging above).

  • API source. The official OpenAPI document is published at https://api.kaseyaquotemanager.com/docs/v1/swagger.json (API Reference v1, 39 read-only endpoints); the getting-started guide is in the Kaseya Quote Manager help center.

  • Paging. The API returns plain arrays with no total; has_more is true when a page comes back full, and pageSize is capped at the API's maximum of 100.

  • All tools are read-only and annotated as such, matching the API.

License

Apache License 2.0 - see LICENSE and NOTICE.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Read-only MCP server providing AI assistants with access to Kaseya Quote Manager entities including quotes, sales orders, procurement, catalog, and CRM data via 39 tools.
    1
    Apache 2.0
  • A
    license
    A
    quality
    B
    maintenance
    Provides read-only visibility into CyberQP privileged access management data, including customer and account metadata, tenant event logs, and Just-In-Time account status and policies, for AI assistants.
    10
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to read-only query an MSP's Action1 data — organizations, managed endpoints, missing OS and third-party updates, and scheduled automations — using per-request credentials that are never stored. Supports multi-tenant, stateless access over Streamable HTTP with paginated list results and structured error responses.
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to read Datto SIRIS and ALTO backup appliance data, including protected machines and shares, snapshot history with local and screenshot verification, offsite replication status, fleet alerts, and partner portal activity logs. Provides read-only access to the Datto partner REST API with stateless, per-request authentication.
    Apache 2.0