A read-only Model Context Protocol (MCP) server for ConnectWise Manage — query tickets, companies, agreements, time entries, projects, and more from any MCP-compatible AI client.
First-time setup guide
·
Report Bug
·
Request Feature
Table of Contents
This MCP server exposes ConnectWise Manage data to AI assistants and automation pipelines through the Model Context Protocol. It is read-only and reporting-focused — no records are created, modified, or deleted.
Key design decisions:
- OAuth 2.1 authentication — users sign in through your IdP (Entra ID, Google, etc.). The MCP server validates a Bearer JWT on every
/mcprequest. CW API credentials live server-side, never in URLs. - Admin dashboard at
/admin— setup wizard, settings, audit log, users + permissions, layered context docs, board aliases, company exclusions, service-account API keys, health, backups. Postgres-backed. - Per-user tool filtering — each user's tool surface is filtered by their CW security role; admins see everything.
- Stateless Streamable HTTP transport — compatible with any MCP client that supports HTTP.
- Docker + Cloudflare Tunnel — ship it anywhere without opening inbound firewall ports.
Built with: TypeScript, Node.js, Express, Postgres, Docker, Cloudflare Tunnel.
101 tools — 89 single-endpoint CW tools, 10 composite reporting tools, plus 2 utility tools (describe_entity, get_context).
| Module | Tools |
|---|---|
| Service | get_service_tickets, get_service_ticket_by_id, get_service_ticket_notes, get_service_ticket_time_entries, get_service_ticket_tasks, get_service_ticket_count, get_service_ticket_configurations, get_service_ticket_documents, get_service_ticket_products, get_service_ticket_links, get_service_boards, get_service_board_statuses, get_service_board_types, get_service_board_subtypes, get_service_board_teams, get_service_priorities, get_service_slas, get_service_impacts, get_service_sources, get_service_severities, get_service_teams |
| Knowledge Base | get_knowledge_base_articles, get_knowledge_base_article_by_id, get_knowledge_base_categories, get_knowledge_base_subcategories |
| Surveys | get_service_surveys, get_service_survey_questions, get_service_survey_results |
| Company | get_companies, get_company_by_id, get_company_sites, get_company_notes, get_contacts, get_contact_by_id, get_contact_communications, get_contact_notes, get_company_configurations, get_company_configuration_by_id |
| Finance | get_agreements, get_agreement_by_id, get_agreement_additions, get_agreement_adjustments, get_agreement_sites, get_agreement_recap, get_agreement_types |
| Time | get_time_entries, get_time_entry_by_id, get_time_sheets, get_time_sheet_by_id, get_work_roles, get_work_types, get_charge_codes |
| Project | get_projects, get_project_by_id, get_project_phases, get_project_tickets, get_project_team_members, get_project_notes, get_project_statuses |
| System | get_members, get_member_by_id, get_member_skills, get_departments, get_audit_trail, get_system_info |
| Schedule | get_schedule_entries, get_schedule_entry_by_id, get_schedule_calendars |
| Sales | get_opportunities, get_opportunity_by_id, get_opportunity_forecast, get_opportunity_notes, get_sales_activities |
| Expense | get_expense_entries, get_expense_entry_by_id, get_expense_types, get_expense_reports |
| Procurement | get_products, get_product_by_id, get_catalog_items, get_catalog_item_by_id, get_purchase_orders, get_purchase_order_by_id, get_rma_actions, get_rma_action_by_id |
| Marketing | get_marketing_campaigns, get_marketing_groups |
| Webhook | get_callbacks, get_callback_by_id |
All list tools support ConnectWise's full query syntax: conditions, childConditions, customFieldConditions, orderBy, fields, page, pageSize, pageId.
| Tool | Description |
|---|---|
describe_entity |
Returns the field list, types, and example conditions for a ConnectWise entity. Call before list tools when unsure what fields exist or how to filter. |
get_context |
Returns the merged org-specific context for the calling user — boards, team, business rules, query patterns — composed from the global, role, and user context layers. Call once at the start of a session. |
These combine multiple API calls into a single response for MSP reporting workflows:
| Tool | Description |
|---|---|
get_ticket_summary |
Complete ticket view — details, notes, time entries, tasks. Includes computed totals. |
get_member_utilization |
Tech utilization — logged hours vs scheduled hours for a date range. |
get_agreement_profitability |
Agreement financials — additions, adjustments, billing recap. |
get_board_overview |
Service board dashboard — details, statuses, open ticket counts per status. |
get_tech_skills_report |
Tech skills assessment — profile, skills, recent tickets, time entries. |
get_recurring_issues_report |
Recurring issue analysis — grouped by type/subType, ranked by frequency. |
get_ticket_tone_analysis |
Tone/sentiment data — ticket + notes with metadata for AI sentiment analysis. |
get_common_issues_by_company |
Per-company issue patterns — open vs closed ratios, frequency ranking. |
get_helpdesk_team_report |
Team performance — per-member stats plus top issue types. |
get_sla_compliance_report |
SLA response/resolution times by priority vs SLA targets. |
Composite tools return partial results with an _errors array if any sub-call fails — never crash on a single API error.
10 MCP prompts provide pre-built AI workflows for common MSP tasks.
| Prompt | Args | Description |
|---|---|---|
daily_standup |
— | Morning briefing: open tickets, SLA risks, time logging, action items. |
escalation_check |
— | Escalation checklist: SLA breaches, unassigned high-priority, aging tickets. |
helpdesk_manager_weekly |
— | Weekly report: team performance, ticket metrics, SLA compliance, recurring issues. |
| Prompt | Args | Description |
|---|---|---|
recurring_issue_analysis |
boardName (optional) |
Pattern detection, KB gaps, root cause categorization, prevention recommendations. |
ticket_tone_review |
ticketId |
Sentiment analysis: tone timeline, escalation risk level, recommended actions. |
common_issues_by_client |
companyIdentifier |
Per-client patterns: anomaly detection, one-off vs systemic, prevention. |
sla_compliance_review |
— | SLA review: compliance rates, worst breaches, board comparison, improvements. |
| Prompt | Args | Description |
|---|---|---|
client_review |
companyIdentifier |
Client health: open tickets, agreements, recent engagement, recommendations. |
tech_productivity |
memberIdentifier |
Productivity report: utilization, throughput, resolution time, skills coverage. |
tech_skills_report |
memberIdentifier |
Skills assessment: inventory, work profile, gaps, training recommendations. |
See docs/setup.md for the full first-time setup guide. It walks through:
- Prerequisites (Docker, ConnectWise admin access, OAuth IdP, Cloudflare Tunnel)
- Generating ConnectWise API credentials + Client ID
- Registering an OAuth app (Microsoft Entra ID walkthrough)
- Configuring the Cloudflare Tunnel
- Cloning the repo + filling in
.env - Running
docker compose up - Completing the first-run setup wizard at
/admin/setup - Connecting Claude.ai or another MCP client
- Troubleshooting common issues
If you already know the moving parts, the short version is:
git clone https://github.com/npab19/cw-manage-mcp.git
cd cw-manage-mcp
cp .env.example .env
# edit .env — fill in CW credentials, POSTGRES_PASSWORD, ADMIN_EMAILS, OAUTH_*, etc.
docker compose up --build -d
docker compose logs cw-manage-mcp | tail -30 # find the bootstrap URL
# Visit the bootstrap URL printed in the logs to complete setupA pre-built image is published to GitHub Container Registry on every push to master:
docker pull ghcr.io/npab19/cw-manage-mcp:latest- claude.ai → Profile → Settings → Integrations → Add integration
- Paste the MCP URL — no query parameters:
https://cw-mcp.yourdomain.com/mcp - Save. Claude walks the OAuth flow against your IdP, then lists the tools your account is granted.
{
"tool": "get_service_tickets",
"arguments": {
"conditions": "board/name=\"Service Desk\" and closedFlag=false",
"orderBy": "lastUpdated desc",
"pageSize": 50
}
}{
"tool": "get_time_entries",
"arguments": {
"conditions": "member/identifier=\"jsmith\" and timeStart>[2026-05-01T00:00:00Z]",
"orderBy": "timeStart desc"
}
}npx @modelcontextprotocol/inspector "https://cw-mcp.yourdomain.com/mcp"The Inspector walks the OAuth flow on first connect.
- Read-only tools for core CW modules (service, company, finance, time, project, system, schedule, sales)
- Expense, Procurement, Marketing, Webhook tool modules
- Composite reporting tools for MSP workflows
- MCP prompts library
- Docker + Cloudflare Tunnel deployment
- OAuth 2.1 (Resource Server + Authorization Server proxy)
- Admin dashboard with setup wizard, settings, MCP audit log
- Auto-publish Docker image to GHCR
- CW user import + permission mirroring (per-role tool allow-lists)
- Layered context documents (global / per-role / per-user) as MCP resources +
get_contexttool - Managed content (board aliases, company exclusions)
- Service-account API keys for CI / n8n / custom integrations
- Caching, per-user rate limiting, nightly Postgres backups, admin Health page
See open issues for proposed features and known issues.
Contributions welcome. Fork, branch, commit, PR:
- Fork the project
git checkout -b feature/your-featuregit commit -m 'Add your feature'git push origin feature/your-feature- Open a Pull Request
MIT. See LICENSE.
- Model Context Protocol
- ConnectWise Manage REST API
- Best-README-Template
- Img Shields
- Cloudflare Tunnel