Hudu MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Hudu MCP Servershow me the password for Acme's firewall"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hudu MCP Server
An MCP server for the Hudu API (v1), the IT documentation platform MSPs use per client. It lets an AI agent read companies, documented assets and their layouts, stored passwords, knowledge-base articles and folders, monitored websites, procedures, relations, Magic Dash tiles and the activity (audit) log and, on explicit request, create, update and archive records and (with confirmation) delete them.
Transport: MCP Streamable HTTP at
POST /mcp, health probe atGET /healthStateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first
tools/listPython 3.12, uv, FastMCP, httpx
License: Apache-2.0, Copyright 2026 MSPbots.ai
Authentication headers
Header | Required | Type | Default | Allowed values | Description | Example |
| Yes | string | none | https URL | Root URL of the Hudu instance (a bare host gets |
|
| Yes | string | none | - | Hudu API key |
|
Where to get them: in Hudu open the Admin area's API key settings and create a key. Use the key options Hudu offers (such as limiting the key or its access to passwords) to give the agent only what it needs. If Hudu restricts API access by IP, allow the public egress IP of the environment that runs this server.
How the key is sent to Hudu: every call goes to {X-Hudu-Base-URL}/api/v1/... with the key in
the x-api-key header.
A request to /mcp without both headers gets HTTP 401 naming the missing one; a non-https URL
gets HTTP 400.
Related MCP server: Hudu MCP Server
Tools
All tools return a JSON string. List tools take page and page_size (default 25, max 1000)
and return {count, page, has_more, next_page}. write marks tools that change data;
confirm marks deletes, which also need confirm: true.
Area | Tools |
Connection |
|
Companies |
|
Assets |
|
Asset layouts |
|
Passwords |
|
Articles |
|
Websites |
|
Other |
|
Errors come back as a JSON envelope instead of an exception:
{"error": {"code": "invalid_argument", "message": "Hudu returned HTTP 422 for companies: name has already been taken", "retryable": false}}code is one of not_configured, unauthorized, not_found, invalid_argument,
rate_limited, upstream_error. Reads are retried with backoff on 429, 5xx and network
errors; writes only on 429. Hudu allows about 300 API requests per minute per instance.
Run locally
uv sync
uv run python -m hudu_mcp # listens on 0.0.0.0:8080or with Docker:
docker build --platform linux/amd64 -t hudu-mcp:dev .
docker run --rm -p 8080:8080 hudu-mcp:devConfiguration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0),
MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read
from the environment.
Testing example
# list tools
curl -s http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-Hudu-Base-URL: https://docs.example.com" \
-H "X-Hudu-API-Key: your-hudu-api-key" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
# assets of one company
curl -s http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-Hudu-Base-URL: https://docs.example.com" \
-H "X-Hudu-API-Key: your-hudu-api-key" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"hudu_list_assets","arguments":{"company_id":12}}}'Unit tests (no network access needed):
uv run pytestDelivery notes
Tool count (39). Kept as is because the tool names are an existing contract.
Asset routes fixed. Hudu serves single assets only under their company (
/companies/{company_id}/assets/{id}); older versions called/assets/{id}, which does not exist, so getting, updating, deleting and archiving assets failed. The four tools now take an optionalcompany_idand look it up from the asset id when it is omitted.Password handling.
hudu_list_asset_passwordsreturns entries withpasswordandotp_secretmasked (plushas_password/has_otp_secret), so a company's credentials are not all exposed at once;hudu_get_asset_passwordreveals one entry. Create / update results are masked too.Deletes need confirmation. The five delete tools take
confirm: trueand otherwise return a "not done" result; archiving is the reversible alternative.Websites. Hudu stores the website address as its
name; the oldurlparameter, which the API ignores, was dropped. The websites list has no server-side company filter, socompany_idfilters the returned page.Request bodies are wrapped in the resource name Hudu expects (
{"company": {...}},{"asset": {...}}, ...).
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP facade over the Nebelus Construction API. ~48 tools give full agent build parity: create/update/probe agents, edit graphs, attach knowledge and vector stores, wire connectors, set governance policies and locked guardrails, enable grounding-trace, and read deployment wiring. Purpose-built for regulated industries: data residency is enforced per region (EU / GCC-KSA), with PII controls and an audit trail. Agents are created as drafts — no deploy tool is exposed over MCP by design; publishing happens in the Nebelus console.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with HUDU technical documentation and customer management platform through API integration. Supports retrieving company information, searching knowledge base articles, and managing assets and credentials.8MIT
- FlicenseCqualityDmaintenanceEnables Claude to interact with Hudu IT documentation, including searching, reading, creating, and updating articles, assets, passwords, companies, and more.100-
- AlicenseNot gradedqualityBmaintenanceConnects AI assistants to Hudu IT documentation platform with 43 tools, Markdown output, and multi-tenant support for MSPs.3MIT

hudu-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to interact with Hudu IT documentation, providing tools for companies, assets, knowledge base articles, credentials, IPAM, racks, and more, with security gates for passwords and destructive operations.7013 npmMIT