MCP servers for your MSP stack
16 hosted MCP servers, one endpoint. Connect the AI you already use to ConnectWise, Microsoft 365, Google Workspace, Meraki, Pax8, Xero and the rest of your stack — read-only by default, scoped per person by your admin, and every answer traced to the tool call that produced it. Nothing to install, nothing to keep running.
https://www.mspstuff.io/mcp
What is an MCP server?
The Model Context Protocol is an open standard that lets an AI assistant call a system's tools. An MCP server exposes one system — a PSA, an RMM, a tenant, a ledger — as a set of tools the assistant can call with your permission.
Without one, an assistant can only talk about your systems from memory. With one, it reads the live record and shows you which call produced each figure.
Most published servers cover a single product, so a ten-platform stack means ten connectors to add and ten sets of credentials to manage. MSPStuff hosts one scoped server for the whole stack instead: your admin decides what each person may reach, platform by platform and domain by domain.
Every server on the board
Each one lists the skills it carries, what it can read, the limits that apply and what connecting requires.
- ConnectWise ScreenConnect MCP serverWho connected to what, when — your remote-access fleet, answerable.
- ConnectWise Automate MCP serverEvery machine, patch, monitor, and script — your Automate fleet, answerable.
- ConnectWise PSA MCP serverTickets, agreements and the pipeline — answerable across every board.
- ConnectWise Asio MCP serverEndpoints, policies, and the automation around them — your Asio fleet, answerable.
- Pax8 MCP serverYour distributor book — subscriptions, seats, and spend, answerable.
- Google Workspace MCP serverEvery client domain — people, licenses, devices, and the admin record — in one conversation.
- Microsoft 365 MCP serverAsk once across every tenant — identity, licensing, devices, and security posture.
- Cisco Meraki MCP serverEvery network, uplink and port — answerable, read-only today.
- Webroot MCP serverEvery site under the GSM — protection, threats, DNS and agents — read and never written.
- NinjaOne MCP serverYour whole RMM — and its ticketing — answerable in plain English.
- ImmyBot MCP serverDeployment automation you can interrogate.
- Axcient x360Recover MCP serverYour whole BCDR footprint, answerable in plain English.
- Xero MCP serverYour books, answerable: invoices, aging, cash and financial performance.
- Ninety MCP serverYour EOS operating system — rocks, issues, to-dos and the scorecard, answerable in plain English.
- SentinelOne MCP serverEvery endpoint SentinelOne protects — health, threats, policy — answerable in plain English.
- Trend Vision One MCP serverEvery client Trend protects — status lights, devices, detections — answerable in plain English.
Questions
- What is an MCP server?
- The Model Context Protocol (MCP) is an open standard that lets an AI assistant call a system's tools. An MCP server exposes one system's data and actions as tools the AI can call with your permission. Without one, an assistant can only talk about your systems; with one, it can read them.
- Do I have to run the server myself?
- No. MSPStuff hosts and operates every server listed here. There is no agent to install, no container to keep running and no API keys handed to technicians. Your data stays yours; the server and the software running it are ours.
- How is this different from a single-product MCP server?
- Most published servers cover one product, so a ten-platform stack means ten connectors and ten sets of credentials. Switchboard is one scoped endpoint for every platform your company connected, and your admin sets what each person may reach, per platform and per domain.
- Is access read-only?
- Yes, today. Any change a platform could make is held back — refused by our server before anything reaches the platform — until a person switches it on, and nothing is switched on today. External AI clients read your platforms; in MSPStuff they can also run and create reports when the role allows it.
- Can I limit what each person's AI client can do?
- Yes. Each person's role has a column for their AI client, and it can never hold more than the role allows in MSPStuff. Take a permission away in MSPStuff and the AI client loses it too. The roles and what each one holds are listed on the roles and permissions page at /permissions.
- Which AI clients can connect?
- Any client that speaks MCP. Published setup guides cover every supported client, including the desktop, web and coding apps your technicians already use — see the connectors page for the current list and the steps for each.
- What is the difference between an API and an MCP server?
- An API is the interface a platform publishes for other software, and using it means writing code against its endpoints with your own keys. An MCP server exposes a system's data as tools an AI assistant can call with your permission, so you ask in plain English instead. The MSPStuff servers sit on each platform's own API: the server makes the calls, and every answer is traced to the tool call behind it.
- Is an MCP server safe to use?
- That depends on what the server can reach and change. Every live server listed here is read-only today, each person reaches only what their admin scoped for them, connector credentials stay out of the browser, and every answer is traced to the tool call that produced it. The security page at /security sets out each control and what it rests on.
Get AI connected to your stack.
Apply for the beta: 14 days free on the Hosted plan against your own environment, read-only, every answer traced. Accepted MSPs get half off seats and client tenants for the first year. Dedicated infrastructure is priced separately.