`public` defaults to 0, so a document an assistant creates is not visible to anyone else until you change that — the safe default for a tool that writes into a shared workspace. The one thing to get right at setup is the token: it is read from the environment rather than the config file, so a working `config.yaml` with no `YUQUE_TOKEN` exported still fails at the first API call.
A Yuque (语雀) knowledge-base server written in Go. It covers the document lifecycle against the Yuque v2 API: fetch a document, create one, update its title or body, search across your documents, and read the current user's profile.
- `yuque_get_document` fetches one document, taking `book_id` (the knowledge base) and `doc_id` (ID or slug)
- `yuque_create_document` creates one, taking `book_id` and `title`, with optional `body`, `format` (markdown by default) and `public` (private by default)
- `yuque_update_document` edits an existing document's `title`, `body`, `format` or `public` setting
- `yuque_search_documents` searches by `query`
- `yuque_get_current_user` returns the authenticated user's details
Go, and a Yuque API token supplied as the `YUQUE_TOKEN` environment variable. Run `go mod tidy`, then `go run cmd/server/main.go -f config.yaml`; the server listens on `http://localhost:8080`. `config.yaml` sets the host, port, the Yuque base URL (`https://www.yuque.com/api/v2`) and a 30s message timeout, and holds the CORS list. In a client, set `cwd` to the checkout and put `YUQUE_TOKEN` in the entry's `env`.
Build from source — clone the repository and build it, then point your client at the binary