MCP Hub’s category tools can create a topic section, place it under an existing parent and change its description or visibility. Start by reading the current hierarchy so an assistant does not create a second category with the same purpose.

Check the editorial connection

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 knowledge base categories before making changes. Read the returned category names, IDs, parents and visibility. A list restricted to one parent does not show the entire hierarchy.

Create the intended section

1. Identify the existing parent category, or explicitly choose the top level.
2. Specify the new category name and a short description of the topics it will contain.
3. State the intended visibility rather than accepting a default.
4. Ask the assistant to use Add a knowledge base category with that parent and visibility.
5. List the parent’s categories again and verify the returned category ID, name and setting.

For a review category, explicitly request hidden: true. In WHMCS, hiding a category is different from setting an article to Private. A private article is for signed-in clients; an article filed only in hidden categories is reported by the hub as unavailable to clients. Check every category attached to the article before treating it as a review draft.

The category tools use the hidden setting rather than an article-style staff access level. Do not ask for a nonexistent staff-only article switch or assume a category name such as Drafts changes visibility by itself.

Rename or move without duplicating

Use Edit a knowledge base category with the existing category ID when the task is changing a name, description, parent or visibility. Moving an existing category is different from creating another one with the same name. Do not move a category into itself or one of its descendants.

A visibility change can affect the articles filed there. Review the affected content and native client view as part of the intended change, rather than treating a category edit as a cosmetic update.

If a create request has an uncertain outcome, list the categories and reconcile the result before retrying. Read back the saved hierarchy after an authorised change; the assistant’s success message alone is not the final check.

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