PD MCP Hub has dedicated tools for listing, reading, creating and updating knowledge-base content. The connection’s ceiling, selected area and bound staff permissions must all match the intended task.

Choose a content connection

Use a separate connection for editorial work rather than widening an assistant that handles a particular client. KB content belongs to the installation: a connection with Limit to specific clients populated is refused KB operations, including reads.

Blesta knowledge-base tools use Support Manager. That plugin must be installed for the company, and the bound active staff member’s group needs access to its Knowledge Base area. A group permission for client invoices does not grant knowledge-base access.

Set the required access

1. Open PD Modules → MCP Hub → Connections and edit the intended content connection.
2. Select the staff account whose permissions have been reviewed for this task.
3. Under Which areas it can reach, select Content — knowledge base, announcements, client notes. This is a group of capabilities, not a KB-only grant; the staff permissions and ceiling further limit it.
4. For reading, keep Ceiling at Read only. Creating or editing an article requires Write — update records or higher.
5. If writes are intended, check that the separate read-only override is not still preventing changes.
6. Consider Ask a person before anything that changes data, not just the risky ones, then save.

The module also associates its KB tools with Core, but choosing Content makes the editorial purpose clear. Do not add billing, ticket or provisioning access merely to obtain KB tools.

Read before writing

Refresh the assistant’s tool list and start by listing categories or reading an agreed article. Confirm the target category, language and visibility before requesting a change. A create request can publish immediately; it is not automatically an unpublished draft.

Deletion uses a higher destructive class and human approval. Ordinary article creation and editing do not need that ceiling. If a KB write is refused, check its specific reason rather than granting the highest class.

Verify the result

After an authorised edit, read the article back and inspect Audit trail. Check the full body, categories and access setting, not just the assistant’s success message. If approval is pending, inspect the module’s Approvals screen before retrying.

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