Docsbook
Overview

Comment on issue

MCPcomment_on_issueWRITE$0.02 / call

Reply on a GitHub issue or pull request — the conversation ON the record, where the question was asked. Use it when you finish work a record asked for (say what you did, with the numbers), when you were handed a comment to answer, and when you disagree with something written there. A reply that exists only in your answer is read once and lost; the thread stays unanswered.

Say the thing. Do not restate the record back at the reader, and do not promise to do something later — either do it now and report it, or say why it cannot be done. REQUIRES a read-write MCP token.

Issues and pull requests share one numbering on GitHub, so number accepts either.

Call get_issue_thread first. A reply that repeats an answer already in the thread is worse than silence.

Arguments
workspace_idstringoptional

Workspace ID (optional when MCP endpoint is auto-scoped). Numeric workspace id — OR the project as the user names it: 'owner/repo', the repo name alone, the site's display name, its docs URL or custom domain. Text is resolved server-side; an ambiguous name returns the candidates instead of guessing, so pass what the user said rather than calling list_workspaces first.

numbernumberrequired

The issue or pull request number.

bodystringrequired

Markdown. What you are actually saying — evidence and figures, not a summary.

Call it#

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "comment_on_issue",
    "arguments": {
      "number": 42,
      "body": "<body>"
    }
  }
}
curl -X POST 'https://docsbook.io/api/mcp/server' \
  -H 'Authorization: Bearer dbk_YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"comment_on_issue","arguments":{"number":42,"body":"<body>"}}}'

Try it over REST#

The same tool is callable as a plain HTTP request, no MCP client required. It runs on the same server, at the same price.

Your workspace is resolved from the API key, so workspace_id is decided server-side here and anything you send for it is ignored.

POST/api/v1/tools/comment_on_issue
Authorization
Authorizationstringrequired

Your API key, sent as Authorization: Bearer dbk_YOUR_API_KEY.Sent as the Authorization header. Your key is used only by your browser for this request — it is never sent to Docsbook or stored.

Body
argsobjectrequired

The arguments above, as one JSON object.

Request
curl -X POST 'https://docsbook.io/api/v1/tools/comment_on_issue' \
  -H 'Authorization: Bearer dbk_YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"args":{"number":42,"body":"<body>"}}'

Updated

Was this page helpful?