James Wright spent months telling two vendors they needed to talk to each other.
Wright is the CTO of Executech, an MSP that had already built its service desk around Liongard's asset intelligence platform. What he wanted was a way to get that data in front of his technicians without a separate login, and Thread, the AI Service Desk platform Executech also runs on, was the other half of that answer. So Wright pushed the two companies together directly, by his own account, "grabbing them both by the ear," until Liongard and Thread built the integration.
That integration, run through Thread MCP, which connects AI tools like Claude and ChatGPT directly to an MSP's PSA, RMM, and other connected systems, so a technician can ask a plain-English question instead of hunting for the answer across five logins. Paired with Liongard, that question can now reach Executech's asset data too.
Before the integration, Wright's team dealt with a familiar failure mode. "They would get lost," Wright said of tickets, describing what happened when documentation lagged behind reality: someone leaves for the weekend, changes something, forgets to note it, and the next tech to touch that client's environment is missing the one detail that explains the outage.
That gap wasn't a documentation problem so much as a timing problem. Liongard was already collecting the underlying data, asset states, configurations, identities, but pulling it into a specific ticket still meant a technician stopping to go look, assuming they knew to look there at all. Wright has described this as Liongard giving him "the devil in the details," but reaching those details still took a separate step.
There was a second cost that showed up less in any one ticket and more in how long it took a new hire to become useful. A new technician had to learn not just the client's environment, but which internal tool held which piece of truth, and how much to trust whatever the last person had documented.
With Liongard connected through Thread MCP, that lookup step collapses into the question itself. A technician working a ticket can ask directly, in the same conversation where they're already working the issue, and get an answer sourced from Liongard's asset inventory rather than whatever documentation happened to be current.
Wright has pointed to onboarding as where this shows up most clearly. New technicians no longer need to be fluent in Liongard's interface to get value from what it's collected. They also aren't stuck trusting that whoever documented a client's environment last got it right. "They're not going down a rabbit hole," Wright said. "Just get them the direct points, quick and easy." Data that used to require someone to go find it starts showing up the moment a technician asks.
The pattern isn't unique to Executech. Other MSPs using the same integration have used it to answer backup questions during compliance tickets, pull a client's security posture on demand ahead of a quarterly business review, and sweep for assets like expiring SSL certificates directly from a chat window instead of a separate report. What changes in each case is the same thing Wright was after: the data was already there, and the only thing missing was a way to ask for it without leaving the ticket.
Thread founder Mark Alayev and Liongard co-founder Vin Tran have both credited Wright with getting the two companies into the same room in the first place, a partnership that came together over roughly a year rather than being planned from the start by either vendor. All three told that story in detail on a joint webinar hosted by Liongard, where Alayev ran a live demo of the same kinds of questions Wright's team had been asking, the license audits, the SSL certificate sweeps, the searches that used to mean five separate logins.
For Executech, the result is less about any single feature and more about what stopped being a separate step. The data Liongard was already gathering didn't need a new home. It needed a way for a technician to ask for it without knowing, in advance, that it was the right place to look.
If your MSP already runs on Thread and Liongard, schedule a demo to see the integration working against your own environment.
What is Thread MCP? Thread MCP is Thread's Model Context Protocol server. It connects AI clients like Claude and ChatGPT directly to an MSP's PSA, RMM, and documentation systems, so a technician can ask a question in plain English instead of logging into each system separately.
How does the Thread MCP and Liongard integration work? Once an MSP connects Liongard through Thread MCP, a question asked from Claude or ChatGPT routes through Thread to Liongard's asset inventory and back, giving technicians access to Liongard's asset data without a separate login or a separate report.
What is asset intelligence? Asset intelligence is a continuously updated, deduplicated record of every identity, device, and system in an environment, tracked over time so changes are visible as they happen. Liongard, which uses the term to describe its platform, aggregates this across more than 90 supported systems rather than any single PSA or RMM alone.
Does it cost extra for MSPs already using both Thread and Liongard? No. According to both companies, MSPs who already run Thread and Liongard don't pay an additional fee to connect the two through Thread MCP.