Skip to content
Back to the index

google_search_console

pipeworx.ioInfrastructure

PulseGate's liveness check found it on 3 Oct 2026; it has been in the index since 22 Aug 2026. How this is checked

Google Search Console MCP Server exposes four JSON-RPC tools for connected Search Console accounts. Developers and automation systems can list properties and sitemaps, query search analytics, and inspect URL indexing status.

Inferred · not functionally tested

WebAPICloud-managed
google_search_console preview
Visit pipeworx.io
1alternative
8features
2026since

Overview

6 features

Purpose: Accessing Google Search Console site and search-performance data programmatically through MCP tools.

Inferred · not functionally tested

Audience: developers and SEO automation builders

Inferred · not functionally tested

Functions: data_extraction, analytics

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

In the API design, testing & docs space, google_search_console takes a focused approach. Inferred · not functionally tested: It focuses on accessing Google Search Console site and search-performance data programmatically through MCP tools. Inferred · not functionally tested: It is built as a B2B product for developers and SEO automation builders. Basis unknown · not verified: It ships for the web and API.

It is developed by Pipeworx. Inferred · not functionally tested: Key capabilities include List Search Console sites, search analytics queries, and list submitted sitemaps. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • List Search Console sites
  • Search analytics queries
  • List submitted sitemaps
  • Inspect URL indexing
  • JSON-RPC endpoint
  • MCP integration

Topics: Inferred · not functionally tested

Tags
google-search-consolemcp-serverseo-data-apisearch-performance

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCP
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed22 Aug · 01:00 UTC
    Google_search_console seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about google_search_console

What does google_search_console do?
Inferred · not functionally tested: Google_search_console focuses on accessing Google Search Console site and search-performance data programmatically through MCP tools. It is catalogued under API design, testing & docs on PulseGate.
Who should use google_search_console?
Inferred · not functionally tested: google_search_console is a B2B product built for developers and SEO automation builders.
What platforms does google_search_console run on?
Basis unknown · not verified: google_search_console runs on the web and API.
Is google_search_console still active?
PulseGate's liveness check found it on 3 Oct 2026.
What are alternatives to google_search_console?
Similar projects tracked by PulseGate include Google Search Console MCP, Google Search Console MCP Server, and Google Search Console MCP.Google Search Console MCPGoogle Search Console MCP ServerGoogle Search Console MCP
Who develops google_search_console?
google_search_console is developed by Pipeworx.
Does google_search_console have an API or integrations?
Inferred · not functionally tested: Yes — google_search_console exposes an MCP server.

Similar projects

Closest matches by what these projects do