Noma MCP Server: Your AI Visibility Data in Claude and Cursor

Noma by Nurdd runs an MCP server, so you can ask Claude, Claude Code or Cursor about your AI visibility and get answers from your own Noma data: scores, the AI answers that named you, your competitors and the questions where they appear and you do not. It is included on every paid plan, from Starter at $79 a month.

MCP (Model Context Protocol) is an open standard that lets an AI assistant call tools in other software. Instead of exporting a report and pasting it into a chat, the assistant asks Noma directly and works with the result.

What can you ask?

A few questions the tools below can answer:

• “How visible is my brand in AI answers today, and how has that changed this month?”
• “Which AI answers mentioned us this week, and what did they say?”
• “Which questions do AI engines answer with my competitors but not with us? Draft a brief for the top one.”
• “What is my site’s AEO readiness score, and what should I fix first?”
• “Re-check the prompt about pricing tools and tell me when it has run.”

Because the answer arrives inside your assistant, you can carry on from it: turn a content gap into an outline in Claude, or open the page that needs work in Cursor.

The 10 tools

“Reads” tools only read your workspace. The two “Runs” tools ask AI engines fresh questions, so they use your plan’s credits the way a run in the app does. Every tool carries the standard MCP safety labels (read-only, destructive, idempotent), so your client can tell which is which before it calls one.

How do you connect it?

1. In Noma, open Crawler activity, then Settings, and create an API key. It starts with noma_sk_. Treat it like a password.
2. Add the server to your client with the key as a bearer token, as below.
3. Ask a question about your visibility. The client lists Noma’s tools and calls the ones it needs.

Claude Code

claude mcp add --transport http noma https://platform.nomahq.app/api/mcp \
  --header "Authorization: Bearer YOUR_NOMA_KEY"

Cursor

Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "noma": {
      "url": "https://platform.nomahq.app/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_NOMA_KEY" }
    }
  }
}

Other clients

Any MCP client that can call a remote server over HTTP with a header can use the same URL and key. The server also supports OAuth 2.1 sign-in with dynamic client registration and publishes its metadata, for clients that connect that way. The key goes in the Authorization header only, never in the URL, so it does not end up in logs or browser history.

Is it safe to connect?

• No tool deletes or edits your projects, prompts or settings.
• Every tool that takes a project checks that the project belongs to the account whose key was used, and refuses otherwise.
• A key works only while its owner is still a member of the workspace, and a revoked key stops working at once.
• Only the two Runs tools use credits.

Which AI visibility tools include MCP?

Several AI visibility tools now offer MCP. This is where each vendor lists it, read on each vendor’s own pricing page on 3 November 2026, on monthly billing where the page offers a choice. Check the vendor’s page before you buy, as plans change often.

For prices, engines and prompt limits side by side, see every Noma comparison, including Profound alternatives and Peec AI alternatives.

What else connects to Noma?

Server logs come in by webhook, Vercel log drain or access-log upload, and your data goes out through CSV exports and, on higher plans, the Noma API. See all integrations, or compare plans to start.

This page is written by Noma by Nurdd. Other vendors’ plans were read on their own pricing pages on 3 November 2026.

← All integrations