SEOmonitor MCP connects your account to assistants such as Claude and ChatGPT.

MCP stands for Model Context Protocol, a standard for connecting AI assistants to external tools and data.

The connector is currently in beta and included in all paid SEOmonitor Pro subscriptions at no additional charge. It provides read access to tracked campaigns. Content Audit and draft campaigns are not available through the MCP.

You need access to a tracked campaign in SEOmonitor and an AI assistant that supports remote MCP connections. Your assistant's plan and workspace settings must allow custom connections. On a managed workspace, an administrator may need to enable access.

Data availability depends on your campaign. For example, AI Search analysis requires access to the relevant tracked LLM engine, and traffic analysis requires GSC/GA integrations connected

Use this server URL:

Complete SEOmonitor's sign-in, select your account, and approve read access. The current connection uses OAuth, so you do not need to copy an API key.

For Team and Enterprise workspaces, an owner first adds the connector under Organization settings → Connectors. Members then connect their own accounts. See Claude's custom connector guide for current availability and instructions.

Menu labels and availability can vary by account. OpenAI documents the current connection flow and personal plugin setup.
​

Add a remote MCP connection using the same server URL and complete the sign-in flow. Follow your assistant's setup instructions for remote servers and OAuth.
​

Start with a small request:
​

Use SEOmonitor to list the tracked campaigns I can access. Show the domain and market for each campaign.
​

Select the campaign you want to analyse. If you track the same domain in multiple markets, specify the market as well.
​

Then try:

For [campaign and market], show the latest available organic Visibility and the AI Search engines being tracked. State the date of the data and flag anything unavailable.
​

The available tools support several types of analysis:

The assistant uses the data returned by SEOmonitor to write its analysis. Recommendations are interpretations of that data, so ask it to show the keywords, pages, and metrics behind each conclusion.
​

Replace the text in square brackets before using a prompt. For comparisons, specify both date ranges and the device where relevant.
​

Use this for a monthly review or client meeting.

Using SEOmonitor, review [campaign and market] for [date range] against [comparison period]. Use [device] for Google rankings and AI Overviews. Summarise organic Visibility, AI Overview mentions and citations, and each tracked AI Search engine separately. Identify the keyword groups with the largest changes and show supporting keywords. Finish with three areas worth investigating. State any missing data or incomplete comparisons.
​

A good Google ranking and an AI citation are different signals. This prompt helps identify where they diverge.

For [campaign], find tracked keywords in [group] where we rank in Google's top 10 on [device] but our website is not cited in the AI Overview on [date]. Only include keywords with an AI Overview. Show our ranking page, rank, cited competitor pages, and whether our brand is mentioned. Separate competing brands from publishers and other sources.
​

Use the results to choose pages for closer review.

For [group] in [campaign], find topics where [competitor domain] is cited in AI Overviews and our site is not on [date and device]. Verify each example at keyword level. Show the competitor's cited URL, our current ranking URL, our rank, and our citation status. Identify existing pages worth reviewing.

Citation data can identify a gap. Assessing whether page structure, coverage, or another factor explains it requires reviewing the pages themselves.

A brand can be named without its website being cited, and a website can be cited without the brand being named.

For [campaign] in [tracked AI Search engine] on [date], group the checked keywords into: mentioned and cited, mentioned only, cited only, and neither. Show the keyword count and examples for each group, including citation URLs where available.

Use this to investigate Reddit, YouTube, industry publications, or another source domain.

For [campaign and keyword group] in [tracked AI Search engine] during [date range], find answers citing [source domain]. Show the keyword, cited URL, observation date, and whether our brand is mentioned in that same answer. Keep observations from different dates separate.

This examines sources cited within the campaign's tracked results. It is not a complete search of everything published on that source website.

For [campaign], identify tracked keywords ranking in positions 4–20 on [device]. Group them by topic and show search volume, current rank, and ranking page.

Suggest a shortlist based on relevance to [business priority]. If research is available for this campaign's market, also find relevant keywords that [competitor] ranks for and we do not track. Keep tracked opportunities and research suggestions separate.

Research tools currently support campaigns in the US, UK and Romania. The campaign determines the research market.

Compare total organic traffic for [campaign] in [date range] with [comparison period]. Also show brand and non-brand traffic separately where available. Identify keywords associated with the largest changes and compare their rankings over the same periods. Distinguish observed changes from possible explanations, and flag missing traffic data.

Specify total organic, brand, or non-brand explicitly. The traffic tools default to non-brand when no segment is selected.

Retrieve the current Objective and existing forecast scenarios for [campaign]. Summarise the targets, assumptions, and available progress data. Show the keyword-level forecast detail for the main opportunities. Label forecasts separately from actual results and state where progress cannot be assessed from the available data.

This retrieves and explains existing forecasting data. Treat a new scenario suggested in the conversation as an analysis proposal until it has been created in SEOmonitor.

I cannot add the connector. Check whether your assistant supports custom remote MCP connections on your plan and whether your workspace permits them. If the option is unavailable, contact your workspace administrator.

The assistant cannot find my campaign. Confirm the account selected during sign-in and ask it to list all accessible tracked campaigns. Include the campaign's market when several campaigns share a domain.
​

An AI Search returns no data. Check whether the AI Search add-on is enabled and accessible for that campaign before interpreting the result. Missing access and missing tracking are different from no mentions or citations.
​

The numbers differ from SEOmonitor. Match the campaign, group, date, device, engine, traffic segment, and metric.
​

You can reuse the same prompt for regular reviews. Scheduling it, creating alerts, saving a report to Google Sheets, or creating a CRM record requires the relevant capabilities and connections in your AI assistant. The SEOmonitor connection supplies the data; connecting it does not automatically schedule reports or grant access to other applications.

Contact customer.success@seomonitor.com. Include the assistant you use, campaign, prompt, date range, and any error message so the team can investigate.