Repository navigation
Add GSC PAP MCP - #627
Add GSC PAP MCP#627aliarifsoydas wants to merge 3 commits into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
| 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 |
There was a problem hiding this comment.
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.
| url: https://gscpap.com | ||
| category: data | ||
| prerequisites: | ||
| - Google account with Search Console access |
There was a problem hiding this comment.
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).
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (1 file)
Unverified by static review
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: Files Reviewed (1 file)
Previous review (commit 3b7ab9c)Status: 2 Issues Found | Recommendation: Address before merge Overview
The new Issue Details (click to expand)WARNING
SUGGESTION
Unverified by static review
Files Reviewed (1 file)
Reviewed by deepseek-v4.1-flash-1017 · Input: 88.7K · Output: 13.3K · Cached: 736.3K Review guidance: REVIEW.md from base branch |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Both review points are addressed: |
| 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) |
There was a problem hiding this comment.
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.
Adds
mcps/gsc-pap/MCP.yaml, a hosted remote MCP in the same shape as the Anaconda OAuth entry.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, plusanalytics.readonlyfor GA4).datacom.gscpap/gsc-pap· Site: https://gscpap.com · Docs: https://github.com/aliarifsoydas/gsc-pap-claude-pluginReal 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