> ## Documentation Index > Fetch the complete documentation index at: https://docs.seomator.com/llms.txt > Use this file to discover all available pages before exploring further. # MCP server: connect Claude, ChatGPT and more > Add SEOmator to Claude, ChatGPT, Claude Code, Cursor or VS Code through MCP, and see every tool it can use to read and change your projects. Add SEOmator to the AI tool you already use, so the tool can read your projects and run SEOmator tools through MCP (Model Context Protocol). ## Before you start * You need a SEOmator account in at least one organization. * Find your tool's setup line: in the sidebar, click **MCP**. The **MCP clients** section on the [Integrations](https://docs.seomator.com/settings/integrations.md) page lists each supported tool with its URL or command and a **Copy** button. ![The Integrations page with a Copy button on each MCP client row and the Connected apps list](https://mintcdn.com/se-omator/LHKLDWeFBDdpYX2o/images/integrations.light.png?fit=max\&auto=format\&n=LHKLDWeFBDdpYX2o\&q=85\&s=c2be8589eac46b5a8e881276ba186950) The server URL is: ```text theme={null} https://api.seomator.com/mcp ``` ## Add SEOmator to your tool > [tab] Claude > > **1. Copy the URL** > > On the Integrations page, click **Copy** in the **Claude** row. > > **2. Add a connector** > > In Claude, add a custom connector with this URL. > > **3. Sign in** > > Sign in to SEOmator when Claude asks, then [approve the > connection](#approve-the-connection). > [tab] ChatGPT > > **1. Copy the URL** > > On the Integrations page, click **Copy** in the **ChatGPT** row. > > **2. Add a connector** > > In ChatGPT, add a connector with this URL. > > **3. Sign in** > > Sign in to SEOmator when ChatGPT asks, then [approve the > connection](#approve-the-connection). > [tab] Claude Code > > **1. Copy the command** > > On the Integrations page, click **Copy** in the **Claude Code** row. > > **2. Run it** > > Run the command in your terminal: > > ```bash theme={null} > claude mcp add --transport http --scope user seomator https://api.seomator.com/mcp > ``` > > **3. Sign in** > > In Claude Code, run `/mcp` and sign in to SEOmator. > > **4. Approve** > > [Approve the connection](#approve-the-connection) in your browser. > [tab] Cursor > > **1. Add it** > > On the Integrations page, click **Add to Cursor**. Cursor opens and adds > SEOmator. > > **2. Sign in** > > Sign in to SEOmator when Cursor asks, then [approve the > connection](#approve-the-connection). > [tab] VS Code > > **1. Add it** > > On the Integrations page, click **Add to VS Code**. VS Code opens and > adds SEOmator. > > **2. Sign in** > > Sign in to SEOmator when VS Code asks, then [approve the > connection](#approve-the-connection). Another MCP client that supports remote servers can use the same URL. ## Approve the connection When you sign in from your tool, SEOmator opens an **Authorize** page in your browser. **1. Check the account** Check the email you're signed in with. To use a different account, click **Use another account**. **2. Choose the organization** Under **Organization**, choose the organization the tool may use. A connection works with one organization only. **3. Allow it** Read what the tool can do, then click **Allow**. To refuse, click **Deny**. The tool is connected and shows under **Connected apps** on the Integrations page. It stays connected while you use it. A connection can read the organization's projects, reports and AI answers. If it also asks to make changes, it can change projects, prompts and competitors, as your role allows. ## Connect with an API key Scripts and tools that can't sign in through the browser can use an organization API key instead. **1. Create a key** Create a key on the [API keys](https://docs.seomator.com/settings/api-keys.md) page. **2. Point the client at the key endpoint** Set the client's server URL to `https://api.seomator.com/mcp/key`. **3. Send the key** Send the key in the `x-api-key` header, or as `Authorization: Bearer `. The client can now use SEOmator tools with the key's access. A read-only key can only use read tools. ## Try it Copy a prompt into your tool to check the connection with your own data. Everything your tool can do is listed in [MCP tools](#mcp-tools). In my SEOmator project, how often do ChatGPT, Google AI Mode and Gemini name my brand, and how does that compare with my competitors? In my SEOmator project, how often do ChatGPT, Google AI Mode and Gemini name my brand, and how does that compare with my competitors? Which domains and pages do the AI answers in my SEOmator project cite most? Which domains and pages do the AI answers in my SEOmator project cite most? ## MCP tools Once your AI tool is connected, it works in SEOmator through these tools. You don't call them by name: ask a question and the tool picks the ones it needs. The [agent](https://docs.seomator.com/agent/overview.md) inside SEOmator uses the same tools. Read tools work with every connection. Write tools need a connection you allowed to make changes, or a **Read and write** API key, and a role that allows the change. What each role can do: [Members](https://docs.seomator.com/settings/members.md). ### Read tools | Tool | What it returns | | - | - | | **List projects** `list_projects` | The projects the connection can open, newest first. | | **Get project** `get_project` | One project. | | **AI visibility report** `get_visibility_report` | How often ChatGPT, Google AI Mode and Gemini name each tracked brand, with the counts behind each [metric](https://docs.seomator.com/reports/metrics.md). | | **Sources of AI answers** `get_cited_sources` | The domains or pages the answers read and cite, by site or page type, or by day, week, assistant, topic or prompt. | | **List collected AI answers** `list_answers` | The answers, newest first, with the brands each one names, its source and citation counts and the start of its text. | | **Read one AI answer** `get_answer` | The full text of one answer, the brands it names in order, and its sources. | | **List tracked brands** `list_brands` | Your own brand and your competitors, with their aliases and domains. | | **List suggested competitors** `list_brand_suggestions` | Up to 20 brands the answers name that you don't track yet, with how many answers name each and one quote. | | **List tracked prompts** `list_prompts` | The prompts asked every day, newest first. | | **Read one tracked prompt** `get_prompt` | One prompt's text, intent, topic and status, and whether it names your brand. | | **List topics** `list_topics` | The topics your prompts are grouped under. | | **List Google keywords** `list_keywords` | The Google searches the project follows, with monthly volume, your Google position and ranking URL, and Search Console clicks. | | **Query Google Search Console** `query_search_console` | Clicks, impressions, CTR and average position, grouped by query, page, country, device, search appearance or date. | | **Inspect a URL in Google** `inspect_url` | Whether one page is indexed and why not, its last crawl, and the canonical Google chose against the one the page declares. | | **List submitted sitemaps** `list_sitemaps` | The sitemaps in Search Console, when Google last read them, how many URLs they list, and their warnings and errors. | The last three tools need Search Console connected to the project: [Connect Google Search Console](https://docs.seomator.com/getting-started/projects.md#connect-google-search-console). ### Write tools | Tool | What it changes | | - | - | | **Track a new prompt** `create_prompt` | Adds a prompt that is asked every day from now on. | | **Edit a tracked prompt** `update_prompt` | Changes a prompt's text, intent or topic. | | **Stop tracking a prompt** `archive_prompt` | Stops asking a prompt. Its past answers stay in the reports. | | **Track an archived prompt again** `reactivate_prompt` | Asks an archived prompt again from the next run. | | **Add a topic** `create_topic` | Adds a topic to group prompts under. | | **Rename a topic** `rename_topic` | Renames a topic. Its prompts and reports stay the same. | | **Track a brand** `create_brand` | Starts tracking a brand, as a competitor by default, with its domains and aliases. | | **Edit a tracked brand** `update_brand` | Changes a brand's name, aliases or domains. | | **Track a suggested competitor** `accept_brand_suggestion` | Tracks a suggested brand as a competitor. | | **Hide a suggested competitor** `dismiss_brand_suggestion` | Hides a suggested brand. | When a tool starts tracking a brand or changes its name or aliases, SEOmator recounts it in your past answers. > [!WARNING] > > A prompt added over your plan's daily allowance runs on credits. What it > costs: [Plans and credits](https://docs.seomator.com/getting-started/plans.md#credits). ## If it doesn't work * The page says "This consent link is not valid": start the connection again from your tool. * The page says to create an organization first: create one in SEOmator, then connect again. * The tool lost access: it may have been disconnected or unused for too long. See [Integrations](https://docs.seomator.com/settings/integrations.md), then connect it again. ## Related > [card] [Integrations](https://docs.seomator.com/settings/integrations.md) > > See and disconnect the apps you approved. > [card] [API keys](https://docs.seomator.com/settings/api-keys.md) > > Create keys for scripts and MCP clients. > [card] [AI SEO Agent](https://docs.seomator.com/agent/overview.md) > > Ask the same questions inside SEOmator. > [card] [Metrics](https://docs.seomator.com/reports/metrics.md) > > What the numbers in a visibility report mean. ## Related topics - [Frequently asked questions](https://docs.seomator.com/getting-started/faq.md) - [Integrations: MCP clients and connected apps](https://docs.seomator.com/settings/integrations.md) - [API keys: connect scripts and MCP clients](https://docs.seomator.com/settings/api-keys.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.