Connect AI Tools With MCP

MCP access lets visitors connect your Scroll Sites help center to the AI tools they already work in, like Claude, ChatGPT, Cursor or VS Code. Their AI tool can then search your site and read your articles directly, so answers come from what you published, not from the model's training data.

Each site gets its own MCP endpoint. Access is read-only: AI tools can search, list and read published pages. They can't change anything.

What it's good for

• Developers get answers from your docs inside Cursor, VS Code or Claude Code, without leaving their task.

• Customers ask the AI tool they already use and get answers for their product version, instead of opening a support ticket.

• Teams building their own assistant or agent use your published content as its source, with the model and behavior they choose.

Turn on MCP access for a site

1. In Scroll Sites, open the site and go to Site settings › Search and AI.

2. Under MCP access, turn on Let AI tools access your site.

3. Save your changes. Scroll Sites updates the site. When the update is finished, the MCP endpoint is live.

4. Copy the MCP endpoint URL with the copy button. Share it, or let visitors find it on any article (see below).

MCP access is off by default and is set per site. It's independent of the search experience you choose (Keyword search, AI search or AI assistant), and it doesn't use your OpenAI API key: the visitor's own AI tool does the reasoning.

Your MCP endpoint URL

The endpoint is your site URL plus /mcp: https://docs.example.com/mcp

• Use the URL exactly as shown, with no trailing slash.

• Opening the URL in a browser doesn't show anything useful. It's meant for AI tools.

How visitors find the endpoint

When MCP access is on, every article gets a Connect with MCP option in the Use with AI menu. With the AI assistant experience on, you'll find Use with AI next to the Ask AI button.

Clicking Connect with MCP copies the site's MCP endpoint URL, so visitors can paste it straight into their AI tool. When you turn MCP access off, the option disappears.

Connect your AI tool

Your AI tool needs the site's MCP endpoint URL. No sign-in or API key is needed. Pick your tool:

claude mcp add --transport http example-docs https://docs.example.com/mcp

{
  "mcpServers": {
    "example-docs": {
      "url": "https://docs.example.com/mcp"
    }
  }
}

{
  "servers": {
    "example-docs": {
      "type": "http",
      "url": "https://docs.example.com/mcp"
    }
  }
}

npx -y mcp-remote https://docs.example.com/mcp

What AI tools can do with your site

AI tools only get what visitors already see on your public site. Scroll Sites checks your site's visibility settings on every request, using the same configuration as the website itself. AI tools can't write, change or delete content, and nothing is stored between requests.

Try prompts like these once you're connected:

• Using the Example Docs connector, how do I set up single sign-on? Link the pages you used.

• Search the docs for version 3.0 and summarize what changed for admins.

• I'm writing a config file in this project. Check the docs for the supported options before you suggest anything.

Usage limits

To keep your site fast and stop the endpoint from being used for bulk downloads, Scroll Sites limits how many MCP requests it accepts:

• A request is rejected as soon as either limit is reached. The AI tool gets a "too many requests" error (HTTP 429) with standard rate-limit headers, so it knows when to try again.

• Normal use stays well below these limits. Answering a question usually takes a search and a few page reads.

• People who connect through the same company network or VPN can share one IP address, and with it the same limit.

Known limitations

• Public sites only. Support for protected sites (token access and single sign-on) is planned.

• Reading full pages depends on your AI tool. Some tools only use search results and don't open full pages yet.

• Help Center theme only for the Connect with MCP option on articles. The endpoint itself works regardless of theme.

FAQ and troubleshooting

Last updated: November 06, 2026