Custom connectors for Claude, ChatGPT and Copilot
A connector lets the AI you already use call a system's tools. MSPStuff Switchboard is one connector for your whole MSP stack — sign in once, and Claude, ChatGPT or Copilot can read across ConnectWise, Microsoft 365, Meraki, Pax8 and every platform your company connected, read-only by default, every answer traced.
What a connector is
One door, your whole stack behind it.
The Model Context Protocol (MCP) is the open standard AI assistants use to call tools. An MCP server exposes a system's data as tools an AI can call with your permission; a connector is how your AI reaches one.
A custom connector is an MCP server you add to your AI yourself — in Claude it lives under Settings, then Connectors; ChatGPT and Copilot have the same idea under different names. Most servers cover one product.
Switchboard is one hosted, scoped MCP server for the whole stack. Your admin decides, per person and per domain, what it may reach; you sign in with your MSPStuff account, and every platform your company connected is behind that one connector.
Add MSPStuff as a custom connector
Three steps, whichever AI you use.
Every client points at the same endpoint. Sign in with your MSPStuff account and your admin's scope applies — nothing to install, no keys to hand around.
https://www.mspstuff.io/mcpClaude.ai
In the browser, on Pro, Max, Team or Enterprise.
- Open Settings → Connectors → Add custom connector.
- Name it MSPStuff and paste the endpoint above.
- Approve the request — you sign in with your MSPStuff account — then switch MSPStuff on in a chat.
Claude Desktop
The Mac or Windows app, same account as Claude.ai.
- Open Claude Desktop → Settings → Connectors → Add custom connector.
- Paste the endpoint above.
- Approve the request with your MSPStuff account, then enable it in the chat's tools menu.
ChatGPT
Plus, Pro, Team or Enterprise — connectors may need your workspace admin.
- Open Settings → Connectors → Create (Developer mode may need turning on for your workspace).
- Paste the endpoint above as the MCP server URL.
- Approve the request — you sign in with your MSPStuff account — then start a chat with the connector on.
Microsoft Copilot (Copilot Studio)
Add MSPStuff as a tool on a Copilot Studio agent for Microsoft 365.
- In Copilot Studio open your agent → Tools → Add a tool → Model Context Protocol.
- Paste the endpoint above; authentication is discovered automatically (OAuth).
- Approve the request with your MSPStuff account, then publish the agent.
Claude Code
Anthropic's terminal agent — one command, uses a key.
- Create a key on your Connect your AI page — it is shown once, so copy it straight away.
- Run the connect command shown on your Connect your AI page in your terminal.
- Run claude mcp list — mspstuff should read as connected.
Cursor
The AI code editor — configured from a JSON file, uses a key.
- Create a key on your Connect your AI page — it is shown once, so copy it straight away.
- Add the config block shown on your Connect your AI page to ~/.cursor/mcp.json (or the project's .cursor/mcp.json).
- Reload Cursor — mspstuff appears under Settings → MCP.
What it can reach
What it reaches — and what it can't.
Only the platforms your company connected
A connector reaches what an admin connected — nothing else, and nothing you did not already have access to.
Only the domains your admin allowed, per person
Service, finance, sales, company, assets, projects, people: each person's connector is scoped separately, and the admin can change it any time.
Read-only by default
Writes exist only where a platform's page says so, and every one of them is confirmed with you before it runs.
Every answer traced
Each figure in an answer points at the tool call that produced it, so you can check the work.
Nothing to install
No agent, no API keys handed to technicians — the server is hosted and operated by MSPStuff.
Revoked in one click
Your Connect your AI page lists every client that ever connected; disconnecting one ends its access immediately.
Your own server
Bring your own MCP server
Point Switchboard at an MCP server you run or subscribe to, approve exactly the tools it may use, and sessions ask across it like any other platform.
Your server is reached only through an MSPStuff-hosted gateway that lists the approved tools and nothing else — the brain never connects to it directly, and the credentials you give it stay in the vault.
Anything you bring is labelled as yours, not vetted by MSPStuff, and any tool you mark as able to change things is confirmed before it runs.
Common questions
Connectors, answered straight.
What are Claude connectors?
Connectors are how Claude reaches outside systems: each one is an MCP server that exposes a system's data as tools Claude can call with your permission. Anthropic ships some, and you can add custom ones — MSPStuff Switchboard is a custom connector that covers your whole MSP stack.
How do I add a custom connector in Claude?
In Claude.ai or Claude Desktop open Settings, then Connectors, then Add custom connector. Paste the MSPStuff endpoint, approve the request by signing in with your MSPStuff account, and switch MSPStuff on in a chat. Claude Code takes the same endpoint with a key from your Connect your AI page.
What data can Claude access through connectors?
Through the MSPStuff connector, only what your admin scoped for you: the platforms your company connected, the domains you were allowed, read-only by default. Every answer is traced to the tool call that produced it, and your admin can revoke a client at any time.
Are Claude connectors safe?
A connector is as safe as the server behind it. MSPStuff's is hosted and operated by us, scoped per person, read-only by default, and every call is logged; credentials never sit in the browser or in your AI client. Read the platform pages for exactly what each one can and cannot touch.
Is there a Microsoft 365 connector for Claude?
Yes. Connect Microsoft 365 in Switchboard and the same connector gives Claude, ChatGPT or Copilot read access to your client tenants — users, licenses, Intune devices, MFA gaps and service health — with writes only through capability packs each client's own Global Admin consents to.
Can I use my own MCP server with Switchboard?
That is coming to the dedicated tier: point Switchboard at a server you run or subscribe to, approve the tools it may use, and sessions ask across it like any platform. Your server is reached only through an MSPStuff-hosted gateway, and anything you bring is labelled as yours.
Does this work with ChatGPT and Copilot too?
Yes. The same endpoint works as a connector in ChatGPT (Settings, then Connectors) and as a tool on a Copilot Studio agent, and as an MCP server in Claude Code and Cursor. One endpoint, scoped by your admin, for every client on your team.
Every platform behind the connector is documented on its own page — see the whole board.
Patch your stack in.
Apply for the beta — a read-only Switchboard trial against your own environment, traced answers, live in an afternoon. Accepted MSPs get half off the whole first year.