---
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-10-09T07:26:57.018Z"
---

The Nuxt SEO Pro MCP server exposes your Site data to an AI client. It has its own tool catalog. The server marks this transitional transport as deprecated. Prefer the CLI or public API for new integrations.

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

The server publishes OAuth discovery metadata at the endpoints below. Your client must complete authorization and consent before it can read Team data. If a client cannot complete OAuth, use the CLI or a client that supports a Team API token header.

For this protected endpoint, use OAuth in [ChatGPT](https://chatgpt.com) or Claude's remote connector UI. Use a supported coding client for Team API token headers.

### ChatGPT

1. Follow [OpenAI's current developer mode instructions](https://help.openai.com/en/articles/12584461-developer-mode-and-mcp-apps-in-chatgpt). Availability depends on your plan and workspace permissions.
2. Create an app under Settings > Apps.
3. Enter `https://nuxtseo.com/mcp/pro` and choose OAuth.
4. Complete authorization, approve the intended Team, and finish the tool scan.

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

Follow [Claude's remote connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp). Add `https://nuxtseo.com/mcp/pro` under Settings > Connectors, then complete authorization. Claude Desktop uses this connector flow too.

The server exposes discovery metadata. Successful discovery alone does not establish a completed authorization grant. 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](https://code.claude.com/docs/en/mcp):

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

For Cursor and Windsurf, follow the client's current remote HTTP configuration documentation. Do not use local Claude Desktop server JSON for a remote connector.

[VS Code with GitHub Copilot](https://code.visualstudio.com/docs/agents/reference/mcp-configuration) uses this configuration in `.vscode/mcp.json`:

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

[Gemini CLI](https://geminicli.com/docs/tools/mcp-server/):

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

[Codex CLI](https://developers.openai.com/codex/mcp):

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

Set `NUXTSEO_TOKEN` in the environment that starts Codex. Keep real tokens out of shared configuration files.

## What the tools reach

The transitional tool catalog includes:

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

Read tools accept any Team role with the required entitlement. Write tools need the `editor` or `admin` role. An OAuth grant also needs `mcp:write`.

A write tool called with a `viewer` token returns an authorization error. Check role and OAuth scopes before retrying.

## 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.