ConnectWise PSA runs on your own machine — the client starts it, so there is no endpoint to ping. 167 installs a week from npm. Last commit 7 Oct 2026.
ConnectWise PSA (Manage) MCP server — tickets, time entries, companies, configurations, BYOK
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет mcp-connectwise-psa ссылается на mspstack/mcp-connectwise-psa
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-connectwise-psa -e 'CW_SITE=<CW_SITE>' -e 'CW_COMPANY_ID=<CW_COMPANY_ID>' -e 'CW_CLIENT_ID=<CW_CLIENT_ID>' -e 'CW_PUBLIC_KEY=<CW_PUBLIC_KEY>' -e 'CW_PRIVATE_KEY=<CW_PRIVATE_KEY>' -- npx -y mcp-connectwise-psa{
"mcpServers": {
"mcp-connectwise-psa": {
"command": "npx",
"args": [
"-y",
"mcp-connectwise-psa"
],
"env": {
"CW_CLIENT_ID": "<CW_CLIENT_ID>",
"CW_COMPANY_ID": "<CW_COMPANY_ID>",
"CW_PRIVATE_KEY": "<CW_PRIVATE_KEY>",
"CW_PUBLIC_KEY": "<CW_PUBLIC_KEY>",
"CW_SITE": "<CW_SITE>"
}
}
}
}[mcp_servers.mcp-connectwise-psa]
command = "npx"
args = ["-y", "mcp-connectwise-psa"]
env = { CW_SITE = "<CW_SITE>", CW_COMPANY_ID = "<CW_COMPANY_ID>", CW_CLIENT_ID = "<CW_CLIENT_ID>", CW_PUBLIC_KEY = "<CW_PUBLIC_KEY>", CW_PRIVATE_KEY = "<CW_PRIVATE_KEY>" }{
"mcpServers": {
"mcp-connectwise-psa": {
"command": "npx",
"args": [
"-y",
"mcp-connectwise-psa"
],
"env": {
"CW_CLIENT_ID": "<CW_CLIENT_ID>",
"CW_COMPANY_ID": "<CW_COMPANY_ID>",
"CW_PRIVATE_KEY": "<CW_PRIVATE_KEY>",
"CW_PUBLIC_KEY": "<CW_PUBLIC_KEY>",
"CW_SITE": "<CW_SITE>"
}
}
}
}{
"servers": {
"mcp-connectwise-psa": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-connectwise-psa"
],
"env": {
"CW_CLIENT_ID": "<CW_CLIENT_ID>",
"CW_COMPANY_ID": "<CW_COMPANY_ID>",
"CW_PRIVATE_KEY": "<CW_PRIVATE_KEY>",
"CW_PUBLIC_KEY": "<CW_PUBLIC_KEY>",
"CW_SITE": "<CW_SITE>"
}
}
}
}Put your own values in place of
<CW_SITE> (ConnectWise host (e.g. na.myconnectwise.net or an on-prem host; full URLs accepted)), <CW_COMPANY_ID> (ConnectWise login company id), <CW_CLIENT_ID> (Integration clientId from developer.connectwise.com), <CW_PUBLIC_KEY> (API member public key), <CW_PRIVATE_KEY> (API member private key).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
CW_MEMBER_IDENTIFIER (Member identifier the API keys belong to — enables "my tickets"/"my time" tools).
Alternatives to ConnectWise PSA
same job, measured the same wayConnectWise PSA (Manage) MCP server — tickets, time entries, companies, configurations, BYOK
MCP server for ConnectWise Manage PSA — companies, tickets, projects, time entries, and more.
MCP server for ConnectWise Manage PSA — companies, tickets, projects, time entries, and more.
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
Read Desk365 tickets, conversations, contacts, companies, time entries and knowledge articles.
ConnectWise PSA — questions
Answers built from our own checks of this server.