For AI agents: every page on this site is listed at /llms.txt, and this page is also available as Markdown.

MCP servers for MSPs in 2026: how the options compare

Last checked November 2, 2026. Disclosure: Servosity makes msp-skills and wrote this page. Product facts link to the company’s own pages. Where we say we found nothing, that is a dated web and GitHub search, not a guarantee. Prices and counts change fast, so check the linked page before you buy. Spot a mistake? Tell us on GitHub and we will fix it.

An MCP server is the connector that lets an AI app like Claude, ChatGPT or Copilot use one of your tools, through the open Model Context Protocol (MCP). MSPs now have four kinds to pick from: free open-source servers you run yourself, hosted gateways that hold your API keys and give your whole team one web address, Thread’s server, built around its own service desk, and servers vendors build for their own products. The real choice is which AI app you use and who holds your keys.

The comparison at a glance

Option Price, as published Where your API keys live Coverage What has been checked
msp-skills (by Servosity) Free, Apache-2.0 (README) Your machine: an environment variable or your AI app’s config file, or the macOS Keychain / Windows Credential Manager if you use connect-tool 84 connectors (catalog) 19 confirmed on a live tenant, 65 awaiting live verification (receipts wall)
WYRE self-run servers 46 of its 90 -mcp repositories, including autotask-mcp, connectwise-manage-mcp and halopsa-mcp, are free under Apache-2.0; GitHub shows no standard license for the other 44, so their terms are unclear Your machine or your own server, as environment variables (autotask-mcp) 90 public -mcp repositories (WYRE-AI on GitHub) The autotask-mcp README shows build and coverage badges and claims 80%+ test coverage; we did not find a list of which servers have been run against a live tenant
WYRE Conduit (hosted) $39 per seat a month, 2 AI-agent seats free, 14-day trial (pricing) WYRE’s servers in Microsoft Azure, encrypted per record (security) 155 vendor connectors (pricing) Integrations labeled live or beta (blog); not SOC 2 certified, “preparing for SOC 2 Type 2” (security)
StackJack (hosted) Free tier on every connector (100 calls a month); Pro $19 to $99 and Business $29 to $199 per connector a month (about) StackJack’s Azure Key Vault (security) 114 connectors (home) SOC 2 Type II report issued, shared under NDA (security)
MSPbots Connector (hosted) “Free to use” (MSPbots on GitHub) MSPbots’ service, “encrypted per record” (same page) “150+ connectors” (same page) MSPbots reports a completed SOC 2 Type II audit (data security)
Thread MCP server Needs a Thread plan: AI Essentials $19 or AI Pro $34 per managed customer a month (pricing); without AI Pro the server offers seven read-only tools (guide) No key: you sign in with your Thread account (guide) Thread’s service desk, plus NinjaOne, ImmyBot, TimeZest, IT Glue and Hudu tools once those integrations are set up (guide) “Generally available to all partners” (guide)
Vendors’ own servers Varies: Syncro includes it in every plan, Kaseya says its servers are free, Liongard’s needs its own subscription (links below) Usually your vendor sign-in; some take an API key What that vendor’s platform holds: one product for most, several for platforms such as ScalePad, N-able, Liongard and Rewst Built by the vendor; several are still beta, preview or early access

Local does not mean nothing leaves your machine. Whichever option you pick, your AI app reads the results the server returns (msp-skills README). If that app runs on a cloud model, as Claude, ChatGPT and Copilot do, those results go to the model’s provider.

When a hosted gateway is the better pick

When a vendor’s own server is the better pick

If you need one product and its vendor ships a server, start there. It comes from the company that owns the API, and many let you sign in with the account you already have instead of handling a key. Support varies: CrowdStrike and SentinelOne each say theirs is a community project they maintain, not an official product (CrowdStrike, SentinelOne). The catch is coverage: each one reaches what that vendor’s platform can see. Some see a lot: Liongard answers questions across the systems it inspects, and Rewst runs workflows through its integrations. Anything outside that platform needs another connector.

When msp-skills is the better pick

Where msp-skills is weaker

  1. Most connectors are unproven on a real tenant. 19 of 84 have been confirmed live; 5 of those 19 were confirmed by Servosity on its own tenants. 7 were confirmed on an earlier release than today’s, and the other 12 did not record a version, so no receipt yet proves today’s release (receipts wall). The other 65 pass our automated build and documentation checks, which cannot tell us what a live tenant does (CONTRIBUTING.md).
  2. Web-based AI apps are hard. ChatGPT on the web and Microsoft 365 Copilot need the setup described above.
  3. Keys sit in plain text by default. The manual setup in our install guides puts your API secret in your AI app’s config file (HaloPSA install guide). connect-tool can store it in the macOS Keychain or Windows Credential Manager instead, but each person still holds their own keys.
  4. No team controls. There is no hosted dashboard, so no single sign-on, no central audit log and no one switch to revoke a tech’s access. Your strongest control is scoping the API key inside your own vendor tenant (are MCP servers safe?).
  5. The local copy is not encrypted and does not expire. You delete its folders by hand to remove it (SECURITY.md).
  6. Some connectors can write without asking. 53 connectors expose a tool that can call any endpoint the connector covers, including writes where the API has them, with no confirmation step; 17 support a read-only switch (SECURITY.md).
  7. Fewer connectors. 84, against 114 for StackJack, 155 for Conduit and “150+” for MSPbots Connector.

Vendors’ own MCP servers, as of November 2, 2026

Checked on each vendor’s own site or GitHub. “Your instance” means the server runs inside the copy of the product you already use.

About Thread’s skills and MCP server

Thread is an AI service desk, not a connector library. Its MCP server lets Claude, ChatGPT, Claude Code or Cursor work in Thread itself: search tickets, manage contacts and run write actions (guide). What each person sees follows their Thread permissions and plan: without AI Pro it is seven read-only tools, and the NinjaOne, ImmyBot, TimeZest, IT Glue and Hudu tools appear on Agentic plans once those integrations are set up (same guide). Its public GitHub skill library is a set of prompts for Thread’s own AI, each capped at 3,000 characters (GitHub). If you run Thread, its server covers Thread and those integrations; the rest of your stack needs one of the other options.

Try an msp-skills connector

These are the 19 connectors we recommend today, because each one has been confirmed against a live tenant: Acronis, Avanan, Axcient, CIPP, Cove, DataGate, Datto BCDR, HaloPSA, HubSpot, Hudu, Huntress, ImmyBot, NinjaOne, QuickBooks, SentinelOne, SuperOps, ThreatLocker, WordPress and Zammad. Servosity confirmed HaloPSA, HubSpot, QuickBooks, WordPress and Zammad on its own tenants; outside MSPs confirmed the rest (receipts wall).

Each connector’s page has setup steps for your AI app. Or run the installer yourself. On macOS or Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/servosity/msp-skills/main/skills/halopsa/install.sh)

On Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/servosity/msp-skills/main/skills/halopsa/install.ps1 | iex

Swap halopsa for the connector you want. Before you connect, create the API key in your own tenant with just the permissions you want the AI to have. Ran one of the other 65 against your tenant? Tell us it worked and the badge flips.

FAQ

Which MCP server should an MSP use in 2026?

It depends on which AI app your team uses and who you want holding your API keys. ChatGPT on the web or Microsoft 365 Copilot, or a need for team sign-in and a central audit log, points to a hosted gateway such as WYRE’s Conduit, StackJack or MSPbots Connector; check that your AI app is on the gateway’s setup list. One product with a vendor-built server points to that server. A local AI app such as Claude Desktop or Claude Code, no budget, and keys kept on your own machine point to msp-skills or WYRE’s open-source servers.

Is there a free MCP server for ConnectWise, Autotask or HaloPSA?

Yes. msp-skills and WYRE both publish free, open-source servers for all three that you run yourself, and StackJack has a free tier of 100 calls a month per connector. HaloPSA’s own server runs on your Halo instance, and Kaseya says its early-access Autotask server is free. Of the msp-skills three, HaloPSA has been confirmed on a live tenant; ConnectWise PSA and Autotask are awaiting live verification.

Where do my API keys live with a hosted MCP gateway?

On the gateway company’s servers. Conduit encrypts each one in Microsoft Azure and says an operator with production access could in principle decrypt them (security). StackJack keeps them in Azure Key Vault (security). With msp-skills they stay on your own machine.

Can I use msp-skills with ChatGPT?

In the ChatGPT desktop app, it should work: the app can run local MCP servers, which is how msp-skills runs (OpenAI), but we have not yet confirmed a connector in it. ChatGPT on the web needs a remote server, and our SECURITY.md says not to run a connector that way until it is reprinted; 75 of the 84 install guides still carry that pause note. If your team works in ChatGPT on the web, a hosted gateway or your vendor’s own hosted server is the better pick.

Who makes msp-skills?

Servosity Inc., which also wrote this comparison. msp-skills is free and Apache-2.0 licensed, and anyone can contribute a connector or a fix (CONTRIBUTING.md).

Read this next