MCP Client - Custom Tools Integration
S
Scott Cook
It's unacceptable that an MCP integration doesn't exist yet. It's actually hampering my efforts to recreate some things in Hatz I'm already able to do with copilot, like connect to HaloPSA and Microsoft Learn MCP servers. We need this now to accelerate adoption.
Brandon Adams
I was going to request the same. We are experimenting with the idea of hosting our own MCP gateway to integrate into our Autotask tenant. This would also allow for a fine level of control when it comes to the need of customizing functionality with interacting with any API or other entities MCP server. If users were empowered(since in this case half of us are techs at MSPs) to hook into our own/client's environments, we could find new use cases and have a level of control that makes sys admins feel warm and fuzzy inside. Currently, my main goal with the MCP GW is to use LangGraph (or similar) to build workflows to identify similar tickets and tag in Autotask (reoccurring issues/similar issues/recommended fix based off AT ticket notes) and alert management if related/similar tickets start coming in for the same or multiple clients. I'm diving into the schematics and how it all ties together. I know this is beyond what you're trying to provide at the moment, but the ability for agents to utilize tools from MCP gateways would be huge. Stateful awareness and agent collaboration would also be huge. (not sure if that's in the pipeline)