Skip to main content
ClaudeWave
ES, Spanish
WYRE-AI / MCP Servers · Registry oficial

connectwise-manage-mcp

MCP server for ConnectWise Manage (PSA) — tickets, companies, contacts, projects, and time entry tools for AI assistants

  • 28 estrellas
  • 44 forks
  • 9 issues abiertos
  • Lenguaje: TypeScript
  • Licencia: Apache-2.0
  • actualizado

Instalación

Claude Code CLI
git clone https://github.com/WYRE-AI/connectwise-manage-mcp
  1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
  2. Replace any <placeholder> values with your API keys or paths.
  3. Restart Claude. The MCP server and its tools appear automatically.

Clone https://github.com/WYRE-AI/connectwise-manage-mcp and follow its README for install instructions.

README

Resumen de MCP Servers

README completo en GitHub

ConnectWise Manage MCP Server

License Node.js

Let your AI assistant work directly with ConnectWise Manage. Search tickets, log time, look up companies and contacts, manage projects — through natural conversation instead of clicking through the CWM interface.

This is a Model Context Protocol (MCP) server that gives Claude (or any MCP-compatible AI) 84 tools covering the daily operations ConnectWise Manage shops depend on. Works with both cloud-hosted and self-hosted CWM instances — just point it at your server.

Part of the MSP Claude Plugins ecosystem — a growing suite of AI integrations for the MSP stack including Autotask, Datto RMM, IT Glue, HaloPSA, NinjaOne, Huntress, and more. Built by MSPs, for MSPs.

One-Click Deployment

Deploy to DO

Deploy to Cloudflare Workers

Note on registry auth: This server depends only on public npm packages, so the Cloudflare and DigitalOcean cloud builders install its dependencies anonymously — no token is required for one-click deploy. (If a future release adds a private @wyre-ai/* dependency, you would supply a GitHub PAT with read:packages as a build variable — NODE_AUTH_TOKEN for Cloudflare Workers, a build-time GITHUB_TOKEN secret for DigitalOcean.)

Installing the published package: The released package is published to the GitHub Packages npm registry, which requires authentication on every install (even for public packages). To install it, authenticate npm to npm.pkg.github.com with a GitHub PAT that has read:packages:

export NODE_AUTH_TOKEN=$(gh auth token)
npm install @wyre-ai/connectwise-manage-mcp

For deploying to Azure Container Apps with Entra ID OAuth 2.1, see AZURE_ACA_DEPLOYMENT.md.

Configuration

Environment Variables
VariableRequiredDescription
CW_MANAGE_COMPANY_IDFor stdio and AUTH_MODE=envYour ConnectWise company identifier
CW_MANAGE_PUBLIC_KEYFor stdio and AUTH_MODE=envAPI member public key
CW_MANAGE_PRIVATE_KEYFor stdio and AUTH_MODE=envAPI member private key
CW_MANAGE_CLIENT_IDFor stdio and AUTH_MODE=envClient ID from ConnectWise Developer Portal
CW_MANAGE_URLNoAPI base URL (see below)
CW_MANAGE_REJECT_UNAUTHORIZEDNoSet to false for self-signed certs (default: true)
MCP_TRANSPORTNostdio (default) or http
MCP_HTTP_PORTNoHTTP port (default: 8080)
MCP_HTTP_HOSTNoBind address when MCP_TRANSPORT=http. Defaults to 127.0.0.1. A configured CONDUIT_S2S_SECRET honors this value. The container image sets 0.0.0.0.
CONDUIT_S2S_SECRETYes for HTTPService-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, secret, your-s2s-secret, replace-me, and similar). Compose will not start when it is unset. Never commit a real value. Leave it empty in .env.example.
MCP_ALLOW_INSECURE_DEVNoSet to 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and listens on 127.0.0.1 only (a wider MCP_HTTP_HOST is overridden). A placeholder secret is still refused.
AUTH_MODENoenv (default) or gateway. Gateway mode requires X-CW-Company-Id, X-CW-Public-Key, X-CW-Private-Key, and X-CW-Client-Id on each /mcp request. env uses CW_MANAGE_* after S2S auth succeeds.

/health stays unauthenticated and does not read ConnectWise credentials. The stdio transport does not use CONDUIT_S2S_SECRET.

HTTP authentication

With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The header value is:

t=<unix seconds>,v1=<hex hmac-sha256>

v1 is HMAC-SHA256 (hex, lowercase) of the ASCII string t=, keyed with CONDUIT_S2S_SECRET. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401. The process never writes the secret to logs.

X-Gateway-S2S: t=1710000000,v1=<hmac-sha256("t=1710000000")>

In AUTH_MODE=gateway, /mcp also requires X-CW-Company-Id, X-CW-Public-Key, X-CW-Private-Key, and X-CW-Client-Id (X-CW-URL is optional). Those headers are the credential source for that request. A request missing any required header returns 401.

Entra OAuth discovery routes stay available when MCP_OAUTH_ENABLED=true. POST /mcp still requires a valid X-Gateway-S2S header when the secret is set.

API Base URL (CW_MANAGE_URL)
Instance TypeURL
Cloud (North America)https://api-na.myconnectwise.net (default)
Cloud (Europe)https://api-eu.myconnectwise.net
Cloud (Australia)https://api-au.myconnectwise.net
Self-hostedhttps://cwm.yourcompany.com

For self-hosted instances, set CW_MANAGE_URL to your server's base URL. The server automatically appends /v4_6_release/apis/3.0 unless the URL already contains that path.

If your self-hosted instance uses a self-signed certificate, also set CW_MANAGE_REJECT_UNAUTHORIZED=false.

Getting Your API Keys
  1. Log in to your ConnectWise Manage instance

  2. Navigate to System > Members > API Members

  3. Create a new API member with appropriate permissions

  4. Generate API keys for the member

  5. Get your Client ID from the ConnectWise Developer Portal

Available Tools

Interactive Ticket Card (MCP Apps)

cw_get_ticket renders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card "Add note" round-trip via cw_add_ticket_note that always posts internal-only (internalAnalysisFlag) notes; plain-JSON behavior is unchanged in other hosts. The card is neutral by default and brandable via window.__BRAND__ injection or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL, MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG, MCP_BRAND_TEXT) — no rebuild needed.

Tickets
  • cw_search_tickets — Search service tickets with conditions

  • cw_get_ticket — Get a ticket by ID

  • cw_get_ticket_configurations — List configuration references associated with a service ticket (paged)

  • cw_update_ticket_configurations — Add/remove ticket configuration associations in an ordered batch, reporting every outcome

  • cw_create_ticket — Create a new service ticket. Optional parentTicketId (the same field cw_get_ticket returns) creates the ticket as a child of that parent.

  • cw_update_ticket — Update a ticket (JSON Patch)

  • cw_get_ticket_notes — Get all notes on a ticket (including child ticket notes)

  • cw_add_ticket_note — Add a note to a ticket (discussion, internal, or resolution). Nothing is emailed unless processNotifications is true. emailContactFlag, emailResourceFlag, emailCcFlag, and emailCc are not ServiceNote fields and are not sent (posting them is a ConnectWise 400). A true flag only turns on processNotifications. Recipients come from the ticket automaticEmailContactFlag, automaticEmailResourceFlag, automaticEmailCcFlag, and automaticEmailCc. Optional memberId is sent as member.id and sets the author; omit it and Manage attributes the note to the API member. The create response reports internalFlag / externalFlag from the note type that was stored, so an internal note is not also reported as external.

Companies
  • cw_search_companies — Search companies

  • cw_get_company — Get a company by ID

  • cw_create_company — Create a new company

  • cw_update_company — Update a company (JSON Patch)

Contacts
  • cw_search_contacts — Search contacts. Filter contact type with typeName, typeId, or childConditions (for example types/name = "Primary"). types / types/name in conditions is invalid and returns 400 ApiFindCondition because type is a child collection; the tool moves those clauses to childConditions. Contacts have firstName and lastName, not name. String values use double quotes (firstName = "Ada"); single quotes are accepted and rewritten.

  • cw_get_contact — Get a contact by ID

  • cw_create_contact — Create a new contact. Communication type names vary per tenant, so the email and phone types are resolved from GET /company/communicationTypes (emailFlag / phoneFlag, cached for 10 minutes per connection) instead of assuming "Email" / "Direct". Optional emailTypeId, emailTypeName, phoneTypeId, phoneTypeName override the lookup (an id wins over a name; an unknown name lists the available types).

  • cw_list_communication_types — List the tenant's communication types (GET /company/communicationTypes) to find the ids for cw_create_contact and cw_update_contact

Topics
ai-toolsclaudeconnectwise-managemcpmcp-servermodel-context-protocolmspmsp-mcptypescriptwyre-technology
Preguntas frecuentes

Lo que la gente pregunta sobre connectwise-manage-mcp

¿Qué es WYRE-AI/connectwise-manage-mcp?

WYRE-AI/connectwise-manage-mcp es mcp servers para el ecosistema de Claude AI. MCP server for ConnectWise Manage (PSA) — tickets, companies, contacts, projects, and time entry tools for AI assistants Tiene 28 estrellas en GitHub y su última actualización registrada es del 2026-10-22.

¿Cómo se instala connectwise-manage-mcp?

Puedes instalar connectwise-manage-mcp clonando el repositorio (https://github.com/WYRE-AI/connectwise-manage-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar WYRE-AI/connectwise-manage-mcp?

Nuestro agente de seguridad ha analizado WYRE-AI/connectwise-manage-mcp y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene WYRE-AI/connectwise-manage-mcp?

WYRE-AI/connectwise-manage-mcp es mantenido por WYRE-AI. La última actividad registrada en GitHub es del 2026-10-22, con 9 issues abiertos.

¿Hay alternativas a connectwise-manage-mcp?

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.