Skip to content

Add GSC PAP MCP - #627

Open
aliarifsoydas wants to merge 3 commits into
Kilo-Org:mainfrom
aliarifsoydas:add-gsc-pap
Open

aliarifsoydas wants to merge 3 commits into
Kilo-Org:mainfrom
aliarifsoydas:add-gsc-pap

Conversation

@aliarifsoydas

Copy link
Copy Markdown

Adds mcps/gsc-pap/MCP.yaml, a hosted remote MCP in the same shape as the Anaconda OAuth entry.

  • What it does: read-only Google Search Console, GA4 and PageSpeed Insights for the user's own sites, plus live Google results. 38 read-only tools; Search Console history is archived past Google's 16-month limit.
  • Install: Streamable HTTP at https://mcp.gscpap.com/mcp. No parameters or secrets: the client signs in with OAuth (PKCE S256, dynamic client registration), which goes through Google sign-in (webmasters.readonly, plus analytics.readonly for GA4).
  • Category: data
  • Official MCP Registry id: com.gscpap/gsc-pap · Site: https://gscpap.com · Docs: https://github.com/aliarifsoydas/gsc-pap-claude-plugin

Real use case: SEO and content teams asking their assistant for quick wins, decaying pages or Search Console pages joined to GA4 conversions without setting up a Google Cloud project. Submitted by the maintainer.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Comment thread mcps/gsc-pap/MCP.yaml Outdated
pages joined to GA4 conversions and real-user Core Web Vitals, with a Search Console archive kept past Google's 16-month
limit.
author: GSC PAP
url: https://gscpap.com

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: url points to the marketing landing page, not the MCP server repository/docs

CONTRIBUTING.md defines url as the link to the MCP server repository. This entry asks users to grant a third-party OAuth server access to their private Search Console/GA4 data, so the catalog link should let them inspect the operator and source before authorizing. The PR body names the public docs repo but the listing does not link it. Use the repository/docs URL (e.g. https://github.com/aliarifsoydas/gsc-pap-claude-plugin) or a docs page that documents the OAuth scopes and data handling.

Comment thread mcps/gsc-pap/MCP.yaml
url: https://gscpap.com
category: data
prerequisites:
- Google account with Search Console access

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Prerequisite omits GA4 access

The description advertises GA4 conversions and joins, but the only account prerequisite is Search Console access. A user with Search Console but no GA4 property access will install successfully and then hit permission errors on the GA4 tools. Add the GA4 requirement, for example Google Analytics 4 property access (for the GA4 tools).

@kilo-code-bot

kilo-code-bot Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 1
Issue Details (click to expand)

SUGGESTION

File Line Issue
mcps/gsc-pap/MCP.yaml 13 Bing tools are advertised, but the listing never explains how a Bing Webmaster Tools API key reaches the hosted server, and the install config has no parameters or headers for one
Files Reviewed (1 file)
  • mcps/gsc-pap/MCP.yaml - 1 suggestion

Unverified by static review

  • Network access is blocked in this sandbox, so Bing support, the https://mcp.gscpap.com/mcp endpoint, the OAuth scopes, and the "16-month" Search Console/Bing archive claim could not be exercised. Confirm the Bing tools are live and that any Bing key is collected and stored without appearing in logs or tracked files.
  • The PR body still describes only Google Search Console/GA4, 38 tools, and Google OAuth scopes; it does not mention Bing. Update it so consent and scope expectations match the listing.

Fix these issues in Kilo Cloud

Previous Review Summaries (2 snapshots, latest commit 96a37c6)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 96a37c6)

Status: No Issues Found | Recommendation: Merge

The incremental changes resolve both prior findings: url now links the project repository (https://github.com/aliarifsoydas/gsc-pap-claude-plugin) and the GA4 access prerequisite was added. The entry remains a valid hosted-OAuth remote MCP (streamable-http, no secrets, data category, id matches directory name). No new issues on the changed lines.

Files Reviewed (1 file)
  • mcps/gsc-pap/MCP.yaml

Previous review (commit 3b7ab9c)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 1

The new mcps/gsc-pap/MCP.yaml follows the hosted-OAuth remote-MCP shape used by existing entries (streamable-http, no secrets, valid data category, id matches directory). Two metadata/provenance gaps are flagged inline. The PR's claims that could not be verified statically are noted below as unverified rather than as findings.

Issue Details (click to expand)

WARNING

File Line Issue
mcps/gsc-pap/MCP.yaml 8 url is the marketing landing page, not the server repository/docs, so users cannot inspect the operator before granting OAuth access to Search Console/GA4 data

SUGGESTION

File Line Issue
mcps/gsc-pap/MCP.yaml 11 Prerequisites omit GA4 property access even though the listing advertises GA4 tools

Unverified by static review

  • The endpoint https://mcp.gscpap.com/mcp and the "read-only" / "38 tools" / "Official MCP Registry id com.gscpap/gsc-pap" claims in the PR description were not exercised; a maintainer should confirm the endpoint responds and the OAuth scopes are limited to webmasters.readonly and analytics.readonly before merging.
  • Generated catalog (mcps/marketplace.yaml) is not included, but the Generate Marketplace workflow regenerates and commits it, so this is not treated as a defect.
Files Reviewed (1 file)
  • mcps/gsc-pap/MCP.yaml - 2 issues

Fix these issues in Kilo Cloud


Reviewed by deepseek-v4.1-flash-1017 · Input: 88.7K · Output: 13.3K · Cached: 736.3K

Review guidance: REVIEW.md from base branch main

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aliarifsoydas

Copy link
Copy Markdown
Author

Both review points are addressed: url now points to the public repo (https://github.com/aliarifsoydas/gsc-pap-claude-plugin), which documents the OAuth scopes and data handling, and GA4 property access is listed as a prerequisite for the GA4 tools.

Comment thread mcps/gsc-pap/MCP.yaml
prerequisites:
- Google account with Search Console access
- Google Analytics 4 property access (for the GA4 tools)
- Bing Webmaster Tools account (optional, for the Bing tools)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Document how the Bing credential is supplied

Bing Webmaster Tools API access uses a per-user API key generated in Bing Webmaster Tools; Bing does not offer OAuth for that API. This listing only adds an account prerequisite, and the hosted streamable-http content has no parameters or headers for a key. If the new Bing tools need a key the user must provide, add it to prerequisites (plus a parameters entry if the client must pass it). Otherwise state that the key is connected in the gscpap.com dashboard so the expected setup is clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant