ConnectWise Manage MCP Server

An MCP server that lets Claude (or any MCP client) work with ConnectWise Manage PSA — search and manage service tickets, log notes and time, and look up companies and contacts.

Built in TypeScript on the official MCP SDK. Ships as a one-click Claude Desktop extension (.mcpb) and as an npm package.

Installation

Pick the path that matches your users.

Option A — Claude Desktop extension (easiest, no technical setup) ⭐

For end users / non-technical staff. No Node, no build, no JSON.

1. Get the connectwise-manage.mcpb file (build it with npm run bundle, or download it from your internal share / releases page).
2. Open Claude Desktop → Settings → Extensions.
3. Drag the .mcpb file into the window (or click Install extension).
4. A form appears — fill in the five fields (the private key and client ID are masked):
   • Site URL (prefilled with the NA cloud default)
   • Company ID
   • API Public Key
   • API Private Key
   • Integrator Client ID
5. Click Save, then ask Claude: "Test the ConnectWise connection."

That's the entire setup. Credentials are stored by Claude Desktop's secure config — nothing to edit by hand.

Option B — Claude Code / any client via npx

For CLI and developer users. Requires Node.js 18+.

claude mcp add connectwise \
  --env CW_SITE_URL=https://api-na.myconnectwise.net \
  --env CW_COMPANY_ID=your_company_id \
  --env CW_PUBLIC_KEY=your_public_key \
  --env CW_PRIVATE_KEY=your_private_key \
  --env CW_CLIENT_ID=your_client_id_guid \
  -- npx -y connectwise-mcp-server

Or add it manually to any MCP client's JSON config (e.g. Claude Desktop's claude_desktop_config.json):

{
  "mcpServers": {
    "connectwise": {
      "command": "npx",
      "args": ["-y", "connectwise-mcp-server"],
      "env": {
        "CW_SITE_URL": "https://api-na.myconnectwise.net",
        "CW_COMPANY_ID": "your_company_id",
        "CW_PUBLIC_KEY": "your_public_key",
        "CW_PRIVATE_KEY": "your_private_key",
        "CW_CLIENT_ID": "your_client_id_guid"
      }
    }
  }
}

Option C — From source (for development)

npm install
npm run build
npm start   # runs dist/index.js (needs the env vars set)

Getting ConnectWise credentials

You need three things from ConnectWise:

1. API Member key pair — In ConnectWise: System → Members → API Members. Create an API member (give it a security role scoped to what the MCP should access), open it, go to the API Keys tab, and generate a key pair. Copy the public and private keys (the private key is shown only once).
2. Integrator / Client ID — Register at https://developer.connectwise.com under My Account → Client IDs. This GUID is sent as the clientId header.
3. Site URL — Your API host, e.g. https://api-na.myconnectwise.net (NA cloud), https://api-eu.myconnectwise.net (EU), or your on-prem hostname. Do not include the /v4_6_release/apis/3.0 path — the server adds it.

| Config field | Env var | Required | |---|---|---| | Site URL | CW_SITE_URL | yes | | Company ID | CW_COMPANY_ID | yes | | API Public Key | CW_PUBLIC_KEY | yes | | API Private Key | CW_PRIVATE_KEY | yes | | Integrator Client ID | CW_CLIENT_ID | yes | | API version (optional pin) | CW_API_VERSION | no |

Tools

| Tool | Type | Purpose | |---|---|---| | connectwise_test_connection | read | Verify credentials + report system info. Run this first. | | connectwise_search_tickets | read | Search/list service tickets with conditions filters | | connectwise_get_ticket | read | Full detail on one ticket | | connectwise_create_ticket | write | Create a ticket on a board | | connectwise_update_ticket | write | Change status/priority/owner/summary/board | | connectwise_list_ticket_notes | read | List a ticket's notes | | connectwise_add_ticket_note | write | Add a discussion/internal/resolution note | | connectwise_add_time_entry | write | Log time against a ticket | | connectwise_search_companies | read | Search/list companies | | connectwise_get_company | read | Full detail on one company | | connectwise_search_contacts | read | Search/list contacts | | connectwise_get_contact | read | Full detail on one contact |

The conditions query language

The search tools accept a ConnectWise conditions string (SQL-like):

• Strings must be double-quoted: status/name="New"
• Booleans: closedFlag=false
• Dates use bracket syntax: dateEntered>[2026-01-01T00:00:00Z]
• Reference fields use /: company/id=123, board/name="Help Desk"
• Combine with and / or; operators: = != < <= > >=, contains, like
• Example: company/id=123 and closedFlag=false and summary contains "backup"

Distributing to your organization

• Build the extension: npm run bundle produces connectwise-manage.mcpb (build → prune dev deps → pack). Host it on an internal share, SharePoint, or a GitHub release, and have staff drag it into Claude Desktop.
• Publish to npm (enables Option B): npm publish (the package is set to public access; prepublishOnly rebuilds first).
• Least privilege: the API member's security role governs everything the MCP can see or do. Create a dedicated member with only the access you need.
• Per-user credentials: with the MCPB path each user enters their own keys, so ConnectWise auditing attributes actions to the right person.

Development

npm run dev      # watch mode (tsx)
npm run build    # compile to dist/
npm run bundle   # produce connectwise-manage.mcpb
npm start        # run compiled server

# Inspect tools interactively:
npx @modelcontextprotocol/inspector node dist/index.js

Project layout

src/
  index.ts            # server bootstrap + tool registration
  constants.ts        # API path, limits, enums
  schemas/common.ts   # shared Zod fragments (conditions, paging, format)
  services/
    client.ts         # auth + HTTP + error normalization
    format.ts         # response/markdown/pagination helpers
  tools/
    system.ts         # connection test
    tickets.ts        # service desk
    companies.ts
    contacts.ts
manifest.json         # MCPB (Claude Desktop extension) manifest + config form

To add agreements, configurations, projects, or invoices: create a new file in src/tools/, follow the pattern in companies.ts, register it in index.ts, and add the tool names to manifest.json. The shared cwRequest client handles auth, paging, and errors for you.

Security notes

• Credentials are read from environment variables only; nothing is persisted by the server. Claude Desktop stores extension config in its own secure store.
• The API member's security role governs what the MCP can see and do — scope it to least privilege.
• Write tools (create_ticket, update_ticket, add_ticket_note, add_time_entry) are annotated as non-read-only so clients can gate them behind confirmation.