Skip to main content
Glama
lucasbenevinuto

gitbook-mcp

by lucasbenevinuto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to gitbook-mcp

No user-submitted related servers found.

    Related Servers

    • Evergreen

      hganumpally-a360
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read, write, and maintain documentation through an MCP server, providing tools for asking questions, generating docs, checking drift, and exploring knowledge graph.
      12 npm
      MIT

    • en-quire

      nullproof-studio
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for structured document management of markdown and YAML files, with RBAC, git-based approval workflows, and semantic search, enabling agents to read, edit, and maintain documents under governance.
      MIT

    • sourcebook

      BackendGameSetMatch
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI coding agents a git-backed markdown wiki to read and update, enabling search, read, write, verify, ingest, promote, and lint operations on versioned knowledge documents with schema validation, staleness tracking, and contradiction detection.
      4
      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 39 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs, but a few overlaps exist: get_page_by_id vs get_page_by_path both retrieve pages, and git_import vs import_content both perform destructive imports from different sources. These are minor confusions, as the descriptions clarify the differences.

    Naming Consistency4/5

    The naming convention is predominantly verb_noun in snake_case (e.g., get_space, create_change_request, list_comments), which is consistent. However, git_import and git_export break the pattern by placing the noun first, and ask_ai is slightly anomalous. Overall, the style is readable and predictable with only minor deviations.

    Tool Count2/5

    With 39 tools, this server is heavily over-scoped for an MCP server. The domain of GitBook is broad, but the tool count exceeds the typical range and feels unwieldy. Many tools are narrowly focused (e.g., list_requested_reviewers vs remove_reviewer), and consolidation could reduce the count while maintaining functionality.

    Completeness2/5

    Significant gaps exist in page management: there are no tools to create, update, or delete pages directly. While change requests are well-covered, the inability to manage pages is a critical omission. Also missing are delete operations for spaces and change requests, limiting lifecycle completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources