---
title: "MCP"
description: "Connect ChatGPT, Claude, or an editor to your Nuxt SEO Pro Site data over MCP."
canonical_url: "https://nuxtseo.com/docs/nuxt-seo-pro/guides/mcp"
last_updated: "2026-09-23T04:45:05.144Z"
---

The Nuxt SEO Pro MCP server exposes your Site data to an AI client. It reads the same server operations as the CLI and the API.

Use MCP when your client cannot run a terminal. If your client has a terminal, use the [CLI](/docs/nuxt-seo-pro/guides/cli) instead. The CLI has exit codes and pipes, so a script can act on a result.

## Endpoint

| Field     | Value                                                       |
| --------- | ----------------------------------------------------------- |
| URL       | `https://nuxtseo.com/mcp/pro`                               |
| Transport | Streamable HTTP                                             |
| Auth      | OAuth 2.1, or a Team API token in an `Authorization` header |

## Connect with OAuth

::note
The OAuth authorization server has not shipped yet. The paths below record its shipping shape, so you can prepare the connector configuration ahead of the deploy. Until then, use a Team API token.
::

OAuth is the only auth a [ChatGPT](https://chatgpt.com) connector or a [Claude.ai](http://Claude.ai) connector accepts. Neither UI lets you attach a header.

### ChatGPT

1. Open Settings, then Connectors.
2. Choose Create.
3. Enter `https://nuxtseo.com/mcp/pro` as the MCP server URL.
4. Choose OAuth as the authentication method.
5. Approve the Team on the consent screen.

### [Claude.ai](http://Claude.ai)

1. Open Settings, then Connectors.
2. Choose Add custom connector.
3. Enter `https://nuxtseo.com/mcp/pro` as the remote MCP server URL.
4. Approve the Team on the consent screen.

Both clients discover the rest. The server publishes RFC 9728 metadata at `/.well-known/oauth-protected-resource/mcp/pro` and RFC 8414 metadata at `/.well-known/oauth-authorization-server`. Client registration is dynamic, so there is no client ID to copy.

Protocol endpoints:

| Purpose   | Path                   |
| --------- | ---------------------- |
| Authorize | `/pro/oauth/authorize` |
| Token     | `/pro/oauth/token`     |
| Register  | `/pro/oauth/register`  |

Scopes:

| Scope            | Grants                                                          |
| ---------------- | --------------------------------------------------------------- |
| `mcp:read`       | Every read tool. Required. Without it the endpoint stays closed |
| `mcp:write`      | Write tools, on top of the role check below                     |
| `offline_access` | A refresh token                                                 |

A grant is scoped to one Team, not to one user. Your role is read from live membership on every request, so a demoted member loses write access at once.

## Connect with a Team API token

Mint a token under Settings, then API tokens. A token starts with `nsp_`. Send it as `Authorization: Bearer <token>`{lang="html"}.

Claude Code:

```sh
claude mcp add nuxt-seo-pro https://nuxtseo.com/mcp/pro \
  --transport http \
  -H "Authorization: Bearer nsp_your_token"
```

Cursor, Windsurf, and Claude Desktop:

```json
{
  "mcpServers": {
    "nuxt-seo-pro": {
      "url": "https://nuxtseo.com/mcp/pro",
      "headers": { "Authorization": "Bearer nsp_your_token" }
    }
  }
}
```

GitHub Copilot:

```json
{
  "servers": {
    "nuxt-seo-pro": {
      "type": "http",
      "url": "https://nuxtseo.com/mcp/pro",
      "headers": { "Authorization": "Bearer nsp_your_token" }
    }
  }
}
```

Gemini CLI:

```json
{
  "mcpServers": {
    "nuxt-seo-pro": {
      "httpUrl": "https://nuxtseo.com/mcp/pro",
      "headers": { "Authorization": "Bearer nsp_your_token" }
    }
  }
}
```

Codex CLI:

```toml
[mcp_servers.nuxt-seo-pro]
url = "https://nuxtseo.com/mcp/pro"

[mcp_servers.nuxt-seo-pro.http_headers]
Authorization = "Bearer nsp_your_token"
```

## What the tools reach

Tools cover the Site features the dashboard shows:

- Next Actions, Sprint Tickets, and Page Issues
- Organic Search rows and Search Indexing diagnostics
- Lighthouse scans, Core Web Vitals, and their findings
- Crawl changes, duplicate clusters, and internal link structure
- Keyword research, competitors, backlinks, and mentions
- Content Briefs and content decay
- Site list and account usage

Read tools work for any role. Write tools need the `editor` or `admin` role on the Team. An OAuth grant also needs the `mcp:write` scope.

A write tool called with a `viewer` token names the token role and the tool in the error, so the fix is clear.

## Revoke access

Revoke a Team API token under Settings, then API tokens. Revoking stops the CLI, the API, and any MCP client using that token.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.