# Connect your AI assistant (/ai/connect)

PeekRank has an **MCP server**: the standard way AI assistants connect to apps. Once connected, you can ask your
assistant about your rankings, keywords, competitors and AI visibility in plain words, and it answers from your own
PeekRank data. It can also run research for you, within limits you set.

You sign in with your PeekRank account: there's no key to copy, and you can disconnect any time. The MCP server is
in beta.

Jump to yours: [Claude](#claude-web-desktop-and-mobile) · [ChatGPT](#chatgpt) · [Claude Code](#claude-code) ·
[Codex](#codex) · [Cursor](#cursor) · [VS Code](#vs-code-github-copilot) · [Other clients](#other-clients) ·
[API key](/ai/access/#api-keys)

**Server URL:**

```text
https://app.peekrank.io/mcp
```

## Fastest: one command

If you have Node.js, this sets PeekRank up in every assistant on your computer (Claude Code, Codex, Cursor, VS Code,
Windsurf, Gemini CLI and more). Each one asks you to sign in with PeekRank the first time you use it.

```bash title="Terminal"
npx add-mcp https://app.peekrank.io/mcp -g -n peekrank
```

It uses the open-source [add-mcp](https://github.com/neon-solutions/add-mcp). Add `-a claude-code` (or another agent)
to set up only some.

## Claude (web, desktop and mobile)

<Steps>
<Step>
In Claude, open [Customize → Connectors](https://claude.ai/customize/connectors) and click **Add custom connector**.
</Step>

<Step>
Name it **PeekRank**, paste the server URL and click **Add**.
</Step>

<Step>
Click **Connect**, sign in to PeekRank, pick the workspace and what Claude can do, and click **Allow**.
</Step>
</Steps>

Added once, PeekRank shows up in Claude on the web, in Claude Desktop and in the mobile apps, and in Claude Code when
you're signed in with the same Claude account. On Team and Enterprise plans, an Owner adds it in **Organization
settings → Connectors**, then each member clicks **Connect**. Claude's Free plan allows one custom connector.

## ChatGPT

<Steps>
<Step>
Turn on **Developer mode**: **Settings → Security and login → Developer mode** (Plus, Pro, Business, Enterprise and
Edu plans).
</Step>

<Step>
In **Plugins**, click **+** to create an app: name **PeekRank**, the server URL, authentication **OAuth**.
</Step>

<Step>
Sign in to PeekRank and approve. In a chat, pick **Developer mode → PeekRank** from the **+** menu.
</Step>
</Steps>

ChatGPT asks you to confirm every billed tool before it runs.

## Claude Code

```bash title="Terminal"
claude mcp add --transport http --scope user peekrank https://app.peekrank.io/mcp
```

Then sign in: run the command below, or type `/mcp` inside Claude Code, pick **peekrank** and **Authenticate**. Your
browser opens the PeekRank sign-in.

```bash title="Terminal"
claude mcp login peekrank
```

`--scope user` makes PeekRank available in every project, not only the current folder.

## Codex

For the Codex CLI, the IDE extension and the desktop app (they share the same configuration):

```bash title="Terminal"
codex mcp add peekrank --url https://app.peekrank.io/mcp
codex mcp login peekrank
```

Codex opens the PeekRank sign-in as soon as you add it; the second command signs in again whenever you need to (another
account, an expired session).

## Cursor

[Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=peekrank&config=eyJ1cmwiOiJodHRwczovL2FwcC5wZWVrcmFuay5pby9tY3AifQ%3D%3D), or add this to `~/.cursor/mcp.json`:

```json title="~/.cursor/mcp.json"
{
  "mcpServers": {
    "peekrank": {
      "url": "https://app.peekrank.io/mcp"
    }
  }
}
```

Cursor asks you to sign in to PeekRank the first time it connects.

## VS Code (GitHub Copilot)

[Install in VS Code](vscode:mcp/install?%7B%22name%22%3A%22peekrank%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapp.peekrank.io%2Fmcp%22%7D), or from a terminal:

```bash title="Terminal"
code --add-mcp '{"name":"peekrank","type":"http","url":"https://app.peekrank.io/mcp"}'
```

VS Code opens the PeekRank sign-in when you start the server.

## Other clients

Any MCP client that supports remote servers works (Windsurf, Zed, Gemini CLI, Goose…): add the server URL as a
**streamable HTTP** server. PeekRank uses the standard MCP sign-in (OAuth 2.1 with PKCE, with dynamic client
registration and client ID metadata documents), so the client opens the sign-in by itself.

For scripts, CI or clients that can't sign in, an owner or admin can create an **API key** instead. See
[Sign-in, API keys and access](/ai/access/#api-keys).

## What you approve when you connect

When you sign in, PeekRank asks:

![PeekRank's consent screen: the workspace, what the assistant can do, and the optional workspace management](/screenshots/consent.webp)

*The consent screen an assistant opens the first time (sample data).*

- **Workspace**: which of your workspaces the assistant works on. It acts as you there, with your role and your projects.
- **What it can do**:
  - **Read only**: projects, positions, changes, history, saved runs, AI visibility, your workspace and team. It never
    bills or changes anything.
  - **Read + run billed tools**: also fetch fresh data (research, overviews, rank checks, backlinks, audits, AI checks)
    and set up tracking. Each call states its price before it runs and is paid from the workspace's balance, within its
    limits.
- **Workspace management** (only if you're an owner or admin of that workspace): tick **Also manage the workspace** to
  let it invite teammates as members or remove them, change which projects they see, create or revoke public report
  links, change report branding and revoke connected apps. It never makes anyone an admin. Leave it off unless you need
  it.

Then click **Allow**. You can see and disconnect your connections any time in **Settings → Developers & AI**. More in
[Sign-in, API keys and access](/ai/access/).

## Check it works

Ask your assistant: *"List my PeekRank projects."* It should answer with your projects. Then try the
[recipes](/ai/recipes/).

| If | Then |
|---|---|
| The assistant doesn't see PeekRank | Check the server URL, then restart the assistant or start a new chat. |
| It asks you to sign in again | Sessions renew while you use them; after a long break, sign in again from the assistant. |
| A billed tool is refused | Your connection may be read-only, or a limit was reached. See [Spending limits for assistants](/ai/spending-limits/). |
| You don't see a tool listed in [MCP tools](/reference/mcp-tools/) | Some tools only appear for some connections. See [who sees which tools](/ai/access/#which-tools-your-assistant-sees). |