MCP ConnectWise Manage
Flagler-County-BoCC/mcp-connectwise-manage
Integração IA com ConnectWise Manage — 25 ferramentas tipadas para service desk
Ver no GitHubServidor MCP que integra Claude, Cursor e outros assistentes de IA com ConnectWise Manage, expondo 25 ferramentas tipadas para gerenciar service desk, tickets, tempo, acordos, projetos e vendas. Funciona via stdio com autenticação segura e validação de escrita.
Instalação
npx convez-ai Flagler-County-BoCC/mcp-connectwise-manage1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automatizar operações de service desk e gestão de tickets via IA
- Consultar e atualizar dados de projetos, contratos e vendas em tempo real
- Integrar fluxos de trabalho ConnectWise em agentes Claude e Cursor
Veredito

MCP bem estruturado para ambientes que usam ConnectWise Manage. Requer configuração inicial sólida (credenciais API, OpenAPI spec) mas oferece acesso tipo-seguro e proteções contra mutações acidentais. Ideal para equipes técnicas que querem automatizar service desk via IA.
README
A tradução para o português deste README ainda está na fila.
mcp-connectwise-manage
Model Context Protocol (MCP) stdio server for ConnectWise Manage — exposes service desk, time, agreements, companies, projects, sales, and setup operations as typed MCP tools for AI agents.
Table of Contents
- Overview
- Requirements
- Installation
- Configuration
- MCP Configuration
- Tool Reference
- Testing
- Project Structure
- Contributing
- License
Overview
mcp-connectwise-manage bridges AI assistants (Claude, Cursor, and other MCP-compatible clients) with ConnectWise Manage's REST API. It exposes 25 typed MCP tools across 7 modules, with built-in write safeguards, profile-based access control, and structured logging — all communicating over stdin/stdout using the Model Context Protocol.
Key design decisions:
- Stdio-only transport — no HTTP server, no open ports.
- Write safeguards — all mutating tools require
confirm=trueordryRun=true. - Profile filtering — tool exposure is scoped per
CW_ACTIVE_PROFILEwithout restarting. - Type-safe throughout — Zod validates every tool input; TypeScript strict mode enforced.
Requirements
- Node.js >= 22.0.0
- A ConnectWise Manage instance with API access
- A ConnectWise API Member with appropriate permissions
- A ConnectWise
clientId(register at developer.connectwise.com)
Installation
git clone https://github.com/Flagler-County-BoCC/mcp-connectwise-manage.git
cd mcp-connectwise-manage
npm install
cp .env.example .env
# Edit .env with your ConnectWise credentials
npm run build
Configuration
All configuration is via environment variables. Copy .env.example to .env and fill in the required values.
See docs/ENVIRONMENT.md for the full variable reference.
Minimum required variables:
| Variable | Description |
|---|---|
CW_server | ConnectWise server hostname (e.g. na.myconnectwise.net) |
CW_company | ConnectWise company identifier |
CW_clientId | API client ID from developer.connectwise.com |
CW_pub | API public key |
CW_priv | API private key |
SPEC_PATH | Absolute path to the ConnectWise OpenAPI JSON spec |
MCP Configuration
Cursor (.cursor/mcp.json)
{
"mcpServers": {
"cw-manage": {
"command": "node",
"args": ["/absolute/path/to/mcp-connectwise-manage/dist/stdio.js"],
"env": {
"NODE_ENV": "production",
"LOG_LEVEL": "info",
"CW_server": "na.myconnectwise.net",
"CW_company": "yourcompany",
"CW_clientId": "your-client-id",
"CW_pub": "your-public-key",
"CW_priv": "your-private-key",
"SPEC_PATH": "/absolute/path/to/connectwise-openapi.json"
}
}
}
}
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"cw-manage": {
"command": "node",
"args": ["/absolute/path/to/mcp-connectwise-manage/dist/stdio.js"],
"env": {
"NODE_ENV": "production",
"CW_server": "na.myconnectwise.net",
"CW_company": "yourcompany",
"CW_clientId": "your-client-id",
"CW_pub": "your-public-key",
"CW_priv": "your-private-key",
"SPEC_PATH": "/absolute/path/to/connectwise-openapi.json"
}
}
}
}
Automated setup (Claude Code / Claude Desktop)
npm run setup
This builds the project and registers it in Claude Desktop and Claude Code (~/.claude.json), and installs slash commands to ~/.claude/commands/.
To remove all registrations:
npm run uninstall
Tool Reference
See docs/API.md for the full tool reference with input/output schemas and examples.
Available tool modules:
| Prefix | Module | Tools |
|---|---|---|
agr- | Agreements | list-agreements, get-agreement, list-additions |
co- | Companies | list-companies, get-company, list-contacts |
prj- | Projects | list-projects, get-project, list-phases, list-tickets |
sal- | Sales | list-opportunities, get-opportunity, list-quotes |
svc- | Service Desk | list-tickets, get-ticket, list-boards, list-statuses, list-priorities, list-impacts, list-members |
setup- | Setup | list-tables, list-locations, list-departments, list-work-types, list-work-roles |
time- | Time | list-entries, list-periods, create-entry, update-entry |
Testing
# Run all tests
npm test
# Run with coverage report
npm run test:coverage
# Run integration tests only
npm run test:integration
# Type-check without building
npm run typecheck
Unit tests mock the HTTP layer — no real ConnectWise credentials are required to run tests.
Project Structure
src/
├── config/ # Zod env schema + typed config object
├── errors/ # AppError hierarchy (Forbidden, NotFound, Validation, ExternalService)
├── lib/ # Shared utilities (http-client, logger, container, profile, validate)
├── tools/ # One directory per module
│ └── <module>/
│ ├── <module>.schema.ts # Zod input schemas
│ ├── <module>.service.ts # Business logic + CW API calls
│ ├── <module>.tool.ts # MCP tool registrations
│ └── <module>.types.ts # TypeScript response types
├── server.ts # createServer() — tool registry, profile gating
└── stdio.ts # Entry point — transport, signals, startup log
scripts/
├── setup.ts # Register in Claude Desktop + Claude Code
└── uninstall.ts # Remove registrations
templates/
└── .claude/commands/ # Slash command templates
tests/
├── integration/ # McpServer registration smoke tests
└── setup.ts # Test environment bootstrap
Contributing
See CONTRIBUTING.md.