Hudu MCP server and AI skills, in the works
Your documentation, finally answerable.
Hudu holds the tribal knowledge — articles, assets, processes, and the relationships between them. It isn't on the board yet; the connection is being built in the open, and this page is the plan rather than a shipped feature. Once it's connected, a session will be able to pull the documented answer instead of guessing at it.
In development. Not available to connect yet.
A clear view of what is being built.
Explore the planned scope while this integration is in development. Successful sessions will depend on the released tools and your granted access.
- 01Your platformHudu
- 02Integration in developmentCoverage and setup are being prepared.
- 03Preview the documented scopeRead the planned questions and connection requirements below.
The story
What changes once it’s connected.
Everything is in Hudu. The wifi setup at the site nobody has visited in a year, the assets that tie to the client you're on the phone with, the onboarding runbook the last tech wrote and never told anyone about. It's documented; it just isn't answerable, which is why people still ask in Teams and get an answer from memory. Once Hudu is on the board, the documented version will come back inside the session — what we have written down for that client's network, which assets belong to that office, what the runbook actually says to do first.
It isn't connected yet, and the plan matters more than usual on this one, because Hudu can hold secrets as well as knowledge. The plan is to scope the connection to articles, assets and their relationships and to leave password entries out of what it can ask for, rather than filtering them out of answers afterwards; the connect page will say exactly what refuses them, and where, when it exists. Connecting will take an API key you generate in Hudu and your instance URL, hosted or self-hosted alike. The full skill list and its limits get published here the day it ships.
Hudu offers its own Hudu MCP Server, which can draft and edit KB articles and update asset records, so it is fair to ask why a second one. The plan for this one is narrower and aimed at the MSP desk: MSPStuff will host it, so there is nothing for you to run, and it is planned to answer from articles, assets and their relationships, with password entries left out of what it can ask for. The two would fit different jobs. One helps you write and maintain the documentation; this one is meant to read it back to the tech on the call, next to the ticket and the device the question is about, once your other platforms are connected too.
What you’ll be able to ask
Here’s what’s coming.
Connecting
Connection preview.
How connecting will work
- 01You'll generate an API key in Hudu (Admin → API Keys).
- 02Have your Hudu instance URL ready — hosted and self-hosted work the same way.
- 03The instance URL and key get entered here; password entries stay excluded by design.
Common questions
Asked before you had to ask.
Does Hudu have an API or MCP server?
Hudu supports a RESTful API and offers its own Hudu MCP Server, which can draft and edit KB articles and update asset records. MSPStuff's Hudu MCP server is in the works and not available to connect yet. The plan is to scope it to articles, assets and their relationships, with password entries left out.
Related
Keep patching the board.
Get AI connected to your stack.
Apply for the beta: 14 days free on the Hosted plan against your own environment, read-only, every answer traced. Accepted MSPs get half off seats and client tenants for the first year. Dedicated infrastructure is priced separately.