# GitBook MCP for AI Agents AI Agent Connect > GitBook MCP lets your AI agent read, search, and manage your technical documentation. Connect your GitBook account to browse spaces, retrieve page content, and audit your entire knowledge base directly from your favorite AI client. ## Overview - **Category:** developer-tools - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_bRfoqKlN0JQsHziOen3XBSPPRUJeuiKs7Qebu7XE/ai-agent-connect - **Tags:** documentation, docs-as-code, technical-writing, knowledge-base, collaboration ## Description Stop switching tabs every time you need to check a technical spec or find a snippet of documentation. This Connector lets you talk to your documentation instead of scrolling through it. When you connect your GitBook account, your AI agent can actually see your entire hierarchy. You can ask it to find specific pages, summarize content, or check how your spaces are organized across different teams. It turns your documentation into a searchable knowledge base that your agent can actually interact with. If you're managing a complex docs-as-code workflow, this makes it much easier to keep everything organized without manual auditing. You can find this in the Vinkius catalog to get your environment set up in minutes. It's about getting answers directly in your chat instead of hunting for them in a browser. ## Tools ### list_organizations See all organizations mapped to your profile. This helps you understand the scope of your connected accounts. ### list_spaces Browse the different spaces within a specific organization. Use this to see all available documentation environments. ### get_space Fetch the specific details and metadata for a single space. This is useful for checking visibility and access rules. ### list_pages Get a list of all pages nested inside a specific space. Use this to map out a documentation hierarchy. ### get_page Read the full content of a specific documentation page. This allows your agent to analyze specific technical details. ### search_content Find matching snippets of content within a space using keywords. This is the fastest way to find specific information. ### list_collections Identify how different product documentations are grouped in collections. This helps you see the overall organization. ### get_me Retrieve your authenticated profile information and permission limits. Use this to verify your current account context. ## Prompt Examples **Prompt:** ``` What's the hierarchy for the 'Getting Started' space? ``` **Response:** ``` ### Getting Started Space Hierarchy Here is the structure I found in the **Getting Started** space: * **Introduction** * Welcome * Quick Start * **Core Concepts** * Architecture Overview * Data Models * **Advanced Topics** * Custom Integrations * Webhooks Would you like me to read the content of any of these specific pages? ``` **Prompt:** ``` Search for 'OAuth' in the API docs. ``` **Response:** ``` I searched the **API Reference** space for 'OAuth' and found the following relevant sections: | Page Title | Relevance | | :--- | :--- | | **Auth Overview** | High - Explains the general flow. | | **Token Exchange** | Medium - Specific to getting tokens. | | **Refresh Flow** | Low - Details on refreshing. | Which one should I summarize for you? ``` **Prompt:** ``` Who am I logged in as? ``` **Response:** ``` You are currently logged in as **Alex Rivera**. * **Email:** alex.r@company.com * **Permissions:** Full Admin Access * **Context:** Connected to the 'Engineering' organization. ``` ## Capabilities ### Browse documentation hierarchy View your entire organization structure and nested spaces. ### Retrieve page content Pull full text from specific pages for your agent to analyze. ### Search across namespaces Find specific content snippets using natural language. ### Audit space metadata Check visibility rules and structural configurations for any space. ### Verify user permissions Get authenticated profile details to check account contexts. ## Use Cases ### Support Rep finding answers A rep asks for 'OAuth steps' and the agent uses search_content to find the right page and summarizes the instructions. ### Technical Writer auditing structure A writer wants to see if a new space is linked correctly and uses list_spaces to check the organization structure. ### Product Manager checking distribution A manager asks the agent to list all collections to see how different products are grouped for customers. ### Developer checking page hierarchy A dev wants to see the page hierarchy for a specific guide and asks the agent to use list_pages. ## Benefits - No more manual tab switching because get_page lets your agent pull content directly into your chat. - Faster audits with list_collections and list_spaces, helping you see the big picture of your docs. - Easier content discovery using search_content to find specific info without knowing the exact URL. - Better permission management by using get_me to verify who can see what across the organization. - Simplified navigation where your agent can use list_pages to map out complex documentation hierarchies. ## How It Works The bottom line is you get instant access to your technical docs through a natural conversation. 1. Subscribe to this Connector on Vinkius. 2. Add your GitBook API Token from your developer settings. 3. Ask your AI client to list your spaces or search for specific content. ## Frequently Asked Questions **Can the GitBook MCP help my team find answers faster?** Yes, it lets your agent search all your spaces and pull specific content instantly. You can get answers in your chat without leaving your workflow. **Does the GitBook MCP work with my current documentation?** Yes, it connects to your existing GitBook account. It reads whatever content you already have organized in your spaces and collections. **How do I use GitBook MCP to audit my docs?** You can ask your agent to list all your spaces and collections. This gives you a bird's-eye view of your documentation structure for easier auditing. **Can my AI agent read specific pages for me?** Yes, it can pull the full text from any page in your GitBook. This is great for getting detailed summaries of long technical guides. **Is the GitBook MCP good for large knowledge bases?** Yes, it's designed to navigate complex hierarchies. It allows your agent to browse different organizations and spaces to find exactly what you need. **Can my agent search for technical content across all my GitBook spaces?** Yes. Use the 'search_content' tool. Provide the 'space_id' and your query. The agent will execute cross-page search operations within that GitBook namespace, returning matching snippets and relevant content natively. **How do I retrieve the full content of a specific documentation page via chat?** Use the 'get_page' tool. You will need the 'space_id' and the 'page_id'. Your agent will read the full document content from GitBook, allowing you to summarize, analyze, or verify the information flawlessly. **Can I see how my product documentations are grouped through the agent?** Absolutely. Use the 'list_collections' tool with your Organization ID. Your agent will retrieve the collections that group multiple spaces, helping you understand your documentation hierarchy natively.