Comments

List the comments of an article

knowledge_base.comments.list

Lists the comments of a Knowledge Base article, oldest first, paginated by cursor: content (sanitized HTML, or plain text in old comments), content_text (plain text), mentioned user ids, author and dates (edited_at when the author edited it). Not found (kb_item_not_found) if the article does not exist or the caller cannot see it. Requires view access to the Knowledge Base.

Scope

knowledge_base:read

Permission

View the module

MCP tool

knowledge_base_comments_listOn the full surface; on the compact one, mb_execute_operation with id: "knowledge_base.comments.list".

Declared cost: up to 204 reads and 0 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/knowledge-base/items/{item_id}/comments" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/knowledge-base/items/{item_id}/comments" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Comment on an article

knowledge_base.comments.create

Adds a comment to a Knowledge Base article as the caller: content is HTML (sanitized: formatting, links and mention chips survive, scripts do not) or plain text, up to 10,000 characters. mentions are user ids to notify in the app: only people with access to the organization who can also see the article get the notice (the others are ignored, so a private article never leaks to someone who cannot open it). Returns the new comment. Requires full access to the Knowledge Base.

Scope

knowledge_base:write

Permission

Edit in the module

MCP tool

knowledge_base_comments_createOn the full surface; on the compact one, mb_execute_operation with id: "knowledge_base.comments.create".

Declared cost: up to 5 reads and 2 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/knowledge-base/items/{item_id}/comments" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "content": "CONTENT"
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/knowledge-base/items/{item_id}/comments" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "content": "CONTENT"
}'

Edit a comment

knowledge_base.comments.update

Replaces the content of a comment on a Knowledge Base article; it is marked as edited. Only its author can edit it (403 comment_author_only). mentions replaces the mentioned ids (without it, the previous ones stay); only newly added mentions are notified, and only to people who can see the article. Returns the comment. Requires full access.

Scope

knowledge_base:write

Permission

Edit in the module

MCP tool

knowledge_base_comments_updateOn the full surface; on the compact one, mb_execute_operation with id: "knowledge_base.comments.update".

Declared cost: up to 5 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X PATCH "https://api.mb-suite.com/v1/knowledge-base/items/{item_id}/comments/{comment_id}" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "content": "CONTENT"
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X PATCH "https://api.mb-suite.com/v1/knowledge-base/items/{item_id}/comments/{comment_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "content": "CONTENT"
}'

Delete a comment

knowledge_base.comments.delete

Deletes a comment of a Knowledge Base article. Its author can always delete it; an owner or admin can delete anyone's (403 comment_delete_denied otherwise). It stays 30 days in the trash. Outside the app it needs a dry run and a confirm_token, except a REST DELETE with a key allowed to delete.

With an API key, this DELETE runs directly: the record stays 30 days in the trash and the response carries its trash_item_id. With an OAuth token, and through the MCP, it needs dry_run → confirm_token.

Scope

knowledge_base:write and “Allow deletions” (knowledge_base:delete in OAuth)

Permission

Edit in the module

MCP tool

knowledge_base_comments_deleteOn the full surface; on the compact one, mb_execute_operation with id: "knowledge_base.comments.delete".

Declared cost: up to 3 reads and 2 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X DELETE "https://api.mb-suite.com/v1/knowledge-base/items/{item_id}/comments/{comment_id}" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X DELETE "https://api.mb-suite.com/v1/knowledge-base/items/{item_id}/comments/{comment_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"