Use Nuwtonic from Codex, Cursor, Claude, or another MCP client

MCP lets an assistant call Nuwtonic for you: Search Console data, GEO audits, on-page SEO audits, content fixes, articles, prompt tracking, and reports.

Open MCP Settings from the account menu. Copy the MCP URL there, and have an organization admin generate the bearer token. The token is locked to the domain you choose on that page.

You do not need an organization id or a workspace id. The token already belongs to that domain.

If you only need the product screens, start with the User Guide. Search Console tools also need Google Search Console connected for that site.

1. Before you start

Check these before you connect a client. Each missing item blocks a later step.

1. You are signed in to the organization you want the assistant to use.
2. That organization has at least one workspace, and the workspace has a site URL. MCP Settings shows No domain when the URL is missing. Add the site URL on the workspace, then refresh MCP Settings.
3. You can open that workspace. If the list says no workspace is available to you, ask an organization admin to give you access, then refresh the page.
4. An organization admin is available to generate or revoke the token.
5. For Search Console tools, the property is already connected in Nuwtonic.
6. For publishing or applying fixes, the CMS or webhook integration for that workspace is already connected.

MCP does not create organizations or workspaces. Create them in Nuwtonic first.

2. What MCP Settings gives you

Each organization has one active bearer token. It is locked to the domain you choose on this page. The other workspaces in the organization do not get their own token.

The MCP URL on the page is the one to paste. It is normally https://api.nuwtonic.com/mcp. If the page shows a different URL, paste that one.

3. Generate the token

1. Open MCP Settings.
2. Choose the domain this token may use.
3. Enter a short label you will recognize later, such as Codex or Claude. The label can be at most 80 characters.
4. Click Generate token.
5. Copy the bearer token and the Authorization value before you leave the page.

The token cannot be shown again. Click I have copied the token only after it is saved in the client. If you did not copy it, revoke the token and generate a new one.

A second token is blocked while one is active. Revoke the active token first, then generate the next one. Revoking stops that client immediately.

If the active token points at a workspace that is no longer in the organization, revoke it, choose a current domain, and generate a new token.

4. Connect Codex

Codex CLI, the Codex IDE extension, and the ChatGPT desktop app share this configuration.

The token itself belongs in an environment variable. The config file stores only the variable name. Codex sends it as Authorization: Bearer <token>. Put the raw token in the variable, without the word Bearer.

Windows (current PowerShell window):

$env:NUWTONIC_MCP_TOKEN = "paste-the-bearer-token"

Start Codex from that same window. A new window does not keep this value. To keep it for new windows, set NUWTONIC_MCP_TOKEN in Windows environment variables, then open a new terminal.

macOS or Linux:

export NUWTONIC_MCP_TOKEN="paste-the-bearer-token"

Add the server in ~/.codex/config.toml (on Windows, %USERPROFILE%\.codex\config.toml):

[mcp_servers.nuwtonic]
url = "paste-the-mcp-url"
bearer_token_env_var = "NUWTONIC_MCP_TOKEN"

Or from a terminal where the variable is already set:

codex mcp add nuwtonic --url "paste-the-mcp-url" --bearer-token-env-var NUWTONIC_MCP_TOKEN

Restart Codex after you save the config. In the Codex terminal UI, /mcp lists the server. If Codex says the environment variable is not set, the variable is not visible to the Codex process. Set it again in the environment that launches Codex, then restart Codex.

5. Connect Cursor

Cursor reads ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project. Do not commit the token. A project file should use an environment variable.

Global file (%USERPROFILE%\.cursor\mcp.json on Windows):

{
  "mcpServers": {
    "nuwtonic": {
      "url": "paste-the-mcp-url",
      "headers": {
        "Authorization": "Bearer paste-the-bearer-token"
      }
    }
  }
}

Project file that you might commit:

{
  "mcpServers": {
    "nuwtonic": {
      "url": "paste-the-mcp-url",
      "headers": {
        "Authorization": "Bearer ${env:NUWTONIC_MCP_TOKEN}"
      }
    }
  }
}

Save the file and restart Cursor. The header value must start with Bearer , then one space, then the token from MCP Settings. The Authorization value field on that page is already in that form.

6. Connect Claude Desktop

Claude Desktop, Claude on the web, and the Claude mobile apps use the same connector. Claude calls Nuwtonic from Anthropic's servers, so paste the public MCP URL from MCP Settings.

1. Open Claude Desktop.
2. Go to Customize → Connectors.
3. Add a custom connector:
   • On Pro or Max, click + Add, then Add custom connector.
   • On Team or Enterprise, an owner adds it first from Organization settings → Connectors → Add → Custom → Web. A Free plan can add one custom connector.
4. Name it Nuwtonic.
5. Paste the MCP URL and continue.
6. Under Authentication, choose No sign in.
7. Under Request headers, add one header. Name it Authorization. For the value, paste the Authorization value from MCP Settings. It already starts with Bearer and a space.
8. Click Add.

Open a chat, click +, open Connectors, and turn Nuwtonic on. If the toggle is off, Claude cannot use Nuwtonic in that chat.

If you are on Team or Enterprise and you are not an owner, wait until Nuwtonic appears under Customize → Connectors, then click Connect. On those plans the Authorization header is shared by everyone who uses the connector. Add it only for people who should use this Nuwtonic workspace.

To replace the token, remove the connector and add it again. Claude does not edit a connector in place.

If Nuwtonic does not connect, check three things, then remove it and add it again:

• The URL is the MCP URL from MCP Settings, normally https://api.nuwtonic.com/mcp.
• Authentication is No sign in.
• The header name is Authorization, and the value is the Authorization value, not the raw token alone.

7. Sign in instead of pasting a token

Some clients offer Sign in instead of a pasted token.

• Codex: run codex mcp login nuwtonic after the server URL is configured.
• Cursor: add the MCP URL without a bearer header, then use the server's sign-in.
• Claude: when you add the connector, choose Sign in now instead of No sign in, and leave the Authorization header empty.

Use the email on your Nuwtonic account. Nuwtonic emails a 6-digit code. Enter that code. It expires in 10 minutes.

That sign-in can use the workspaces linked to that email. It is separate from the MCP Settings token, which stays locked to the one domain you chose. If sign-in does not finish, use the bearer token instead.

If the signed-in email cannot open the workspace, the tool says so. Sign in with the Nuwtonic account that can open that workspace, then try again.

8. What to ask for

Ask for the outcome in plain language. Name the site when you need to, using the domain from MCP Settings, such as example.com, without https:// and without a path.

You do not paste organization ids, workspace ids, website ids, or job ids. The token already selects the workspace. When a job is still running, the tool tells the assistant what to check next.

Give both a start date and an end date when you want a range. Dates are YYYY-MM-DD, for example 2026-10-01. Leave both empty when you want the tool's usual period.

9. Tools

Google Search Console

Connect Search Console first. If it is not connected, these tools cannot return performance data.

Ask for clicks, CTR, position, trends, a page snapshot, a breakdown, or the rows for a page, query, device, or country.

GEO audit

Ask for a GEO / AIO audit of one or more page URLs. When it finishes, ask for the results or for the PDF of one page that was already audited.

This checks the AIO / GEO audit permission. If it is off, the tool tells you the next step. Turn that permission on for the workspace, then run the audit again.

A lifetime plan can audit one URL per request. Ask for the next URL in a new request.

Content and SEO fixes

Ask for fix analysis or generated SEO fixes for page URLs on the domain you chose. Ask to apply those fixes only after the CMS or webhook for that workspace is connected.

Generate and analyze check the content fix generate permission. Apply checks the content fix apply permission. See the WordPress, Shopify, Webflow, Ghost, or webhook guide for that workspace.

A lifetime plan can analyze one URL, or generate fixes for one URL, per request.

Articles

Ask for a new article on the domain you chose. A standard article needs the keyword or keywords to write about. A lifetime plan can use one keyword per request.

Ask to publish it, or to save it as a draft. The CMS or webhook must already be connected. Generate and publish both check the content generation permission.

On-page SEO audit

Ask for one page URL to audit now, or for several page URLs at once. A single-page audit finishes in the reply. A bulk audit runs in the background; ask again for the stored results when it finishes.

A one-page audit does not depend on the scheduled on-page automation switch.

Lifetime plans cannot run a bulk audit. Ask for one page URL, then ask again for the next page.

Prompt tracking

Ask to list, add, change, remove, or run prompts that are already part of prompt tracking for your domain. These tools do not create a workspace.

To add a prompt, give the wording. Each prompt is at most 2,000 characters. If you set a country, use a 2-letter code such as US or GB, not the country name.

You can set how often a prompt is checked: daily, every 3 days, weekly, every 15 days, monthly, or only when you ask.

A successful run uses one monthly prompt check. A prompt checked in the last 10 minutes is skipped. Asking how many checks a run will use does not use a check. If the monthly quota is used up, the tool says so. Change the prompts or wait for the quota to reset.

Reports

Ask for one of these:

• The prompt tracking report
• The GEO audit PDF for one page that was already audited
• The on-page SEO audit PDF for the site, or for one page URL
• The client review across search, SEO, GEO, and prompt tracking

A site SEO PDF uses the latest bulk or sitemap crawl. Run that audit first. The PDF does not apply any fixes.

If a part of the client review has no data, the result names that part and the reason. Fix the missing data, or ask for the report with the parts that are ready.

A saved download link expires in one hour. If it does not open, ask for the report again and use the new link.

A GEO or SEO PDF comes back in the reply when the file is 1.5 MB or smaller. A larger PDF is described, not attached. Ask for one page URL, or open the report in Nuwtonic.

When a permission blocks the work

The tool says which permission is off, and what to turn on. These are the switches:

Turn that switch on, then ask again.

10. Lifetime plans

A lifetime plan can run one item at a time from MCP for content generation, GEO audit, on-page SEO audit, and advanced fix.

The tool names the limit and tells you to send one item, then ask again. Prompt tracking is not part of this limit.

11. When something fails

The tool result says what to fix. Use that sentence. These are the cases you will see:

12. What MCP does not do

These stay in Nuwtonic. Do not expect an MCP tool for them:

• Creating an organization, a workspace, or a user
• Showing the bearer token again after you hide it
• Issuing a second active token for another workspace in the same organization
• Keyword research, rank tracking outside prompt tracking, brand visibility, and brand analysis
• Performance Ask AI, GA4, Bing, analytics exports, lead-gap snapshots, and brand work plans
• Credit balance
• Quota top-ups and the prompt-tracking schedule

If you need another workspace, revoke the current token and generate a new one for that workspace. The previous client stops working when you revoke it.