Skip to main content
Glama
HoYongJin

gitbook-mcp

by HoYongJin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to gitbook-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Server

      Nawaf-TBE
      A
      license
      Not graded
      quality
      D
      maintenance
      A Node.js/TypeScript server implementing the Model Context Protocol that provides integrations with GitHub and Notion, allowing automated workflow between these platforms via API endpoints.
      1,026 npm
      MIT

    • GitHub Integrated MCP Server

      wj-yuta-imai
      -
      license
      C
      quality
      Not graded
      maintenance
      A Model Context Protocol server with GitHub API integration that enables interaction with repositories, issues, pull requests, and file management through a standardized interface.
      1
      -
    • git MCP server by modelcontextprotocol

      git MCP serverofficial

      modelcontextprotocol
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models.
      12
      32,924 PyPI
      90,399
      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 89 tools

    Disambiguation3/5

    Many tools have similar names (e.g., list_*_backlinks for different scopes), but descriptions help differentiate. However, with 89 tools, the sheer volume makes it hard for an agent to quickly select the right one, especially without clear categorization.

    Naming Consistency5/5

    All tools adhere to a strict 'gitbook_verb_noun' pattern, with consistent use of prepositions like 'in', 'by', 'for'. No mixing of conventions, making the naming predictable across the entire set.

    Tool Count2/5

    89 tools is excessive for a documentation tool. Many tools handle granular sub-resources (e.g., backlinks, meta-links in specific contexts) that could be consolidated. This makes the surface feel bloated and hard to navigate.

    Completeness3/5

    Covers most read and manage operations for spaces, change requests, comments, and files. However, direct content creation/editing is limited to an asynchronous import tool; no create/update page or document body tools exist, leaving a notable gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources