Is this an official Google Search Console MCP server?

No. It is Memtro's MCP server with Memtro's Google Search Console connector behind it: the connector reads Google Search Console through its API with the credentials you connect on Dashboard → Connections, and Google Search Console publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Google Search Console?

Not yet. Today every Google Search Console tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Analytics

Google Search Console MCP server

Google Search Console in any MCP client, through Memtro: Google Search Console does not publish this server. Memtro's Google Search Console connector reads Google Search Console through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only Google Search Console: search queries, clicks, impressions, CTR and position by page, country, device or date, sitemap status and URL index inspection for the properties the Google account can see (uses the same Google OAuth client as Gmail).

Reads

gsc_sitesList the Search Console properties (siteUrl and permission level) this connection can report on.
gsc_search_analyticsGoogle Search performance for a property: clicks, impressions, CTR (ratio) and average position, optionally broken down by query, page, country…
gsc_sitemapsSitemaps submitted for a property: path, type, when last submitted and downloaded by Google, URL counts…
gsc_inspect_urlInspect one URL in Google's index (URL Inspection API): indexing verdict, coverage state, robots.txt and indexing state, last crawl time…

Connect it

First connect Google Search Console on Dashboard → Connections, then add Memtro to your client once. The Google Search Console tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Google Search Console connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Which search queries brought the most clicks last month?
› What is our average position for 'company memory' and is it improving?
› Which pages have high impressions but a low click-through rate?
› Is https://www.memtro.com/pricing indexed, and what is the canonical?

Questions

Is this an official Google Search Console MCP server?: No. It is Memtro's MCP server with Memtro's Google Search Console connector behind it: the connector reads Google Search Console through its API with the credentials you connect on Dashboard → Connections, and Google Search Console publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Google Search Console?: Not yet. Today every Google Search Console tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.