ConnectWise PSA MCP

Runtime-neutral stdio MCP server for ConnectWise PSA (formerly Manage). It runs under OpenClaw, Hermes, or Claude Code through the Alfe integration manifest.

Launch the released package with npx -y @alfe.ai/[email protected]. Node 22+ and an existing alfe login configuration are required. There are no provider-credential environment variables or separate login files.

Create a ConnectWise PSA connection in Alfe Connections with the final PSA API server origin, company ID, and an API member's public/private keys. The Alfe service supplies its registered PSA ClientID. For cloud tenants, use your region's API hostname (for example https://api-na.myconnectwise.net), rather than a browser deep link. On-premises deployments require a publicly resolvable HTTPS hostname and a trusted TLS certificate. The runtime appends /v4_6_release/apis/3.0 and refuses redirects and non-public destinations.

Call connectwise_psa_list_connections first. Every provider operation requires the selected connectionId; it never silently chooses a default account. Credentials are resolved again on every operation, so changing keys or removing access applies to the next call without restarting the server.

Available tools:

• Connection discovery
• List companies, contacts, service boards, priorities, members, and tickets
• Get a company, contact, or ticket
• List a board's statuses and a ticket's direct notes
• Create a service ticket, update selected fields, and append a note

List tools return a single page (25 rows by default, maximum 100), with page, pageSize, conditions, and orderBy. Notes default to internal-only. Discussion/resolution notes may be customer-visible; select visibility deliberately. Writes are never automatically retried: after a timeout, read the ticket or notes to check whether the write succeeded before repeating it. The API member's PSA security role controls which operations are allowed.

API references and verification status

• ConnectWise Getting Started documents product-specific developer access and sandbox requests.
• PSA REST reference and Developer Guide are the canonical endpoint and authentication references.

On 2026-09-08 the REST reference and Developer Guide required an approved Developer Network login. The implementation uses the PSA REST 3.0 resource contract, with local HTTP-contract/security/MCP-exchange tests; those tests do not constitute verification against a customer PSA server. An approved PSA sandbox should verify company/board/status reads, create a disposable ticket, update it, and add an internal note before release. Version-specific codebase paths other than /v4_6_release are not supported by this release.

Development

pnpm --filter @alfe.ai/connectwise-psa-mcp typecheck
pnpm --filter @alfe.ai/connectwise-psa-mcp lint
pnpm --filter @alfe.ai/connectwise-psa-mcp test
pnpm --filter @alfe.ai/connectwise-psa-mcp build