---
title: "Connect an AI client with MCP"
description: "Give Claude and other compatible clients secure, approved, read-only access to CrawlRaven data."
canonical: "https://crawlraven.com/docs/mcp-connections"
markdown: "https://crawlraven.com/docs/mcp-connections.md"
product: "CrawlRaven v2"
last_verified: "2026-08-19"
---

# Connect an AI client with MCP

> Give Claude and other compatible clients secure, approved, read-only access to CrawlRaven data.

This guide documents current CrawlRaven v2 behavior. UI labels are written exactly where relevant. Bounded Search Console rows are evidence, not guaranteed exhaustive totals.

## What an MCP connection does

CrawlRaven’s remote Model Context Protocol server lets a compatible AI client read the account, websites, Search performance, queries, pages, opportunities, target keywords, and approved timeline data you authorize. The client signs in through OAuth; you do not create or paste a Google token, browser cookie, or personal secret.

> **The connection is read-only:** Current MCP tools cannot edit targets, resolve opportunities, change billing, or update your Google accounts.

The endpoint shown in the app is `https://mcp.crawlraven.com/mcp`.

## Connect a compatible client

1. **Open MCP connections** — From the account menu, choose `MCP connections`, or open [the MCP page](https://app.crawlraven.com/mcp).
2. **Copy the endpoint** — Use Copy endpoint in the Remote MCP server section.
3. **Add a custom connector** — In Claude or another compatible client, add a remote Streamable HTTP MCP server and paste the endpoint.
4. **Sign in in the browser** — The client opens CrawlRaven’s authorization screen.
5. **Review and approve** — Check the client name, account, website when required, and requested read permissions before approving.
6. **Return to the client** — Let the redirect and token exchange finish. The CrawlRaven tools should then appear.

> **Only approve clients you trust:** Tool results are processed by the connected client and its model provider under their policies. Revoke experiments or old devices when you no longer need them.

## Understand free preview and paid access

| Access | Behavior |
| --- | --- |
| Free MCP preview | When enabled for the account: one pinned activated website, fixed 28-day Search performance, up to 50 Query, Page, Opportunity, or Target Keyword rows, no pagination, custom periods, or annotations, and 20 tool calls per account each UTC day. |
| Full MCP access | Available with eligible paid access; clients can use the broader approved read scopes and fetch additional pages when needed. |
| Role restriction | An account owner or member must approve a connection. A user without that permission can see that the account is eligible but cannot connect it. |

The account’s first free grant pins the preview website; another free grant cannot switch it. A connection approved under free preview also does not silently expand later. Reconnect the client after upgrading so you can review and approve broader access.

Continue with [Use the free MCP preview](/docs/mcp-free-preview) or [Use MCP with full access](/docs/mcp-full-access). Exact tool and OAuth details remain in the [MCP server reference](/docs/mcp).

## Try prompts and manage connected clients

Replace `[your site]` with the exact CrawlRaven site name or domain before pasting a prompt.

- “How did [your site] do in search over the last 28 days?”
- “Show the highest-priority active opportunities and explain the evidence behind the top three.”
- “Which target keywords have no planned target page yet?”
- “Find the pages that lost the most clicks and summarize what changed.”

Name the site in your prompt so the client can select the right website quickly. The MCP connections page lists active clients, when each was last used, and when access expires. Connections expire after 90 days.

1. **Find the client** — Open Connected clients and verify its name, account, and identity host.
2. **Select Revoke** — A confirmation control appears beside the client.
3. **Confirm** — The grant is invalidated for future requests and moves into Previous connections.