Skip to main content
Glama
lautarobarba

BookStack MCP Server

by lautarobarba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to BookStack MCP Server

No user-submitted related servers found.

    Related Servers

    • @h4sht/bookstack-mcp

      h4sht
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage BookStack wikis with tools for CRUD operations on books, chapters, pages, shelves, and search, using Markdown input.
      2
      MIT

    • BookStack MCP Server

      ttpears
      A
      license
      B
      quality
      B
      maintenance
      Enables interaction with BookStack knowledge management systems through the BookStack API. Supports searching, reading, creating, and updating documentation content with secure authentication and dual transport modes for flexible deployment.
      17
      252 npm
      37
      MIT

    • BookStack MCP Server

      pnocera
      A
      license
      B
      quality
      A
      maintenance
      Connects BookStack knowledge bases to Claude through 47+ tools covering complete CRUD operations for books, pages, chapters, shelves, users, search, attachments, and permissions. Enables full management of BookStack content and configuration through natural language.
      56
      215 npm
      91
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 41 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources