Skip to main content
Glama

Related Servers

Alternatives to bookstack-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      297 npm
      37
      MIT
    • 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
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI models to interact with BookStack wiki instances through a comprehensive API interface. Supports content management (books, chapters, pages), user administration, search functionality, and content export in multiple formats.
      41
      6 npm
      MIT
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      HTTP MCP server enabling LLMs to search, create, read, update, and delete BookStack entities (books, chapters, pages, shelves) using API tokens.
      297 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: search, list, and get cover different retrieval modes, and create_* are resource-specific. The main ambiguity is between edit_page and update_page, plus the generic 'update' versus 'update_page', though the descriptions explicitly clarify when to use each.

    Naming Consistency3/5

    Page and creation tools follow a clean verb_noun pattern (create_page, update_page, edit_page, create_book, create_chapter, create_shelf), but read/update/delete tools are bare verbs (search, list, get, update, delete). This mixes conventions within the same set.

    Tool Count5/5

    11 tools is well-scoped for a BookStack integration, covering the four entity types (shelf, book, chapter, page) without bloat. Each tool earns its place in the workflow.

    Completeness4/5

    Full lifecycle coverage exists: create for all four entity types, read via get/list/search, update via update_page/edit_page/update, and delete across types. Minor gaps like attachments or user/role management are outside the core wiki scope and unlikely to block agents.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues