ConnectWise Manage

It requires CW_MANAGE_COMPANY_ID, PUBLIC/PRIVATE KEY, CLIENT_ID, and CW_MANAGE_URL, which are sensitive credentials and connection details that can grant access to ConnectWise Manage tenant data. If exposed, they could be used to read or act on tickets, projects, time entries, and other business records. No explicit credential-abuse mechanism is shown, but these secrets should be handled as highly sensitive.

By design, the tool will make network requests to the ConnectWise Manage instance specified by CW_MANAGE_URL and may transmit business data such as companies, tickets, projects, and time entries. No fixed unrelated third-party endpoint is disclosed; based on the material, it mainly connects to the user-configured target service, which is a normal outbound pattern for this type of integration.

The system flags it as executes-code, meaning the MCP runs a local service process and handles requests on the host. The provided material does not indicate unusual system privileges or command execution unrelated to its stated function, so this aligns with normal local execution risk for an MCP tool.

Per the description, its data access scope is centered on ConnectWise Manage PSA resources such as companies, tickets, projects, and time entries, which may include customer and operational data. The material does not indicate broad local file access or permissions beyond the PSA integration purpose, but the API account should still be constrained by least privilege.

Positive factors include an official registry source, open-source code, and updates within the last year. Caveats are the minimal README, no declared license, and low visible community adoption (0 stars), which reduce external review and reuse signals. Overall, there is no strong supply-chain red flag warranting a high-risk rating, but source and dependencies should still be reviewed before deployment.