@pulsatrix/connectwise-mcp

Pulsatrix - ConnectWise MCP Server for LLM Agents & MSP AI

Hand the busywork to AI. Keep the final call.

Self-hosted Model Context Protocol (MCP) for ConnectWise MSPs. This MCP is the AI gateway between your LLM (Claude, GPT-class APIs, Qwen and other open local models via LM Studio, Grok-class clients where you wire MCP, and more) and the stack that runs your desk: ConnectWise Manage (PSA), ConnectWise RMM (Asio), ScreenConnect, Sell / CPQ, Axcient x360Recover, SentinelOne, plus optional Apple Mail.

Not an unsupervised autonomous IT engineer. Not a cloud SaaS that becomes a second tenant of your PSA. Not a thin OpenAPI-to-MCP dump with a wall of logos. AI proposes. Tool calling runs through policy. You approve what matters.

The product will be available for install directly from npm when the private beta ends.

Our story

AI was supposed to buy you hours back.

At first,

You try Microsoft Copilot or N8n
You move to ChatGPT / GPT. Then Claude (Opus / Sonnet).
You try local LLMs — Qwen, Llama-class, whatever reddit is trending.
You wire an automation. You spin up an AI agent with function calling / tool calling.
You show the team. Everyone sees agentic AI potential.

Then reality boards the plane

The question nobody budgeted	What it really is
Who maintains the agents and MCP configs?	Platform work
Who explains LLM limits and hallucinations?	Trust & training
Who chooses Claude vs GPT vs local Qwen?	Model architecture
Who owns API keys, PII, client data, cost?	AI governance
Who answers when the agent breaks at 4:55 p.m.?	You

Your service desk, time entry, and client work did not disappear.

The truth about LLM ROI

Large language models and AI agents save time only when they are structured.

Without governance, process, and a clear control plane for where the model may call tools, “AI” is a new layer of work: prompt debt, connector debt, security debt, etc…

Why Pulsatrix

We built Pulsatrix inside a real ConnectWise MSP because that story was ours.

We didn’t need a chatbot. We are not looking into becoming humainless with “autonomous tech” you cannot fully own or trust. We don’t want fifty shallow MCP integrations for all tool that possibily exists.

We focus on the stack that we believe is optimal and used by most of the MSP. Without reinventing the wheel. Why not simply use a very good MCP with your existing subscriptions or your local hardware with deep tool-calling surface on ConnectWise, human-in-the-loop customizable.

What Pulsatrix is (MCP + LLM + MSP)

Pulsatrix is a self-hosted MCP server / AI gateway:

1. Your MCP client (Claude Code, Claude Desktop, LM Studio, Cursor, …) talks MCP.
2. Your LLM does reasoning and tool selection (function calling).
3. The Pulsatrix host discovers tools, applies risk policy, runs approval, holds credentials, dispatches to domain modules.
4. ConnectWise and adjacent systems execute only what policy allows.

  LLM + MCP client                    ConnectWise-centered stack
  Claude · GPT APIs · Qwen/local      PSA · RMM · SC · CPQ · x360 · S1 · …
  Cursor · Codex · VS Code · …                  ▲
         │  Model Context Protocol              │
         ▼                                      │
   ┌────────────────────────────────────────────┴─┐
   │              PULSATRIX (MCP host)              │
   │  tools/list · risk class · human approval      │
   │  keychain custody · signed modules · license   │
   └────────────────────────────────────────────────┘

We do not sell tokens. We do not mark up Anthropic, OpenAI, Google, xAI, or your local GPU. BYOM — bring your own model.

Works with your AI stack

MCP clients with first-class connect adapters

Wired in the host (detect / register / disconnect — product code, not marketing guesswork):

MCP client	Role
Claude Desktop	Anthropic desktop app — smoothest path for many MSPs
Claude Code	CLI / agentic coding & ops workflows
LM Studio / Bionic / oMLX, etc	Local LLM host — Qwen, Llama-class, and other GGUF/MLX models you load
Cursor	AI IDE with MCP tool calling
Copilot	Microsoft client
VS Code	MCP via editor integration
Codex CLI	OpenAI Codex-style CLI MCP (TOML config adapter)

Any other MCP-compatible client that can spawn a local stdio MCP server can point at Pulsatrix with a standard config snippet. Remote MCP / OAuth connector paths exist for advanced setups (e.g. cloud clients reaching a local host); primary private-beta path is local stdio.

Models & providers (bring your own API or Subscriptions)

Class	Honest guidance
Claude Mythos (Fable), Opus / Sonnet (Anthropic)	Best overall results on complex multi-step MSP tool use
GPT-class / Codex (OpenAI APIs via your client)	Supported as your model behind an MCP client — we are not OpenAI
Gemini (Google)	Use via any MCP client that hosts Gemini; not a separate Pulsatrix model SKU
Grok (xAI)	Usable where your client exposes MCP + a Grok-backed model; advanced remote connector dogfood documented for operators
Qwen and other open weights	Run locally (e.g. LM Studio); size plugin load so the tool surface fits ~30B-class attention budgets
Copilot-era experiments	Many teams start there; Pulsatrix is the control plane when you outgrow tab chaos

Operator-owned tool budget: small local LLMs degrade when tools/list is huge. Load fewer domain modules for Qwen-class locals; load more for Claude-class frontier models. That is a product principle, not a hidden cap.

Mission & principles

Make LLM agents useful on the systems that run an MSP without turning one operator into an unpaid AI department, and without unsupervised authority over client infrastructure.

Principle	Meaning
Structure before magic	Agents need policy, not vibes
Depth over sprawl	ConnectWise stack first
Propose ≠ execute	Tool calls that change state cross your gates
Local by default	Operational data stays on your machine
Fail closed on trust	Unverified modules do not load
BYOM	Claude, GPT, Qwen, Grok-class — your contract with the model vendor

Product surface

Independently loadable domain modules (~190 model-callable actions at full entitlement, plus host utilities for status, discovery, and safe calculation). Exact catalogs ship in entitled installs.

Domain	MSP outcomes
PSA ConnectWise Manage	Tickets, dispatch, time, companies, agreements, projects, sales, finance-adjacent ops
RMM ConnectWise Asio	Fleet inventory/posture, patch & vulnerability views, controlled automation paths
ScreenConnect	Sessions, endpoints, operator-approved remote command paths
CPQ ConnectWise Sell	Quotes, portfolio, recurring revenue views
Backup Axcient x360Recover	Fleet backup health, jobs, recovery evidence
SentinelOne EDR/MDR	Threat/agent posture, investigation, gated response
Envoy (optional)	Apple Mail triage & drafting beside the same MSP workflows

AI safety & governance (human-in-the-loop)

This is how Pulsatrix differs from “paste API keys into an agent and hope.”

Control	What it means for LLM tool calling
Risk classes	Every exposed tool is classified (read / write / intense / never exposed)
Host choke-point	Policy runs in the host before vendor execution
Human approval	Sensitive writes wait on a person
Biometric option	Touch ID / Windows Hello for highest-risk actions you designate
No self-approval	The model cannot loosen policy via a tool
Credential custody	OS keychain path — not secrets sprayed through every agent config
Integrity + entitlement	Modules checked before they join tools/list

Never exposed capabilities are not “soft hidden.” They are not offered to the LLM at all.

Local replica & skills

Capability	Honest scope
Local read-through replica	Slow-moving PSA/RMM reference data; never authoritative for hot truth; never silent write targeting; data stays local
Skills	Taught multi-step MSP job recipes for agent clients that load skills; do not bypass gates; discovery catalog remains the universal fallback

Local-first, Law 25, GDPR

• Execution on your machine
• Operational payloads do not ship to us as product telemetry content
• Optional anonymous product signals (what actions work / misbehave) — opt-out; never tickets/prompts/client identity
• What you send to Anthropic / OpenAI / Google / xAI is your clientprovider relationship
• Or keep inference fully local (LM Studio + open models)

Private beta

Private paid beta. Application-based access. Pricing shared with approved participants.

Apply: https://pulsatrix.ca

npm i @pulsatrix/connectwise-mcp

This npm package is the public product surface (docs + positioning). Runtime binaries ship through approved beta channels. Production MCP control planes are not casual demos — same standard we ask of AI agents on client systems.

FAQ

Is Pulsatrix a ConnectWise MCP server?

Yes. It is a self-hosted MCP host with ConnectWise-centered domain modules (Manage, RMM/Asio, ScreenConnect, Sell, plus x360 and SentinelOne). More coming soon with ConnectWise focus ONLY.

Does it work with Claude / Claude Code / Claude Desktop?

Yes. Claude Desktop and Claude Code have first-class connect adapters. Claude Opus/Sonnet generally yield the strongest multi-step tool-calling results.

Can I use a local LLM (Qwen, LM Studio)?

Yes. BYOM. LM Studio is a wired MCP client. Run Qwen or other local models there; load fewer plugins if the model’s tool-calling budget is small (~30B-class guidance).

Does it work with Cursor, VS Code, Windsurf, Codex?

Yes , those clients are in the product’s connect adapter set. Other MCP clients can use a generic stdio snippet.

Is this autonomous AI that replaces technicians?

No. It is agentic tool use with human-in-the-loop governance. The AI proposes; risk-bearing writes wait on your policy. We want to empower techcian.

Do you resell LLM tokens?

No. Point at Anthropic, OpenAI, Google, xAI, or local inference, your accounts, your spend.

Is client PSA data sent to Pulsatrix cloud?

Never. Operational ticket/company/financial payloads are not our product data path. Local-first execution; license/entitlement traffic is separate. See product docs at beta onboarding.

How is this different from “just expose the ConnectWise API to an LLM”?

Depth over sprawl: job-shaped tools, risk classes, host enforcement, optional biometric gates, module integrity not a raw OpenAPI mirror that burns context and hallucinate endpoints like other solutions out there.

Links

• Product & beta — pulsatrix.ca
• npm — @pulsatrix/connectwise-mcp

---

Built by practitioners who run MSP operations. Independent — not affiliated with ConnectWise, LLC.
ConnectWise, Manage, Asio, Quosal Sell, and ScreenConnect are trademarks of ConnectWise, LLC. SentinelOne, Axcient, Anthropic, OpenAI, Google, xAI, and other marks belong to their owners — used for descriptive interoperability only.