BookStack for internal wikis
BookStack's MCP server, a community project by pnocera, gives an agent full read and write access to a self-hosted BookStack wiki organized into books, chapters, pages, and shelves. For internal wikis it is the second of four picks, and the angle that earns it is control: teams who want their knowledge base on their own infrastructure, with its structure intact, get an agent that reads and edits it directly.
It lands second because the top pick is stronger for general team-knowledge work, but BookStack is the clear fit when self-hosting and a book-and-chapter hierarchy are what you run. The agent can search the wiki, read a chapter, and create or update content without anyone hunting through the UI.
How BookStack fits
Retrieval starts with search. bookstack_search runs across the whole wiki and bookstack_search_books narrows to books, so an agent can find the relevant section and cite it. bookstack_books_list and bookstack_books_read browse and open books, while bookstack_chapters_list and bookstack_chapters_read do the same one level down. On the write side, bookstack_books_create, bookstack_books_update, bookstack_chapters_create, and bookstack_chapters_update let the agent author and revise content, and bookstack_books_export emits a book as PDF, HTML, plain text, or Markdown. bookstack_books_delete moves a book to the recycle bin rather than destroying it outright.
The siblings fit other shapes. Outline is the first pick, a polished team knowledge platform that suits general company docs and is hosted or self-hostable. Guru is the match for verified, card-based knowledge surfaced in workflow. Coda fits when your docs behave like databases with tables and structured data. Reach for BookStack when you self-host, value the book-and-chapter structure, and want an agent with full read and write across it. Note the page-level tools are not in this set, so the agent works mainly at the book and chapter level.
Tools you would use
| Tool | What it does |
|---|---|
| bookstack_search | Searches across the BookStack wiki for matching content. |
| bookstack_search_books | Searches specifically within books. |
| bookstack_books_list | Lists books with sorting and pagination. |
| bookstack_books_read | Reads a single book by id. |
| bookstack_books_create | Creates a new book. |
| bookstack_books_update | Updates an existing book. |
| bookstack_books_delete | Deletes a book (moves it to the recycle bin). |
| bookstack_books_export | Exports a book to PDF, HTML, plain text, or Markdown. |
| bookstack_chapters_list | Lists chapters. |
| bookstack_chapters_read | Reads a single chapter by id. |
FAQ
- Can the agent edit wiki content, or only read it?
- Yes. bookstack_books_create and bookstack_books_update, plus bookstack_chapters_create and bookstack_chapters_update, let the agent author and revise books and chapters. Deletion via bookstack_books_delete is non-destructive, moving the book to the recycle bin.
- Why pick BookStack over Outline for an internal wiki?
- Choose BookStack when you self-host and want the book-and-chapter structure with full agent read/write. Outline is the top pick for general team knowledge and broader polish, so it leads for the overall internal-wiki task while BookStack wins on self-hosted control.