Loading...
searchstack.dev
Sign In

Let AI answer from your pages

The same searchable list has a second consumer. Everything you make searchable for people is, from the same import, available to AI agents — over MCP, with nothing extra to build.

What MCP gives you

MCP (Model Context Protocol) is the standard way an AI agent plugs into an outside tool. Search Stack runs an MCP server, so any MCP-capable agent — Claude, or your own — can use your reference list as a retrieval tool: it searches your pages and answers from what it finds, instead of guessing. This is the difference between an assistant that makes things up about your product and one that reads your actual docs.

Crucially it's the same list you just built — nothing re-imported, no second copy of your data. Make your data searchable once; your users and your agents both use it.

Connect an agent

Point an MCP client at the Search Stack MCP server and give it a read-only key scoped to your list. In an agent's MCP configuration that's one server entry:

{
  "mcpServers": {
    "searchstack": {
      "url": "https://mcp.searchstack.dev/",
      "headers": { "X-API-Key": "YOUR_READ_ONLY_KEY" }
    }
  }
}

The key is a read-only one (search-result:read), scoped to the reference list — so the agent can search these pages and nothing else. With that connected, the agent gains Search Stack's search tools and can answer questions grounded in your site:

You: How do I change a field without breaking apps that already use my search?

Agent: Renaming or removing a field creates a new version, while the old version keeps working, so existing apps aren't affected… — drawn from your Versioning page, which the agent found by searching your reference list.

Because the agent searched rather than guessed, its answer traces back to a real section of a real page — the url on each result is the citation. You can try this shape of thing in the console Playground, which is an agent reading your account's data over this same MCP server.

Go deeper: The Playground — an agent reading your data over MCP in the reference.

Top