Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Google Search Console MCP Server for SEOsMCP100 Selected | xpzouying-xiaohongshu-mcpMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation github:aminforou · Publisher source ↗ | Community implementation github:xpzouying · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Jul 29, 2026 Package: Not documented | Repo: Aug 13, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 1,355 GitHub stars · checked 2026-08-14T18:46:26.000Z | 15,255 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Uses Google OAuth client-secrets JSON and browser login, or a Google service-account JSON whose email has access to the Search Console property. | Manual browser or QR login and saved session cookies are documented; selected actions require an xsec_token. No formal MCP client authentication is documented. |
| Cost | The MIT-licensed server lists no MCP fee. Google Cloud or Search Console quota and billing implications are not documented. | No MCP project or service price is documented. Platform, client, model, proxy, or hosting costs can still apply. |
| Permissions | Lists Google Search Console properties and reads analytics, URL inspection, and sitemap data. Site and sitemap add/delete tools are disabled unless GSC_ALLOW_DESTRUCTIVE=true. | Can log in, publish image or video content, search and read feeds and profiles, read and post comments and replies, like, unlike, favorite, unfavorite, schedule content, and bind products. It stores local session cookies and uses local media paths. |
| Data handling | Search Console properties, queries, pages, crawl and indexing results, and sitemap data are returned to the connected client. OAuth tokens are saved for reuse; service-account JSON is read from a configured path. Further retention is not documented. | Uses local browser session cookies, local image and video paths, and Xiaohongshu feed, profile, and comment data; requested content is posted to Xiaohongshu. Docker examples persist cookies and images in mounted directories. Encryption and telemetry are not documented. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Can expose private Search Console data and, when explicitly enabled, modify sites or sitemaps. Protect credential files, leave destructive tools disabled unless required, and restrict remote SSE deployments. | Account-impacting automation can publish, comment, like, and favorite. Protect the locally stored credential cookies, isolate the account, review every write action, and account for the publisher's warnings about session conflicts, expiry, and account prompts. |
| Evidence date | ||
| Editorial review | 2026-08-11 | 2026-08-11 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →