MCP Hub can create a KB article from an assistant’s approved copy, but the create operation is not automatically an unpublished draft. Decide the audience, category and finished body before authorising it.

Prepare the target and copy

Use a dedicated content connection with a Write ceiling, the required content area and staff permissions. The separate read-only override must permit the intended write. The bound administrator needs Manage Knowledgebase in its administrator role. A connection limited to selected clients cannot operate on the shared knowledge base.

Ask the assistant to list the categories and identify the intended category IDs. Search existing article titles and read likely matches before creating another page for the same task. Draft and review the title, full body, links and language separately from the instruction to publish.

State the audience explicitly

Set access: private for signed-in clients or access: public for public material. Private does not mean the reader bought a particular product. The hub reports clients_see_it when reading the article; check that field along with its categories.

WHMCS does not expose a separate staff-only article mode through these tools. For material that must remain out of the client area during review, file it only in an agreed hidden review category and verify the reported visibility before sharing it. Do not add a visible category until that audience is intended.

Create and read back

1. Give the assistant the approved title and complete body.
2. Specify the exact existing categories and the required access setting.
3. Explicitly authorise Add a knowledge base article for that content and destination.
4. If the connection requires approval, review the pending operation before letting the assistant resume it.
5. Read the returned article ID with Read a knowledge base article.

Compare the saved title, full body, categories and access with what you authorised. Use ordinary headings, paragraphs, lists and links, then inspect the native article view for formatting and link behaviour. A saved HTML body is not proof that every rich embed or interactive element will render as intended.

Handle an uncertain result

If the create request times out or the assistant loses its result, search the category and matching title before trying again. A retry can create a duplicate. Verify the body and category of any returned ID instead of assuming it belongs to the intended request.

Keep the final ID and the publication or review location in your own content record. For a later revision, update that article rather than creating a replacement unless you intend a separate page.

See the PD MCP Hub WHMCS guide for related tasks, or explore PD MCP Hub.