io.github.Servosity/connectwise-manage-mcp

MCPcommunity
v0.2.0io.github.ServosityUnknownUpdated 4d agoGitHub

Every ConnectWise PSA workflow from the terminal - with a typed conditions query builder, offline

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
46GitHub stars
10Forks
4d agoLast update
Needs 3 credentials before it runs
  • CW_CLIENT_IDOAuth apprequired

    Set the CW_CLIENT_ID credential for the ConnectWise Manage MCP server.

  • CW_PRIVATE_KEYAPI keyrequired

    API Member private key used as the composite Basic auth password.

  • CW_PUBLIC_KEYAPI keyrequired

    API Member public key used with the company ID in the composite Basic auth username.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.Servosity
LicenseUnknown
Version0.2.0
Sourcemcp-registry
GitHubservosity/msp-skills
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 23, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable1mo ago

The repository archive could not be read at scan time (tarball exceeds size cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Every ConnectWise PSA workflow from the terminal - with a typed conditions query builder, offline

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.