This guide will go over the Hudu MCP (Model Context Protocol) Server that enables seamless interaction between AI-powered tools and a Hudu instance. The MCP server acts as a bridge between AI clients (such as Cursor) and Hudu's API, exposing structured, reliable access to key resources.
This integration unlocks a powerful new workflow: AI-assisted documentation management, content creation, and auditing, directly inside Hudu.
Visit Process Runs for additional information on processes and runs in Hudu.
Guides
Before you begin
Before connecting any AI client, you must first enable MCP access inside Hudu.
You should also ensure your Hudu instance is accessible over SSL/HTTPS if you plan to connect to cloud-based AI services such as Claude or ChatGPT.
For most environments, your MCP endpoint will look similar to:
https://yourhuduinstance.com/mcp
Enable MCP access in Hudu
Inside Hudu:
- Navigate to Admin → External Apps → Model Context Protocol (MCP)
- MCP access is disabled by default.
- Click Enable Access to get started.
- Once enabled, Hudu will expose the MCP endpoint for external AI clients.
- When an AI client connects, users will authenticate through Hudu OAuth and approve permissions for the available tools.
Connecting AI clients
Each AI platform has a slightly different setup process. Detailed setup instructions for each platform are provided in their own dedicated guides:
Most MCP-compatible editors or AI clients will follow a similar process:
- Add the MCP server URL
- Authenticate through Hudu OAuth
- Approve permissions
- Start using Hudu tools inside the AI client
Tools
The MCP server provides full coverage for Hudu articles, including:
- Read articles (bulk) — articles can be retrieved via an Index operation, allowing AI clients to browse and reason over large sets of documentation.
- Read articles (single) — individual articles can be fetched via Show, enabling targeted access to specific pieces of documentation.
- Create new articles — AI clients can generate and publish entirely new articles directly into Hudu.
- Edit existing articles — the server supports updates to article name, article content, and draft status (draft vs. published).
This makes it possible to use AI for drafting, refining, and maintaining documentation without leaving your editor.
Not currently supported: deleting articles.
The MCP server also provides read access to Hudu article folders:
- Read article folders (bulk) — folders can be retrieved via an Index operation, allowing AI clients to see how documentation is organized.
- Read article folders (single) — an individual folder can be fetched via Show.
Not currently supported: creating or editing article folders.
The MCP server provides read access to Hudu companies, including:
- Read companies (bulk) — companies can be retrieved via an Index operation, allowing AI clients to browse and search across your Hudu instance.
- Read companies (single) — an individual company can be fetched via Show.
Not currently supported: creating or editing companies.
The MCP server also provides coverage for Hudu assets, including:
- Read assets (bulk) — assets can be retrieved via an Index operation, allowing AI clients to browse and search assets across companies.
- Read assets (single) — individual assets can be fetched via Show, including all field values.
- Read asset layouts — asset layouts (the schemas that define what fields each kind of asset has) can be retrieved via Index and Show, so AI clients understand the structure of an asset before creating or editing one.
- Create new assets — AI clients can generate and publish new assets directly into Hudu.
- Edit existing assets — the server supports updates to existing asset field values.
Not currently supported: deleting assets.
The MCP server provides coverage for Hudu processes and runs, including:
- Read processes (bulk) via Index
- Read processes (single) via Show, including tasks in depth-first order
- Create new processes
- Update existing processes
- Start new runs from a process
- Read runs (bulk) via Index
- Read runs (single) via Show, including tasks and a summary of the parent process
- Update a run's name or associated asset
- Complete or uncomplete tasks within a run
This allows AI clients to kick off and track documented procedures — like onboarding or offboarding checklists — without leaving the AI client.
Not currently supported: deleting processes or runs.
In addition to article, asset, and process/run management, the MCP server exposes Hudu activity logs:
- Read activity logs (bulk) via Index
- Read activity logs (single entry) via Show
This allows AI tools to inspect recent changes, understand historical context, and assist with audits or reviews.
Not currently supported: editing audit logs.
The MCP server also provides coverage for Hudu labels, including:
- Read labels (bulk) — label assignments on records can be retrieved via an Index operation.
- Read label types (bulk) — the admin-defined label types can be retrieved via Index, so AI clients can see which labels exist before applying one.
- Create new label types — AI clients can create new label types directly in Hudu.
- Edit existing label types — the server supports updates to a label type's name, color, and scope.
- Apply labels to a record — labels can be applied directly to a record.
- Remove labels from a record — labels can be removed directly from a record.
Not currently supported: deleting label types, reading a single label type by ID.
The MCP server can also retrieve public photos:
- Read a public photo — an individual public photo can be fetched by its slug.
Not currently supported: uploading or editing public photos.
FAQ
If your Hudu instance is proxied through Cloudflare or a similar bot-mitigation or WAF service, automated OAuth clients (such as Claude and other MCP clients) may silently fail during authentication. These clients cannot complete JavaScript-based challenge pages (such as Cloudflare's browser integrity check or CAPTCHA challenges), so the OAuth flow never completes.
This failure mode is particularly difficult to troubleshoot because the request never reaches Hudu — no error will appear in Hudu's own logs.
To resolve this, exempt the following URL paths from bot-challenge and WAF rules in your proxy or CDN configuration:
/oauth/*/api/oauth/*/.well-known/*
These paths are used during the OAuth authorization flow and must be reachable by automated clients without challenge interception. The exact steps will vary depending on your provider — refer to your provider's documentation for managing WAF rules or bot-fight mode exceptions.