MCP Server Integration
Your own internal tools reach the agent the same way the built-in ones do. Point Rallied at an MCP server you already run, and every tool it exposes turns up in the catalog.
What you get
Your own tools, on the ticket
Internal APIs, systems built for your own MSP, and third-party services outside the built-in catalog all reach the agent this way. Point Rallied at the server and every tool it exposes turns up in the catalog.
Nothing to inventory by hand
Rallied finds the tools on your server, so there is no inventory to write out by hand. Run several servers at once and it keeps two identically named tools apart.
Reads run, writes wait
Rallied starts reads on auto and holds writes behind approval, going on the tool name. Tools from your server take permissions the same way the built-in ones do.
Taking a server back out
Disconnecting a server removes its tools from the catalog and deletes the policies that went with them.
What it handles
- Finds every tool your server exposes
- Connects a ConnectWise, Autotask, NinjaOne, or HaloPSA server you host
- Works with OAuth, a static token, or no authentication
- Starts reads on auto and writes behind approval, going on the tool name
- Runs several servers at once and keeps identical tool names apart