ConnectWise Manage MCP Server

A Model Context Protocol server that lets AI agents on the MSPbots Agent Platform work in ConnectWise Manage (ConnectWise PSA): service tickets and notes, companies, contacts, projects, time and schedule entries, members, configurations, activities, the product catalog, inventory, agreements, invoices, opportunities, purchase and sales orders.

It runs as a stateless HTTP service behind the MSPbots MCP gateway. The gateway sends each tenant's ConnectWise credentials as request headers on every call; the server keeps nothing between requests.

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

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: ConnectWise Manage MCP Server

Credentials (request headers)

Requests are authenticated with HTTP Basic <companyId>+<publicKey>:<privateKey> plus the clientId header, as the ConnectWise developer documentation describes. What the agent can see and change is limited by the API member's security role.

Header names are case-insensitive. A request to /mcp with any of these headers missing or blank gets 401 with the list of expected headers. The server does not check header formats before a tool runs (the platform probes initialize and tools/list with placeholder values); an unusable site URL is reported by the tool as invalid_argument.

Tools

94 tools. Tool names and parameters match the previous ConnectWise Manage connector on the MSPbots Agent Platform, so existing agents keep working. That compatibility is why this is one server with more than 20 tools instead of several smaller ones.

Behaviour notes:

• Every tool returns a JSON string. Errors use one envelope: {"error": {"code": "...", "message": "...", "retryable": false}} with code one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error.

• List tools return {"items", "count", "page", "page_size", "has_more"}. pageSize defaults to 25 (50 for cw_list_sites and cw_list_contact_types) and is capped at 200. Results larger than 20,000 characters are cut and flagged with truncated / has_more. The *_href links ConnectWise adds to every object are removed.

• conditions use ConnectWise syntax: strings in double quotes, dates in square brackets (dateStart >= [2026-01-01T00:00:00Z]). Single-quoted literals are converted to double quotes.

• Updates are JSON Patch arrays (op, path, value); add and replace need a value.

• ConnectWise silently drops unknown fields in request bodies, so the tools send exact API field names.

• Contacts: types are set at creation as types: [{"id": n}] and changed later with cw_update_contact_types (type associations). Contact types keep their label in description; name in cw_list_contact_types conditions is rewritten. cw_search_contacts rewrites a bare name = "..." into first / last name conditions and filters types through childConditions. There is no delete-contact tool: deactivate with inactiveFlag.

• cw_add_ticket_note emails nobody unless an email flag is set.

• cw_update_invoice only accepts the documented invoice paths; cw_update_invoice and cw_update_agreement_addition support dryRun.

• Transient failures are retried with backoff, honouring Retry-After: 429 always, 5xx and timeouts only for requests that are safe to repeat (reads, deletes, replace-only patches), so creates are never duplicated. One tool call stays under 100 seconds.

Run locally

uv sync
uv run connectwise-manage-mcp            # listens on 0.0.0.0:8080
curl -s http://127.0.0.1:8080/health
curl -s http://127.0.0.1:8080/mcp \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -H 'X-CW-Url: https://na.myconnectwise.net' -H 'X-CW-Company-Id: YOUR_COMPANY_ID' \
  -H 'X-CW-Public-Key: YOUR_PUBLIC_KEY' -H 'X-CW-Private-Key: YOUR_PRIVATE_KEY' \
  -H 'X-CW-Client-Id: YOUR_CLIENT_ID' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Environment variables (all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), MCP_TRANSPORT (http or stdio). Unknown variables are ignored. Credentials are never read from the environment.

Docker

docker build -t connectwise-manage-mcp .
docker run --rm -p 8080:8080 connectwise-manage-mcp

Development

uv sync
uv run pytest -q
uv run ruff check . && uv run ruff format --check .

Code is in src/connectwise_manage_mcp/ (one module per area under tools/), tests in tests/. The implementation follows the public ConnectWise PSA REST API documentation at https://developer.connectwise.com/.

License

Copyright 2026 MSPbots.ai. Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.

ConnectWise is a trademark of its owner. This project is not affiliated with or endorsed by ConnectWise.