We Built an MCP Server in a Week.

If you've been in the MSP space for any length of time,you know the pain of IT Glue's API limitations. For years, we've had access toorganizations, configurations, passwords, and flexible assets, but the onething techs actually need mid-ticket, the actual documentation, has been lockedaway.

On January 27th, Kaseya quietly shipped Document APIendpoints in their v1.118.103 release. Documents, document sections, document images. The whole thing. I have to give credit where it's due: this has been along-requested feature and they delivered.

So naturally, we built an MCP server for it.

What's an MCP Server?

Model Context Protocol is Anthropic's standard for connecting AI assistants to external tools and data sources. Think of it as away to give Claude (or any MCP-compatible assistant) the ability to actually do things, not just talk about doing things.

In this case, we built a server that lets any MCP client create, read, update, and publish IT Glue documents directly through conversation.

What It Does

The server exposes 13 tools covering the new DocumentsAPI:

• List and search documents across organizations
• Get full document content with all sections
• Create new documents (they start as drafts)
• Update document metadata and content
• Add, edit, and reorder document sections (text, headings, galleries, steps)
• Publish documents when they're ready

It also includes organization lookup so you can find orgIDs without leaving your AI assistant.

How Fast Did This Come Together?

Kaseya shipped the API on January 27th. We had a workingMCP server published to npm by February 3rd. About a week from announcement to"npx itglue-mcp-server" working in Claude Desktop.

This is what happens when you've already built the infrastructure for tool integrations. The patterns are there, the auth flows are figured out, and adding a new API becomes mostly about mapping endpoints to tools.

How to Use It

If you're using Claude Desktop, Cursor, Windsurf, or any other MCP client, setup is straightforward. Add the following to your MCP config:

{
"mcpServers": {
"itglue": {
"command":"npx",
"args": ["-y","itglue-mcp-server"],
"env": {
"ITGLUE_API_KEY":"your-api-key-here"
}
}
}
}

Restart your client and you can start asking things like"create a new document in Acme Corp for their VPN setup" or"update the network diagram section in that doc I was working on."

EU and Australia regions are supported. Docker image is available if you prefer that route.

Full details and source code: github.com/Junto-Platforms/itglue-mcp-server

Or Just Use Junto

If you don't want to wire up MCP servers yourself, thisis exactly the kind of thing Junto handles out of the box. IT Glue documentation surfaces inline when you're working tickets, alongside your PSA,RMM, and Microsoft tenant data.

We actually had an IT Glue integration before this API existed. It worked by ingesting all your documents and chunking them for search. It got the job done, but it meant syncing large volumes of data anddealing with staleness issues. If someone updated a doc in IT Glue, there wasalways a lag before Junto had the latest version.

This new API changes everything. Now we can pull documents in real-time, directly from IT Glue, exactly when you need them. No sync delays, no stale data, no massive ingestion jobs. Way better for our partners.

We built this MCP server because we were already building the integration for Junto and figured the community could use it too. Open source, MIT licensed, use it however you want.

What's Next

The IT Glue Documents API is still pretty new, so we'llbe watching for any changes or additions from Kaseya. If they expand what's possible, we'll update the server.

In the meantime, if you're tired of tab-switching between your ticketing system and your documentation, this might save you some clicks.

Questions or feedback? Reach out or open an issue onGitHub.