> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.crisp.chat/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # How to connect your Knowledge Base to AI tools with MCP *Learn how to connect your Crisp Knowledge Base to ChatGPT, Claude, and other MCP-compatible AI tools.* The public MCP server makes the content of your public Knowledge Base available to compatible AI assistants. Once connected, they can search your documentation, read articles, summarize information, and retrieve relevant answers directly from your existing help content. If you're new to the Knowledge Base, start with [Getting started with the Crisp Knowledge Base](https://help.crisp.chat/en/article/getting-started-with-the-crisp-knowledge-base-i2tsm1/). --- # ${color}[#0080dd](Enable the public MCP server) Open [Crisp](https://app.crisp.chat), go to **Knowledge Base → Settings → MCP Server**. ||| The MCP server is public and does not require authentication. Only enable it if your Knowledge Base content is intended to be publicly accessible. Enable **Serve a public MCP Server from my Knowledge Base**. Crisp generates a **Public MCP Server URL** using your Knowledge Base domain and ending with `/mcp/`. Copy this URL to connect your Knowledge Base to an MCP-compatible AI tool. ![Enable the public MCP server for a Crisp Knowledge Base](https://storage.crisp.chat/users/helpdesk/website/-/8/7/a/e/87ae2703583ac800/crisp-knowledge-base-public-mc_o7klnr.png =900x572) #### ${color}[#445055](Available Knowledge Base tools) The public MCP server lets compatible AI assistants: * **Search the Knowledge Base** → find relevant information across your documentation * **Read article content** → retrieve the content of a specific page * **Browse Knowledge Base content** → explore the pages available in your documentation * **Check available languages** → identify which languages are published in your Knowledge Base The AI assistant chooses which tools to use depending on the user's request. --- # ${color}[#0080dd](Connect your Knowledge Base to an AI tool) Copy the **Public MCP Server URL** from your Knowledge Base settings and add it as a custom MCP connector in the AI tool you want to use. This can be used with MCP-compatible assistants such as **ChatGPT** or **Claude**. The exact connection flow depends on the tool, but the Crisp MCP URL is the endpoint you need to provide. Once connected, users can ask questions naturally based on your documentation. For example: `What is your GDPR policy?` The AI assistant can search the Knowledge Base, read the relevant articles, and use their content to answer. ![Use a Crisp Knowledge Base with an AI assistant through MCP](https://storage.crisp.chat/users/helpdesk/website/-/8/7/a/e/87ae2703583ac800/crisp-knowledge-base-mcp-ai-as_1moq8bi.png =550x567) This makes your existing help content accessible beyond the public Knowledge Base without maintaining a separate documentation source. --- # ${color}[#0080dd](Understand what content is available) The public MCP server exposes the **same content that visitors can access from the web version of your Knowledge Base**. It does not provide access to additional private Crisp data, such as Inbox conversations or other workspace information. If you need Hugo to connect to external systems, retrieve private data, or perform actions through MCP tools, use Crisp's separate MCP integrations for Hugo. See [How to build MCP integrations with Hugo](https://help.crisp.chat/en/article/how-to-build-mcp-integrations-with-hugo-tlrqmn/). #### ${color}[#445055](Control whether the MCP server is enabled) The default state depends on your Knowledge Base: * **New Knowledge Bases** → the public MCP server is enabled by default * **Existing Knowledge Bases with search engine indexing enabled** → the public MCP server is enabled * **Existing Knowledge Bases with search engine indexing disabled** → the public MCP server must be enabled manually You can disable the public MCP server at any time from **Knowledge Base → Settings → MCP Server**. --- # ${color}[#0080dd](Use MCP with protected Knowledge Bases) The public MCP server does not currently support Knowledge Bases protected with **password or JWT authentication**. If authentication is enabled on your Knowledge Base, the public MCP endpoint cannot access its protected content. For private documentation, keep authentication enabled rather than exposing the Knowledge Base through the public MCP server. Learn more about restricting access in [How to protect the Knowledge Base behind a password](https://help.crisp.chat/en/article/how-to-protect-the-knowledge-behind-a-password-1xfb10p/) or [How to setup JWT token authentication for your Knowledge Base](https://help.crisp.chat/en/article/how-to-setup-jwt-token-authentication-for-your-knowledge-base-6rbrhu/).