Docsbook
Übersicht

Read docsbook doc

MCPread_docsbook_docREADno token needed$0.008 / call

Read ONE page of DOCSBOOK'S OWN official documentation in full, verbatim, by the path from a search_docsbook_docs hit (e.g. 'guides/advanced/custom-domain.md'). Use it when the search snippet is not enough to act on: step-by-step setup, the exact list of options a setting takes, what a limit actually is, what a plan actually includes. Reading the page before you answer is the difference between telling a user which switch to flip and inventing one. 🔴 This is the PRODUCT's manual, not the user's documentation — that is read_doc.

Arguments
pathstringrequired

Path in the official docs, from a search_docsbook_docs hit, e.g. 'ai/chat.md'.

Call it#

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

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.

GET/api/v1/read_docsbook_doc
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.

Query
pathstringrequired

Path in the official docs, from a search_docsbook_docs hit, e.g. 'ai/chat.md'.

Request
curl 'https://docsbook.io/api/v1/read_docsbook_doc?path=%3Cpath%3E' \
  -H 'Authorization: Bearer dbk_YOUR_API_KEY'

Updated

War diese Seite hilfreich?