Log inSubmit server
ConnectWise PSA logo

ConnectWise PSA

ConnectWise PSA tools for tickets, time, scheduling, billing, assets, API access, and optional on-prem SQL.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install ConnectWise PSA

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "connectwise-psa-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-connectwise-psa"
      ],
      "env": {
        "CW_SITE": "YOUR_VALUE_HERE",
        "CW_COMPANY_ID": "YOUR_VALUE_HERE",
        "CW_CLIENT_ID": "YOUR_VALUE_HERE",
        "CW_PUBLIC_KEY": "YOUR_VALUE_HERE",
        "CW_PRIVATE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 41 tools correctly (6d ago).

Overview

The ConnectWise PSA MCP server connects AI assistants to ConnectWise PSA (Manage) through role-focused tools for tickets, time, companies, configurations, scheduling, and finance. It supports local stdio and shared streamable HTTP deployments, with Docker available for HTTP use. Each session can use the caller's ConnectWise member API keys, so ConnectWise security roles govern access and attribute writes to the member. Reach for it when an assistant needs to search or update PSA records, manage schedules and timesheets, inspect billing data, or query an on-prem Manage database.

Use cases

  • Search and update service or project tickets
  • Log time and submit technician timesheets
  • Schedule ticket work and check member availability
  • Review invoices, agreements, and unbilled time
  • Run read-only reports against an on-premises Manage database

Key features

  • Curated ticket, time, company, configuration, schedule, and finance toolsets
  • Per-member ConnectWise API key authentication
  • Persona presets and per-session toolset selection
  • Read-only access to the broader ConnectWise API
  • Optional on-premises read-only T-SQL and saved queries
  • Stdio, streamable HTTP, and Docker deployment options

Tools41

What ConnectWise PSA lets your agent do. Expand a tool for its parameters.

Verified live~9.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 46d

What it can do

From the 41 tools this server returned when we ran it; 41 declare their own safety hints.

Can delete or modify data · 1Handles credentials · 2Makes network requests · 41Read-only tools · 40
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age104 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · mcp-connectwise-psa (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6Stargazers on the source repository.
Last commit16d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed41Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How ConnectWise PSA works

What ConnectWise PSA MCP server does

The ConnectWise PSA MCP server exposes selected ConnectWise PSA (Manage) operations through MCP tools. Its curated toolsets cover tickets, time entries and timesheets, companies and contacts, device configurations, scheduling, and read-only finance data. Ticket tools handle both service and project tickets, while other tools support activities such as adding notes, changing ticket ownership or status, logging time, and scheduling work.

An advanced toolset provides a searchable catalog of roughly 1,150 ConnectWise API endpoints and a read-only GET operation for paths not covered by the curated tools. An optional sql toolset supports read-only T-SQL against an on-premises Manage database, including schema discovery and saved-query management.

How it works

The ConnectWise PSA MCP server can run over stdio for a local assistant or streamable HTTP for a shared deployment. HTTP exposes /mcp for MCP traffic and /health for liveness checks. HTTP sessions are held in memory, so a deployment should use one instance or provide sticky session routing.

Local stdio uses API credentials supplied through environment variables. HTTP clients provide the public and private member keys in request headers, along with an optional member identifier for “my” ticket and time operations. Both key headers are required together, and a session rejects a different key pair after initialization. ConnectWise applies the member's security role to API operations, and write activity is attributed to that member.

Setup and configuration

Build the project with npm install && npm run build, then start node dist/index.js with the ConnectWise site, company ID, client ID, public key, private key, and member identifier configured. A ConnectWise integration client ID is required, and member API keys are created in the ConnectWise administration interface.

For HTTP, start the process with --transport http --port 3000; Docker can publish the same port. Toolsets can be selected with CW_TOOLSETS or --toolsets in stdio mode, and with the x-cw-toolsets header over HTTP. Presets include tech, dispatch, invoicing, and all. The default is all for configured capabilities.

Tools and capabilities

  • Tickets: search, inspect, create, update, add notes, discover boards and priorities, and review ticket time and tasks.
  • Time: create entries, inspect personal time, look up work roles and types, and list or submit timesheets.
  • Companies: search companies and contacts, retrieve contact details, and list company sites.
  • Configurations: list and inspect devices or assets, including available inventory details.
  • Schedule: list, create, reschedule, and cancel entries, and inspect member availability.
  • Finance: read invoices, agreements, and unbilled time.

The sql tools are server-wide rather than member-scoped. If database variables are configured, the default all selection can expose the read-only PSA database to sessions that do not narrow their toolsets. The only destructive operation listed is schedule-entry deletion; saved-query management writes to the query-library file, while database access remains read-only.

Limitations and notes

The server does not define an MCP-level role system for HTTP. Authorization depends on the supplied ConnectWise member keys, except for SQL access, which uses a server-wide read-only database login and is not filtered by the member's ConnectWise permissions. Deployers should narrow toolsets when appropriate and protect database credentials.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about ConnectWise PSA

ConnectWise PSA is an MCP server that connects AI assistants to ConnectWise PSA (Manage) through tools for tickets, time, companies, configurations, scheduling, and read-only finance. It also provides read-only access to broader API paths and optional on-premises SQL, and supports stdio and streamable HTTP deployments.

Install dependencies, build the project, and start `node dist/index.js` with the required ConnectWise environment variables. The documented setup uses `npm install && npm run build`; Docker is also available for HTTP deployments.

Send the ConnectWise public and private member API keys in the `x-cw-public-key` and `x-cw-private-key` headers on initialization and subsequent requests. You can also send `x-cw-member-id` to enable personal ticket and time tools.

Yes, when the `CW_DB_*` settings are configured. The SQL toolset runs read-only T-SQL against the on-premises Manage database and includes schema search and saved-query tools; it uses a server-wide database login rather than the caller's ConnectWise member permissions.

Yes, the README provides a Claude Desktop configuration using the server's stdio command and environment variables. Claude Code is also named as a supported configuration example.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewConnectWise PSA AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/connectwise-psa-2?style=directory)](https://allmcps.com/mcp/connectwise-psa-2)
HTML Embed
<a href="https://allmcps.com/mcp/connectwise-psa-2"><img src="https://allmcps.com/api/badge/connectwise-psa-2?style=directory" alt="ConnectWise PSA on AllMCPs" /></a>