BookStack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOKSTACK_TOKEN | Yes | Your BookStack API token secret | |
| BOOKSTACK_BASE_URL | Yes | The base URL of your BookStack instance | |
| BOOKSTACK_TOKEN_ID | Yes | Your BookStack API token ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_booksC | Get a listing of books visible to the user |
| get_bookB | Get details of a specific book including its content structure |
| create_bookC | Create a new book in the system |
| update_bookC | Update an existing book |
| delete_bookA | Delete a book (moves to recycle bin) |
| export_bookC | Export a book in various formats |
| list_chaptersB | Get a listing of chapters visible to the user |
| get_chapterB | Get details of a specific chapter including its pages |
| create_chapterC | Create a new chapter in a book |
| update_chapterC | Update an existing chapter |
| delete_chapterB | Delete a chapter (moves to recycle bin) |
| export_chapterC | Export a chapter in various formats |
| list_pagesC | Get a listing of pages visible to the user |
| get_pageC | Get details and content of a specific page |
| create_pageC | Create a new page in a book or chapter |
| update_pageC | Update an existing page |
| delete_pageB | Delete a page (moves to recycle bin) |
| export_pageC | Export a page in various formats |
| list_shelvesB | Get a listing of shelves visible to the user |
| get_shelfC | Get details of a specific shelf including its books |
| create_shelfC | Create a new shelf |
| update_shelfC | Update an existing shelf |
| delete_shelfB | Delete a shelf (moves to recycle bin) |
| search_allA | Search across all content types (books, chapters, pages, shelves) in BookStack |
| list_usersC | Get a listing of users in the system |
| get_userB | Get details of a specific user |
| create_userC | Create a new user account |
| update_userC | Update an existing user account |
| delete_userA | Delete a user account (requires admin permissions) |
| list_rolesC | Get a listing of roles in the system |
| get_roleB | Get details of a specific role including permissions |
| create_roleC | Create a new role |
| update_roleC | Update an existing role |
| delete_roleB | Delete a role (users with this role will lose it) |
| list_attachmentsC | Get a listing of attachments |
| get_attachmentC | Get details of a specific attachment |
| delete_attachmentC | Delete an attachment |
| list_imagesB | Get a listing of images in the gallery |
| get_imageC | Get details of a specific image |
| update_imageC | Update image details |
| delete_imageC | Delete an image from the gallery |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 41 tools
Every tool has a clearly distinct purpose with no ambiguity, as each combines a specific action (create, get, list, update, delete, export) with a specific resource type (book, chapter, page, role, shelf, user, attachment, image). The search_all tool is distinct in covering multiple resources. No tools appear to do the same thing.
All tools follow a consistent verb_noun pattern throughout, using snake_case with clear action verbs (create, get, list, update, delete, export) paired with resource nouns. There are no deviations or mixed conventions, making the naming highly predictable and readable.
With 41 tools, the count is excessive for the server's purpose of managing a documentation/wiki system. This feels heavy and could overwhelm agents, as many tools are repetitive across resources (e.g., create/delete/update for each resource type). A more streamlined set would improve usability.
The tool surface provides complete CRUD/lifecycle coverage for the domain, including create, get, list, update, delete, and export operations for all core resources (books, chapters, pages, roles, shelves, users, attachments, images), plus search functionality. There are no obvious gaps or dead ends for agent workflows.