export const metadata = {
  title: "MCP & AI agents: SEO Insight Docs",
  description:
    "Connect Claude, GPT and other agents to your SEO data through the built-in SEO Insight MCP server.",
};

# MCP & AI agents

SEO Insight ships a built-in **Model Context Protocol (MCP)** server, so AI
agents like Claude and GPT can read your keyword reservoir, inspect backlinks
and generate briefs, without you copy-pasting between tools.

## Connect the server

Add the SEO Insight MCP server to your agent's configuration. The server
authenticates with the same API key as the REST API.

```json
{
  "mcpServers": {
    "seo-insight": {
      "command": "npx",
      "args": ["-y", "@seo-insight/mcp"],
      "env": { "SEO_INSIGHT_API_KEY": "sk_live_xxxxxxxxxxxxxxxx" }
    }
  }
}
```

## What agents can do

Once connected, the agent can list tools and call them in a session:

```text
> claude mcp list
seo-insight: connected ✓ (12 tools, 3 resources)

> Find my SEO quick-wins (positions 11-20)
3 quick-wins found:
  • seo mcp tool      · pos. 12 · 880 vol/mo
  • seo mcp server    · pos. 14 · 320 vol/mo
  • seo api for agents · pos. 18 · 210 vol/mo
```

Available tools cover the reservoir (search and filter keywords), backlinks
(inspect the inbound profile) and content (generate and save briefs). Resources
expose the workspace's connected sources.

## Scopes

MCP access inherits the key's workspace scope. Use a read-only key for agents
that should only query data, and a read-write key for agents that create briefs.
See [Authentication](/docs/authentication) for the full scope model.
