NOLU CONSULTINGMCP server builds · Fixed price · All in writing

ConnectWise PSA · MCP server · For Claude

A ConnectWise PSA MCP server, so Claude can work with your ConnectWise data

ConnectWise PSA (formerly ConnectWise Manage) runs tickets, time, agreements and projects for many MSPs. An MCP server lets Claude search and update that data through the ConnectWise REST API, using your own API member keys.

Email your API access details / docs to gus@nolu.ai

Fixed price from US$1,500 · Scope, updates and acceptance in writing · No calls required.

Status: no official server yet

As of 30 October 2026, ConnectWise does not publish an official MCP server for ConnectWise PSA; community servers exist (for example from WYRE and mspstack).

MCP support changes quickly. Re-check ConnectWise’s developer documentation and announcements before you build or buy.

What Claude could do with it

These 10 tools cover the common work MSPs do in ConnectWise. Each one maps to a single REST endpoint.

ToolREST endpointWhat it does
search_ticketsGET /service/tickets (with conditions)Find service tickets by board, status, company or other conditions.
get_ticketGET /service/tickets/{id}Read one ticket and its details.
create_ticketPOST /service/ticketsOpen a new service ticket.
update_ticketPATCH /service/tickets/{id}Change fields such as status, priority or owner.
add_ticket_notePOST /service/tickets/{id}/notesAdd a note to a ticket.
search_companiesGET /company/companiesLook up client companies.
search_contactsGET /company/contactsLook up contacts.
log_time_entryPOST /time/entriesRecord time worked.
list_agreementsGET /finance/agreementsList client agreements.
list_projectsGET /project/projectsList projects.

Paths come from ConnectWise’s public API documentation. The exact endpoints, fields and final tool list are confirmed in writing at scoping, against your account.

Authentication

The REST API lives at https://{your-site}/v4_6_release/apis/3.0. For cloud tenants in North America the host is api-na.myconnectwise.net.

Authentication uses API member keys. Each request sends a Basic header built from base64(companyId+publicKey:privateKey), plus a clientId header.

Honest limits

How you’d connect it

The server runs two ways: locally over stdio, started with npx, or remotely over Streamable HTTP at a URL on your own host. The commands below use placeholders; your README has the real package name, URL and variables. NOLU does not run a shared hosted ConnectWise server.

Claude Code

# remote (Streamable HTTP)
claude mcp add --transport http connectwise-psa https://<your-host>/mcp

# local (stdio)
claude mcp add connectwise-psa -e CW_SITE=<value> -e CW_COMPANY_ID=<value> -e CW_PUBLIC_KEY=<value> -e CW_PRIVATE_KEY=<value> -e CW_CLIENT_ID=<value> -- npx -y <your-server-package>

Claude Desktop

For a remote server, add the URL https://<your-host>/mcp as a custom connector. For a local server, add it to claude_desktop_config.json:

{
  "mcpServers": {
    "connectwise-psa": {
      "command": "npx",
      "args": ["-y", "<your-server-package>"],
      "env": {
        "CW_SITE": "<value>",
        "CW_COMPANY_ID": "<value>",
        "CW_PUBLIC_KEY": "<value>",
        "CW_PRIVATE_KEY": "<value>",
        "CW_CLIENT_ID": "<value>"
      }
    }
  }
}

Cursor

In .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "connectwise-psa": { "url": "https://<your-host>/mcp" }
  }
}

Variable names above are examples. Keep credentials in local config or your host’s secret store, never in the repository.

Who it is for

Price

Starter

US$1,500

About 5 business days

  • Up to 10 tools from the list above, or your own
  • API-key/token authentication
  • Local stdio + remote Streamable HTTP
  • Tests, README and install docs for Claude Desktop, Claude Code and Cursor

Standard

US$3,000

About 7–10 business days

  • Up to 25 tools
  • OAuth 2.1 per the MCP specification
  • Hosted on your Vercel, Cloudflare or AWS account
  • 30 days of bug-fix support

TypeScript and the official MCP SDK. Private GitHub repository you own. 50% deposit, 50% on acceptance. Optional maintenance US$300/month; extra tools US$100 each. Full details on the MCP servers page.

Email your API access details / docs to gus@nolu.ai

Questions

Is there an official ConnectWise PSA MCP server?

As of 30 October 2026, ConnectWise does not publish an official MCP server for ConnectWise PSA; community servers exist (for example from WYRE and mspstack). This changes quickly, so check ConnectWise’s developer documentation before you decide.

What do we need from ConnectWise to start?

An API member with a public and private key, your company ID, your site URL and a Client ID from developer.connectwise.com. Share keys through a secret-sharing link, never by plain email.

Why not use a community server?

You can, and for a quick test it may be enough. A custom build gives you a tool list scoped to your workflows, tests, install docs and a private repository you own. Whichever you use, review what it can read and write before you give it credentials.

What does it cost and how do we start?

Starter is US$1,500 (about 5 business days, up to 10 tools, API-key/token auth). Standard is US$3,000 (about 7–10 business days, up to 25 tools, OAuth 2.1, hosted). Email gus@nolu.ai with what you want Claude to do in ConnectWise; you get a proposed tool list and fixed price in writing within 1 business day.

Start in writing.

Tell us which ConnectWise workflows you want Claude to handle and what API access you have. You get a proposed tool list and fixed price within 1 business day.

Email your API access details / docs to gus@nolu.ai

See also: MCP server builds · Top MCP server development companies in 2026