Skip to content

Connect Cursor to Google Search Console

Connect Cursor to Google Search Console: 1. Connect Google Search Console in ApexGenius. 2. Add the ApexGenius MCP server. 3. Ask Cursor.

1,000 free credits · No card required

How to connect Google Search Console to Cursor

  1. 1Sign in to ApexGenius and connect Google Search Console
  2. 2Add the ApexGenius MCP server to Cursor
  3. 3Start using Google Search Console in Cursor
  1. 1ApexGenius

    Connect Google Search Console to ApexGenius

    Choose what it can reach

    Pick the accounts or properties your AI may use.

  2. 2ApexGenius

    Connect ApexGenius to Cursor

    Choose Cursor

    Back on Start, pick Cursor and copy the prompt.

  3. 3ApexGenius

     

    Approve access

    ApexGenius opens its approval page. Review the access, then approve.

Add the ApexGenius MCP server to Cursor

Cursor reads MCP servers from ~/.cursor/mcp.json for every project, or from .cursor/mcp.json inside one project. The Customize page manages the same servers.

  1. Add the apexgenius entry to mcpServers. Keep any servers already there.
  2. Open Customize in Cursor, find apexgenius and choose Connect.
  3. Approve ApexGenius in your browser.
Add to ~/.cursor/mcp.json
{
  "mcpServers": {
    "apexgenius": {
      "url": "https://server.autom8.pro/mcp"
    }
  }
}

Check it. Cursor lists a connected server’s tools under Available Tools. By default it asks for your approval before it runs one.

Steps follow Cursor documentation, Model Context Protocol (MCP) (opens in a new tab), read November 12, 2026.

Then ask Cursor

List the Google Search Console properties enabled for me in ApexGenius. Do not change anything.

Start free
Written setup, step by stepShow

Before you start

  • A Google account with access to an existing Search Console property.
  • The exact Domain or URL-prefix property you want to use. You can add a missing property with the connector’s Add property write tool. Verify ownership in Google Search Console when required.

1. Connect Google Search Console to ApexGenius

  1. Open Google Search Console in Connections. Sign in to ApexGenius, open Connections, and choose Google Search Console. Select Connect to begin Google authorization.
    ApexGenius Connections searched for Search Console, showing the Google Search Console row with its Connect button.
    Search Connections for Search Console and choose Connect on the Google Search Console row.Open full-size image (opens in a new tab)
  2. Choose the right Google account. Use the account that can already access your site in Search Console. Review the Google consent screen and continue back to ApexGenius.
  3. Enable your Search Console property. Find Allowed resources on the connection page or its Tools tab and choose Refresh. Turn on the exact property you want to use. A Domain property and a URL-prefix property are separate choices.
    Allowed resources in the Google Search Console settings sheet in ApexGenius, with the Refresh button and two sample properties.
    On the Tools tab, open Settings. Under Allowed resources, choose Refresh to find the properties the signed-in Google account can reach.Open full-size image (opens in a new tab)
    Two sample Search Console properties under Allowed resources, sc-domain:example.com switched on and a second property off.
    Turn on the property you want your AI to use. This capture shows a sample property; choose your own.Open full-size image (opens in a new tab)
  4. Check the connection and tools. Use Test connection and review the Read tools. Search performance, property details, sitemap details, and URL inspection are reads. Keep property and sitemap changes off if you only need reporting.
    The Google Search Console page in ApexGenius after you connect: the status control reads Connected, one account row shows when it was added and last checked, and the Tools, Agents and Skill rows follow.
    The Google Search Console page after you connect. The status control reads Connected and the account row shows when it was last checked. Open the status control for Check again.Open full-size image (opens in a new tab)
Connect Google Search Console →

2. Connect ApexGenius to Cursor

Use this server address when adding the connection:

https://server.autom8.pro/mcp

The steps are above, under Add the ApexGenius MCP server to Cursor. These notes apply to Cursor only.

  • No client ID or secret. Cursor signs in with OAuth and registers itself with ApexGenius, so mcp.json needs only the address.
  • Enterprise teams. An MCP allowlist can limit which server addresses run. If apexgenius does not connect on a team account, ask your Cursor admin to allow the ApexGenius address.
  • Turning it off. Enable or disable the server from Customize in the sidebar.
  • Access. When ApexGenius asks what Cursor may use, choose Read only for the first test, or Custom to limit it to the tools you need.

3. Verify one safe read

List the Google Search Console properties enabled for me in ApexGenius. Do not change anything.

List the Google Search Console properties enabled for me in ApexGenius. Do not change anything.

Confirm that the returned property matches the one you enabled. Then ask for its ten pages with the most clicks over a specific date range. Compare the property, dates, search type, clicks, and impressions with the Search Console Performance report.

Full guide: the Google Search Console setup guide.

What it looks like in Cursor

Illustration of a task, not a recorded customer result. Your answers come from the account and dates you choose.

How the route works
Cursor
CursorApexGenius MCP route
Which Google Search Console properties have I enabled in ApexGenius?
ApexGenius
Working with ApexGenius1 tool search · 2 reads
RequestChoose a property
Account scopeAuthorized connections checked
apex_search_toolsGoogle Search Console properties · Find Search Console property accessComplete
Search Consoleapex_call_read_toolgoogle_search_console_list_properties · List enabled propertiesComplete
Search Consoleapex_call_read_toolgoogle_search_console_get_property · Check the selected property’s permission levelComplete
Cursor

Example: sc-domain:example.com is enabled. Confirm that this is the site you want before requesting a report. Nothing was changed.

Read-only route
Cursor

What to ask Cursor about Google Search Console

  • Choose a property

    Which Google Search Console properties have I enabled in ApexGenius?

    Runs google_search_console_list_properties (read), then google_search_console_get_property (read).

  • Analyze performance

    Compare clicks and impressions for my selected property over the last two complete 28-day periods. Which pages gained or lost the most clicks?

    Runs google_search_console_query (read).

  • Find query opportunities

    Find queries with high impressions and low CTR for my selected property. Show their pages and average positions, then suggest what to review.

    Runs google_search_console_query (read).

  • Inspect a URL

    Inspect a URL I provide in my enabled Search Console property. Do not submit it for indexing.

    Runs google_search_console_inspect_url (read).

  • Review sitemaps

    List the sitemaps submitted for my selected property and summarize reported errors, warnings, and last download dates. Do not change anything.

    Runs google_search_console_list_sitemaps (read), then google_search_console_get_sitemap (read).

These 5 questions use 6 of Google Search Console’s 11 operations. The full list is below.

  • Which Search Console properties have I enabled in ApexGenius? Help me choose the right Domain or URL-prefix property. (read)
  • Inspect a URL I provide and explain the index status Google reports. Do not submit anything. (read)
  • List the sitemaps submitted for my selected property and summarize any reported errors, warnings, and last download dates. Do not change anything. (read)

What Cursor can do in Google Search Console

11 operations: 6 read, 5 write. Read looks things up and changes nothing. Writes change Google Search Console and run only when you turn them on.

Search Console operations

6 read · 5 write
  • google_search_console_list_propertiesread
  • google_search_console_get_propertyread
  • google_search_console_add_propertywrite
  • google_search_console_delete_propertywrite
  • google_search_console_queryread
  • google_search_console_inspect_urlread
  • google_search_console_list_sitemapsread
  • google_search_console_get_sitemapread
  • google_search_console_submit_sitemapwrite
  • google_search_console_delete_sitemapwrite
  • google_search_console_requestwrite

You choose the access. When you approve Cursor, pick Full access, Read only, or Custom.

Only properties accessible to the Google account and enabled in ApexGenius can be queried.

Use Read only when authorizing your AI client if you only need search reporting and URL inspection.

Compare the selected property, dates, search type, and returned metrics with Search Console before making a decision.

Adding or removing properties and changing sitemaps require Google write permission and allowed write tools. Adding a property does not verify ownership or enable it in ApexGenius.

Start free

Questions about connecting Cursor to Google Search Console

Updated November 12, 2026.

How do I connect Cursor to Google Search Console?

Connect Cursor to Google Search Console through ApexGenius in three steps. Sign in to ApexGenius and connect Google Search Console by signing in with Google and enabling your property. In Cursor, add an apexgenius entry with the ApexGenius MCP address to mcpServers in ~/.cursor/mcp.json, then choose Connect on the Customize page. Then open a task in Cursor and ask a question about your Google Search Console. Start with a read, so nothing changes.

How do I check that Cursor can use Google Search Console?

Open Customize in Cursor and find apexgenius among the MCP servers. Its tools should appear under Available Tools. If it is listed but not connected, choose Connect and finish the browser sign-in. On an Enterprise team, the MCP allowlist may need the ApexGenius address. Then ask: “List the Google Search Console properties enabled for me in ApexGenius. Do not change anything.”

Is there a Google Search Console MCP server for Cursor?

Yes. ApexGenius is an MCP server that Cursor connects to once. It carries your Google Search Console connection and 11 Google Search Console operations, so Cursor does not need a separate Google Search Console integration or plugin. You set it up one time and add each agent the same way.

What can Cursor do in Google Search Console once it is connected?

Cursor can run 11 Google Search Console operations through ApexGenius: 6 reads that list properties, query search performance, inspect URLs and list sitemaps, and 5 writes that add or delete properties and sitemaps, plus a general request tool, once you allow writes.

Can Cursor read my Search Console properties?

Only properties the Google account can access and you enable in ApexGenius. Domain and URL-prefix properties are separate choices, so enable the exact one. Check the returned property, dates and search type against Search Console before you decide anything. Adding a property is a separate write.

Can Cursor change my Google Search Console?

Not unless you turn on write tools. Search analytics and URL inspection are read only, and they do not request indexing or edit your website. Property and sitemap changes are separate writes you can leave disabled. Adding a property does not verify ownership.

Can I use the same Google Search Console connection with Claude, ChatGPT, Grok Bot or Muse?

Yes. One Google Search Console connection in ApexGenius works with every compatible agent you add, including Claude, ChatGPT, Grok Bot or Muse. Each agent gets its own access choice and its own short setup, so you can pick read only for one agent and more for another.

Connect Google Search Console to Cursor today

Start free

1,000 free credits. No card required. Disconnect any time.