What it says
The record the registry holds
How you get it
There is no address to call. This one is a package you install and run yourself, wherever your assistant runs.
mcp-connectwise-psa · npm · 0.9.0
the record
Copied from the official MCP registry, exactly as it holds it.
{
"server" : {
"$schema" : "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json" ,
"name" : "io.github.mspstack/mcp-connectwise-psa" ,
"description" : "ConnectWise PSA (Manage) MCP server — tickets, time entries, companies, configurations, BYOK" ,
"title" : "ConnectWise PSA" ,
"repository" : {
"url" : "https://github.com/mspstack/mcp-connectwise-psa" ,
"source" : "github"
},
"version" : "0.9.0" ,
"websiteUrl" : "https://github.com/mspstack/mcp-connectwise-psa#readme" ,
"packages" : [
{
"registryType" : "npm" ,
"registryBaseUrl" : "https://registry.npmjs.org" ,
"identifier" : "mcp-connectwise-psa" ,
"version" : "0.9.0" ,
"runtimeHint" : "npx" ,
"transport" : {
"type" : "stdio"
},
"environmentVariables" : [
{
"description" : "ConnectWise host (e.g. na.myconnectwise.net or an on-prem host; full URLs accepted)" ,
"isRequired" : true,
"name" : "CW_SITE"
},
{
"description" : "ConnectWise login company id" ,
"isRequired" : true,
"name" : "CW_COMPANY_ID"
},
{
"description" : "Integration clientId from developer.connectwise.com" ,
"isRequired" : true,
"name" : "CW_CLIENT_ID"
},
{
"description" : "API member public key" ,
"isRequired" : true,
"isSecret" : true,
"name" : "CW_PUBLIC_KEY"
},
{
"description" : "API member private key" ,
"isRequired" : true,
"isSecret" : true,
"name" : "CW_PRIVATE_KEY"
},
{
"description" : "Member identifier the API keys belong to — enables \" my tickets\"/\"my time\" tools",
"name" : "CW_MEMBER_IDENTIFIER"
},
{
"description" : "Comma list of toolsets/presets (default: all). Add sql for database queries." ,
"name" : "CW_TOOLSETS"
},
{
"description" : "ConnectWise SQL Server host (on-prem only) — enables the opt-in sql toolset" ,
"name" : "CW_DB_HOST"
},
{
"description" : "ConnectWise Manage database, e.g. cwwebapp_acme" ,
"name" : "CW_DB_NAME"
},
{
"description" : "Dedicated read-only database login (db_datareader)" ,
"name" : "CW_DB_USER"
},
{
"description" : "Password for the read-only database login" ,
"isSecret" : true,
"name" : "CW_DB_PASSWORD"
},
{
"description" : "Path to a writable JSON file holding saved SQL queries" ,
"name" : "CW_DB_QUERY_LIBRARY"
}
]
}
]
},
"_meta" : {
"io.modelcontextprotocol.registry/official" : {
"status" : "active" ,
"statusChangedAt" : "2026-08-19T08:43:51.257366Z" ,
"publishedAt" : "2026-08-19T08:43:51.257366Z" ,
"updatedAt" : "2026-08-19T08:43:51.257366Z" ,
"isLatest" : true
}
}
}
Make it installable
Draft an Agent Plugin from ConnectWise PSA
close
Paste it into your assistant. It asks for the manifest, the server wiring and the skills, and for an honest account of what this record does not say. Read that second file first.
copy the prompt
168 lines · the record is inside it, so nothing else is needed
Draft an Agent Plugin (agent-plugins.org, specification 1.1.0) that wraps the
MCP server described below, so that somebody could install one thing and have
an assistant that knows when and how to use it.
An Agent Plugin is one installable unit: a `plugin.json` manifest, an
`mcp.json` that wires up the servers it needs, and a `skills/` directory
where each skill is a folder holding a `SKILL.md`. Hand back every file in
full, each under its own path, ready to save.
1. Write `plugin.json` with `$schema` exactly `https://agent-plugins.org/schemas/1.1.0/plugin.schema.json`. The name is
1 to 64 characters of a-z, 0-9, `-` and `.`, alphanumeric at both ends, with
no `--` and no `..` in it.
2. Write `mcp.json` wiring THIS server exactly as its record declares it. A
remote keeps the URL and the transport type as written. A package keeps the
registry, the identifier and the version as written. Do not invent a command,
a port, a flag or an argument that is not in the record.
3. Every secret stays an input. No key, token, password or connection string
belongs in either file. Declare what has to be supplied, name it, and say what
it is for.
4. Do not invent tools. The record lists the tools it lists, and if it lists
none then the honest plugin says the tool list was not published rather than
guessing one from the description.
5. Skills are jobs, not tools. Write one skill per thing somebody would actually
ask for, and inside each one say when to reach for this server, what a good
result looks like, and what to do when it comes back empty. A skill per tool
is a manual page with a different filename.
6. Say where it stops. Name what this plugin will not do — what it has no tool
for, what needs a person, and what it must not be pointed at. A plugin with no
stated edge reads as one with no edge.
7. Keep the author's own words for the description. If you would rather say it
differently, say yours somewhere else and leave theirs where it is.
8. Record which version of the server you wrapped, and where the record came
from, at the top of `plugin.json`'s description or in the readme. A plugin
nobody can trace back to a version is one nobody can update.
Produce a second file alongside them, `LIMITS.md`, and treat it as the more
important of the two. The plugin is for whoever installs it. This is for
whoever has to decide whether installing it is a good idea, and that is
usually a different person who will never read the manifest.
It has three parts.
**What this is built from.** One paragraph: whose server it is, what the
record says it does, which version, and the fact that the record is all you
had. Say plainly that nobody ran it.
**What the record does not say.** One entry per gap. Whether the tool list was
published. What the server does with what it reads. What it costs. Whether it
writes anything anywhere. What credentials it will ask for and what those
credentials can reach. An unanswered question stays an unanswered question:
do not fill one in from the description or from what similar servers usually do.
**What a person has to check before trusting it.** The specific things
somebody should verify for themselves, in the order that would stop them
soonest if the answer is bad.
Write it in plain English, and do not soften it. A plugin drafted from a
directory record is a starting point to argue with, not something to install
into anything that matters.
The server record follows, exactly as the public index holds it. It is
everything I have: nobody has run this server, called a tool on it, or checked
that the address answers.
```json
{
"server": {
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"name": "io.github.mspstack/mcp-connectwise-psa",
"description": "ConnectWise PSA (Manage) MCP server — tickets, time entries, companies, configurations, BYOK",
"title": "ConnectWise PSA",
"repository": {
"url": "https://github.com/mspstack/mcp-connectwise-psa",
"source": "github"
},
"version": "0.9.0",
"websiteUrl": "https://github.com/mspstack/mcp-connectwise-psa#readme",
"packages": [
{
"registryType": "npm",
"registryBaseUrl": "https://registry.npmjs.org",
"identifier": "mcp-connectwise-psa",
"version": "0.9.0",
"runtimeHint": "npx",
"transport": {
"type": "stdio"
},
"environmentVariables": [
{
"description": "ConnectWise host (e.g. na.myconnectwise.net or an on-prem host; full URLs accepted)",
"isRequired": true,
"name": "CW_SITE"
},
{
"description": "ConnectWise login company id",
"isRequired": true,
"name": "CW_COMPANY_ID"
},
{
"description": "Integration clientId from developer.connectwise.com",
"isRequired": true,
"name": "CW_CLIENT_ID"
},
{
"description": "API member public key",
"isRequired": true,
"isSecret": true,
"name": "CW_PUBLIC_KEY"
},
{
"description": "API member private key",
"isRequired": true,
"isSecret": true,
"name": "CW_PRIVATE_KEY"
},
{
"description": "Member identifier the API keys belong to — enables \"my tickets\"/\"my time\" tools",
"name": "CW_MEMBER_IDENTIFIER"
},
{
"description": "Comma list of toolsets/presets (default: all). Add sql for database queries.",
"name": "CW_TOOLSETS"
},
{
"description": "ConnectWise SQL Server host (on-prem only) — enables the opt-in sql toolset",
"name": "CW_DB_HOST"
},
{
"description": "ConnectWise Manage database, e.g. cwwebapp_acme",
"name": "CW_DB_NAME"
},
{
"description": "Dedicated read-only database login (db_datareader)",
"name": "CW_DB_USER"
},
{
"description": "Password for the read-only database login",
"isSecret": true,
"name": "CW_DB_PASSWORD"
},
{
"description": "Path to a writable JSON file holding saved SQL queries",
"name": "CW_DB_QUERY_LIBRARY"
}
]
}
]
},
"_meta": {
"io.modelcontextprotocol.registry/official": {
"status": "active",
"statusChangedAt": "2026-08-19T08:43:51.257366Z",
"publishedAt": "2026-08-19T08:43:51.257366Z",
"updatedAt": "2026-08-19T08:43:51.257366Z",
"isLatest": true
}
}
}
```
The server is listed as "ConnectWise PSA".