NameIO
Sign inSee your AI visibility

Connect your AI assistant (MCP)

Connect the AI assistant you already use to NameIO, then ask it to do your research from there: keyword research, SERP and local results, domain and backlink analysis, rank tracking, AI visibility checks, and your Google Search Console and Google Analytics data. It reads your NameIO projects and, when you allow changes, can save keywords, prompts, reports, project setup and draft page fixes back to them, where they show up in the app.

NameIO is a remote MCP server at https://app.getnameio.com/mcp. You add the server to your client, sign in, and choose whether the assistant may make changes.

NameIO doesn't run AI on its own key. Your assistant does the reasoning; NameIO supplies the data and stores what the assistant saves.

Paste the setup prompt

NameIO's setup prompt tells your agent how to add the server, sign you in and check the connection.

  1. In NameIO, open Agent setup from the AI Tools group in the sidebar.
  2. Click Copy setup prompt.
  3. Paste it into your agent and follow its instructions.
  4. Approve the connection when NameIO asks. See "Approve the connection" below.

The agent finishes by running whoami and list_projects to confirm the connection. It doesn't create projects or run paid research during setup.

The same prompt is on the last onboarding step, Set up your agent, which shows Connected once an agent connects and then continues to the dashboard. That step, the dashboard's Connect your AI agent step and the Agent setup page also show the server URL with a copy button and, below it, the Claude steps.

In Claude (claude.ai and Claude Desktop) and ChatGPT, you add the connector yourself, using the steps for your client below rather than the setup prompt's.

Claude Code

  1. Add the server:

    claude mcp add --transport http nameio https://app.getnameio.com/mcp

    This uses Claude Code's default local scope. Add --scope user to use it across all your projects, or --scope project to write it to the project's .mcp.json.

  2. In Claude Code, run /mcp, select nameio and follow the browser steps to sign in. claude mcp login nameio does the same.

  3. Approve the connection in NameIO.

To use an API key instead of signing in, add it as a header:

claude mcp add --transport http nameio https://app.getnameio.com/mcp --header "Authorization: Bearer nio_your_key"

Don't combine a key with --scope project, which would write it into a file in your repository.

Codex CLI

  1. Add the server:

    codex mcp add nameio --url https://app.getnameio.com/mcp

  2. Start sign-in, then sign in to NameIO in your browser and approve the connection:

    codex mcp login nameio

  3. In the Codex TUI, run /mcp and check that nameio is listed.

Codex saves the server as a [mcp_servers.nameio] table in its configuration, which the Codex IDE extension also uses. To use an API key instead of signing in, keep the key in an environment variable and name that variable in bearer_token_env_var:

[mcp_servers.nameio]
url = "https://app.getnameio.com/mcp"
bearer_token_env_var = "NAMEIO_API_KEY"

Cursor

  1. Open ~/.cursor/mcp.json to add NameIO to all your projects, or .cursor/mcp.json in a project to add it there only.

  2. Add a nameio entry next to any servers already listed:

    {
  "mcpServers": {
    "nameio": {
      "url": "https://app.getnameio.com/mcp"
    }
  }
}

  3. Cursor supports OAuth for servers that require it. Sign in to NameIO when asked and approve the connection.

You manage MCP servers from Cursor's Customize page. To use an API key instead of signing in, read it from an environment variable in a header:

{
  "mcpServers": {
    "nameio": {
      "url": "https://app.getnameio.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:NAMEIO_API_KEY}"
      }
    }
  }
}

Claude (claude.ai and Claude Desktop)

Custom connectors work in Claude, Cowork and Claude Desktop on the Free, Pro, Max, Team and Enterprise plans. On Free you can add one custom connector. Claude reaches NameIO from Anthropic's cloud, not from your computer.

On an individual plan:

  1. Open Customize > Connectors, click + Add, then Add custom connector.
  2. Enter the name NameIO and the URL https://app.getnameio.com/mcp, click Continue, review the detected authentication settings and click Continue again.
  3. For sign-in, choose Sign in now or Sign in when needed.
  4. For the OAuth client, keep Use Claude's published identity (Recommended). Claude then identifies itself with a Client ID Metadata Document that Anthropic publishes, and NameIO's consent page shows the site it was read from. Register automatically also works; it registers a new OAuth client with NameIO each time you connect.
  5. Click Add.
  6. When Claude sends you to NameIO (during setup with Sign in now, or the first time you use the connector with Sign in when needed), sign in and approve the connection.
  7. In a chat, click + in the lower left, open Connectors and turn on NameIO.

On an individual plan, if you can't use sign-in and your dialog shows Request headers (a beta that only some accounts have), choose No sign in, add an authorization header and enter Bearer followed by your NameIO API key.

On Team and Enterprise, an Owner adds the connector under Organization settings > Connectors (Add, then Custom, then Web) with the URL above; either OAuth client choice works. Each member then clicks Connect and signs in to their own NameIO account.

ChatGPT

OpenAI offers full custom MCP servers on the Business and Enterprise/Edu plans; Pro accounts can connect one with read and fetch permissions only. On Business, only admins and owners can add them. On Enterprise/Edu, admins and owners can, and so can members given the Create plugins with MCPs permission. You add custom MCP servers in ChatGPT on the web.

  1. On chatgpt.com, open Plugins (chatgpt.com/plugins).
  2. Click the plus button, then Add custom MCP server.
  3. Enter the name NameIO. The description is optional.
  4. Under Connection, enter https://app.getnameio.com/mcp.
  5. For authentication, choose OAuth.
  6. Tick I understand and want to continue, then click Create as a plugin.
  7. Review the tools ChatGPT found and install the plugin. When ChatGPT sends you to NameIO, sign in and approve the connection.
  8. Start a new conversation, type @, select NameIO and send: "Use NameIO to check my connection and list my projects."

By default, ChatGPT asks you to confirm write actions, and it treats every tool not marked read-only as one. Many NameIO tools, including whoami, research_keywords and get_serp_results, aren't marked read-only, so ChatGPT asks before running them too. You can approve a tool for the rest of a conversation; a new conversation asks again.

Other MCP clients

Add NameIO as a remote Streamable HTTP MCP server at https://app.getnameio.com/mcp using your client's current documentation, and sign in with OAuth. If the client can't complete the sign-in, use an API key.

Approve the connection

When your client starts sign-in, NameIO opens in your browser. If you aren't signed in, click Continue with Google first. NameIO then shows the consent page, Authorize MCP access.

  1. Check the details. An app with a published identity shows the site its identity document was read from (for Claude Code, claude.ai) and the name it calls itself; otherwise the app's name is provided by the app and not verified. Then check where access is sent and the account you're signed in as. Only continue if you started this connection yourself.
  2. Read any warning. If access goes to a program on your computer, any program running there could receive it. If it goes to an app on your device through a custom link type, any app registered for that link type could receive it.
  3. Review the access. Read your NameIO data and run lookups is always included: projects, AI visibility results, keywords, reports and audits. Lookups use your organization's credits.
  4. If the app asked to make changes, Make changes is listed with a switch beside it, on by default. Turn it off to connect read-only.
  5. Click Authorize.

Check the connection

Ask your assistant: "Use NameIO to check my connection and list my projects." It runs whoami and list_projects, which use no credits.

whoami returns your account email, Mode: hosted, your scopes and the credits left in your current organization. On a read-only connection, the scopes don't include mcp:write.

In NameIO, Settings → Personal → Connected apps lists each assistant you connected through sign-in, with its access (Read and change or Read only) and the date it connected. An app with a published identity is listed by the site it was verified against. For API keys, the API keys table shows when each key was last used.

Read only or read and change

A read-only connection can read your saved data and run lookups, which still use credits. It can't create, change or delete anything saved, or start checks and audits. NameIO hides the change tools from read-only connections and refuses them if called by name.

With the Make changes switch on, the assistant can also:

To turn a read-only connection into one that can make changes, disconnect it under Settings → Personal → Connected apps, then connect again from your client and leave the Make changes switch on.

If an app asks only for read-only access, the consent page says so and shows no switch.

Use an API key

Use an API key when your client can't complete the OAuth sign-in.

  1. In NameIO, open Settings from the account menu at the bottom of the sidebar (https://app.getnameio.com/settings).
  2. On the Personal tab, under API keys, click Create API key.
  3. Enter a name of up to 32 characters, such as "Claude Code on laptop", and click Create.
  4. Copy the key. It starts with nio_ and isn't shown again.
  5. Put the key in your client's secret settings or an environment variable, never in a chat or a repository. Have the client send it to https://app.getnameio.com/mcp as Authorization: Bearer nio_.... An x-api-key: nio_... header also works.

A key has full read-and-change access. It works only with the MCP server and doesn't sign you in to the NameIO app. It doesn't expire; it works until you revoke it. The API keys table lists each key's name, its first characters, when it was created and when it was last used.

Organizations

One connection covers every NameIO organization you belong to, whether you connect through sign-in or an API key. When you have more than one, list_projects labels each project with its organization. NameIO checks on every call that you're a member of the project's organization. If you leave every organization, the connection stops working.

What to ask first

If you have no projects yet, the assistant asks for your website and creates a project. A good first task is to have it set up that project: it studies your website itself and saves a business overview, up to 5 competitors, topics with 5 buyer prompts each, and suggested keywords. Saving also schedules weekly AI tracking for the first three topics; on the Pro plan the first check, which uses credits, runs about a week later. Creating and saving need a connection with Make changes on.

Then try: "Use NameIO to show which buying questions AI assistants answer with my competitors instead of me."

For several sites, the NameIO dashboard has a prompt that sets up a separate project for each website you list. It asks the assistant to list your existing projects first and reuse matches, so it doesn't create duplicates.

AI visibility checks cover four engines. ChatGPT and Gemini answers are captured from the apps through DataForSEO. Google AI Overviews come from Google search results through DataForSEO. Perplexity answers come from its API through DataForSEO and can differ from what the app shows. The quick setup in NameIO onboarding tracks ChatGPT on the free plan and all four on the Pro plan. See AI visibility.

Draft a fix for my store

When AI recommends a competitor for a buying question you track, your assistant can draft a change to one of your store's pages and save it in NameIO for you to review. Try: "Use NameIO to find a question where AI recommends a competitor instead of me, and draft a fix for the page that should win it."

Saving a draft needs a connection with Make changes on. A read-only connection can read the brief and the list of fixes, and NameIO tells the assistant to use Copy a prompt in the app instead. Fix is available on hosted NameIO only. It uses no credits and runs no AI model, and drafts are free on every plan.

How it works:

  1. The assistant calls get_fix_brief. Without a page, the brief lists the questions where the latest check found a competitor recommended instead of you, ranked by how many engines you lost, with the competitors named, the domains AI cited and the pages to consider. With a page, it also includes what that page says today.
  2. NameIO reads that page once with a plain request, from your own store. If your store refuses the request, NameIO uses the title and meta description from your latest site audit and marks the claims as not checked.
  3. The assistant writes the fix itself, shows you the text and, once you agree, saves it with propose_page_fix. A fix targets 1 to 5 of your tracked questions and can change one page's title, meta description, one new section and up to 8 questions and answers. The page must be on your project's domain. There is one open draft per page, and up to 50 open drafts per project. To change a draft, ask the assistant to revise it; the revision replaces the draft.
  4. Open Fixes in the sidebar, under AI Visibility. The review page shows, top to bottom:
    • Check before you use this text: every claim NameIO can't find on your page, such as prices, ratings and reviews, numbers and statistics, awards and certifications, superlatives, health and environmental claims, guarantees and policies, and named competitors. It also flags a title or description longer than search results show. Copy a revision request lists them so you can send them back to your assistant.
    • What changes: what the page says now next to the proposed text, with a copy button and a character count for each field.
    • Why: the assistant's reasoning. NameIO doesn't check it.
    • What NameIO saw: what it read on your page, and for each targeted question the engines where you lost, who they recommended and what AI cited, taken from your latest check.
    • Structured data (built by NameIO): NameIO builds the FAQ structured data from the questions and answers, and Product structured data for a product page that has none. Where your page already has that data, NameIO says so instead of adding it. It never adds ratings or reviews, and it adds a price only when it read one on your page. Your assistant can't send structured data.
    • How to apply it in Shopify: the steps for each part, with copy buttons. Structured data goes in a Custom Liquid section and needs an Online Store 2.0 theme; on an older theme, skip that step.
  5. Put it on your store, in one of two ways:
    • Publish to Shopify, for a product page. Connect Shopify once under Settings → Integrations; owners and admins can do this. The review page then reads the product from Shopify and shows the search title and meta description now and after, and the section and questions and answers that will be added at the end of the description, with character counts. Tick I checked the flagged claims if the fix has flags, then click Publish to Shopify. NameIO reads the product back from Shopify and shows when Shopify confirmed the change and which fields. It doesn't change the product title, price, variants, images, inventory or your theme.
    • Roll back puts each field back to how it was just before you published. A field you edited in Shopify since is left as it is, unless you tick Restore it anyway.
    • Paste each part into Shopify yourself, using the steps above. Then click Mark as applied, after ticking I checked the flagged claims if the fix has flags, or click Dismiss. Either can be undone with Back to draft. A published fix is undone with Roll back.

Your assistant sees only whether and when a fix was published (publishedToShopifyAt in list_page_fixes). Nothing NameIO reads from your Shopify store is sent to it.

NameIO checks claims with English wording rules. It flags what it can't find on your page and verifies nothing, so a claim that isn't flagged may still be wrong. Read the text before you use it.

If your assistant isn't connected to NameIO, you can still get a draft:

  1. Click Draft a fix on a question in the Competitor gap on Prompt Tracking, then choose Without an assistant. Copy a prompt on the Fixes page does the same for up to 5 questions.
  2. Choose the page, get the prompt and paste it into any assistant. The prompt holds the same brief for that page and asks for the changes in one JSON block.
  3. Paste the assistant's whole reply back into NameIO and save it. NameIO reads the last JSON block in the reply (a reply can be up to 30,000 characters) and applies the same rules as a connected assistant. If something can't be used, such as HTML or a link to another site, it says what to change. If the page already has a draft, NameIO asks before the reply replaces it, and the earlier draft is dismissed.

The draft opens on the same review page, marked Pasted reply.

See what changed after a fix

After you click Mark as applied or publish the fix to Shopify, the fix's review page shows Before and after at the top, and your assistant can read the same numbers with get_fix_impact. Try: "Use NameIO to show what changed after my fix for the running-shoes page."

It shows what changed after you marked the fix applied, not why. For a fix published from NameIO, the comparison starts when NameIO published it; for one you marked applied, it starts when you clicked, which may not be when the change went live. AI answers vary from check to check.

NameIO reads Search Console and Analytics from Google each time you open the page, using your own connection, and your browser reuses a result for 10 minutes. Reading uses no credits.

Moving the fix back to draft, or rolling it back, clears its before and after, and applying it again starts over. If another fix for the same page or questions was applied after the Before check, the page says so: the checks after it reflect both.

In Fixes, the Results column shows where each applied fix's checks stand. It reads "Day 7 from" a date until the Day 7 check opens, then Day 7 due or Day 7 checked, and the same for Day 28; under a Day 7 status it also says when Day 28 opens. A draft or a dismissed fix shows a dash. The column goes by when finished checks started, so a check of other questions also reads checked; the review page has the counts for the fix's own questions.

get_fix_impact returns the same numbers, including Search Console and Analytics for the page and the whole store. It uses no credits, starts no check and is on hosted NameIO only. It gives your assistant rules for describing the numbers: quote the counts and dates, give the whole store's number beside the page's, use a percentage only where it is given, say when numbers are small, and never say the fix is the reason for a change. To recheck, the assistant asks you first and uses the existing tools.

Share the results of a fix

Share results, at the top of Before and after, writes the results as a page for someone who isn't in NameIO. It asks first and tells you that anyone with the link can see the page. Click Share and NameIO saves the page in Reports as "Fix results: /products/x (as of Oct 22, 2026)" and shows its /s/ link with a copy button.

The page holds what changed (the new text, and the page's old title and description when NameIO read them), the page check, the AI answers with where each came from, Search Console clicks, impressions and position, and Analytics sessions and sessions from AI assistants, with the whole store's beside the page's. It uses the review page's numbers and caveats, worded for a reader outside the store ("after the fix was marked applied"). It leaves out orders, revenue and your assistant's reason for the fix, and it has no scripts.

The page is a copy as of the day you shared it, and it is the one place NameIO keeps Google's numbers, until you delete the report. Click Share results again to update the same page; the link stays the same while it's shared. To stop sharing, open the report in Reports and turn off Public link. Sharing again after that makes a new link.

When you ask your assistant to send the results to someone, NameIO tells it to point you to Share results. It writes a report of its own with save_report, and shares it with set_report_sharing, only when you ask, and leaves orders and revenue out of anything it saves or shares.

Credits and plans

Lookups and checks use your organization's credits; reading saved data doesn't. 1,000 credits are worth $1. Pro is $54 a month or $499 a year, plus applicable tax, and both include $15 of usage credits each month.

These use no credits:

These use credits:

Typical costs, from the tool descriptions:

ToolTypical cost
research_keywordsAbout 54 credits per seed keyword at the default result limit
get_serp_resultsAbout 5 credits per keyword at the default depth of 20
get_domain_overview, get_domain_keyword_suggestionsAbout 100 to 300 credits
get_backlinks_overviewAbout 50 credits for a domain

How the assistant handles cost:

Prompt Explorer, Prompt Research, scheduled AI checks, rank checks, and tracking Gemini, Google AI Overviews or Perplexity need the Pro plan. Saving prompts uses no credits on any plan, and a one-off AI check needs only credits; on the free plan it must also fit in today's free daily budget, unless your top-up credits cover it.

On the free plan, each organization has a daily data budget of $0.25, and all free organizations also share a daily pool. The budget resets at 00:00 UTC. Calls paid with purchased top-up credits don't count against it.

Site audit crawling doesn't use credits. Lighthouse checks and JavaScript rendering in an audit do, and both need the Pro plan. On the free plan, an audit that asks for Lighthouse runs without it. See Site audit.

Disconnect an assistant or revoke a key

To disconnect an assistant you connected through sign-in:

  1. Open Settings → Personal → Connected apps.
  2. Open the app's row menu, click Disconnect and confirm.

The app loses access within a minute, and every token issued to it is revoked. To use it again, connect it again from the app.

To revoke an API key:

  1. Open Settings → Personal → API keys.
  2. Open the key's row menu, click Revoke key and confirm.

Clients using the key stop working. API keys don't appear under Connected apps.

Technical details

For client and agent developers.

What's not done