GSC MCP Core

io.github.glq0546Published by GitHub account glq0546v1.0.0Updated Nov 1, 2026

Multi-tenant GSC data fetcher for AI agents. OAuth secured.

The publisher's own server: core.blue

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote, OAuth-secured MCP endpoint that lets an AI assistant fetch Google Search Console data for multiple tenants.

What you can do
  • Fetch Google Search Console data on behalf of an assistant, per tenant.
  • Serve multiple tenants from one remote endpoint.
  • Authenticate access through OAuth before any data is retrieved.
  • No tool list is published, so the exact queries and reports available are not documented.
When to use it
Use it when you want an assistant to pull Google Search Console performance data for one or more properties or clients without building your own integration, and you are comfortable with an OAuth-based remote service.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. OAuth authentication is required, so the user must authorize access to their Google Search Console data. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to Search Console data, which can include private site performance and query information; review what scopes are requested. The server is multi-tenant, so confirm how tenant separation and data handling work before connecting client accounts. No tool list or documentation is provided, so behavior cannot be verified in advance.

Installation

In SourceWeft

  1. Open GSC MCP Core in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.glq0546%2Fgsc-mcp-core/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gsc-core": {
      "type": "http",
      "url": "https://gsc-mcp-core.vercel.app/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Core integrations