Skip to main content
Glama
Sign In

Google Search Console MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Google Search Console MCP server, with each action switched on or off per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/google-search-console-mcp-server
GitHub Stars
0
Server Listing
Google Search Console MCP Server
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation3/5

query_data and execute_action both serve as the final workflow step and share almost identical prerequisite instructions, so an agent could confuse querying data with executing an action. prompts_menu and query_contexts are more distinct, but the two final-step tools have overlapping framing.

Naming Consistency3/5

execute_action, query_contexts, and query_data follow a readable verb_noun pattern, but prompts_menu breaks that convention with a noun-style name. The set is still interpretable, but the mix is not fully consistent.

Tool Count5/5

Four tools is well-scoped for a workflow-based GSC server: one for context discovery, one for prompts, one for data queries, and one for action execution. Each tool has a clear workflow role rather than feeling redundant.

Completeness4/5

Generic query_data and execute_action tools, backed by query_contexts discovery, can cover most GSC data and action needs. The main gap is that prompts_menu only lists and retrieves prompts, with no create/update/delete operations for custom prompts.

Available Tools

4 tools
execute_actionGSC Execute ActionA
Destructive
Inspect

Execute GSC action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, site_url AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuGSC PromptsA
Read-only
Inspect

Access GSC prompt catalog with 4 operations:

  1. List Public Prompts: • request='menu' - No additional params needed • Returns: All public/system prompts available for Google Search Console

  2. List Custom Prompts: • request='menu', prompt_type='custom', workspace_id= • Returns: All custom prompts for the specified workspace

  3. Get Public Prompt Details: • request='prompt_details', prompt_id= • Returns: Full text/details of a public prompt

  4. Get Custom Prompt Details: • request='prompt_details', prompt_id=, is_custom=True, workspace_id= • Returns: Full text/details of a custom prompt

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsGSC Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Google Search Console data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, site_url, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataGSC Data QueryA
Read-only
Inspect

Query GSC data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, site_url AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • mcp-gsc-multi-account

      MattiooFR
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing multiple Google Search Console accounts through a single MCP server, providing tools for search analytics, quick win detection, period comparison, URL inspection and indexing, and sitemap management.
      MIT

    • gsc-mcp

      mikusnuz
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Google Search Console, URL Inspection & Indexing API — search analytics, sitemap management, and batch indexing
      13
      149 npm
      8
      MIT

    • mcp-google-search-console

      crunchtools
      A
      license
      A
      quality
      B
      maintenance
      Secure MCP server for Google Search Console. Query search analytics (clicks, impressions, CTR, position), manage sitemaps, inspect URL indexing status, and manage site properties.
      10
      AGPL 3.0

    • mcp-search-console

      apexradius
      A
      license
      A
      quality
      C
      maintenance
      Multi-account Google Search Console MCP server enabling AI assistants to query multiple GSC accounts by name in a single session, with support for OAuth and service accounts.
      17
      MIT
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources