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.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldZotero MCPWatchlist candidateGoogle Search Console MCP Server for SEOsMCP100 Selected
Task fit
Best for
  • Searching, reading, and organizing publisher-documented Zotero library metadata and research content through an MCP client
  • SEO analysis across Search Console properties, queries, pages, indexing status, and sitemaps
Not ideal for
  • A complete literature review, authoritative citation validation, or document access outside the configured Zotero library
  • General web analytics or SEO work that does not use Google Search Console data
Avoid when
  • The library contains private notes, attachments, unpublished research, or credentials that must not reach the connected model
  • You cannot grant the configured OAuth user or service account access to the relevant Search Console property
Provenance
Provenance details

Community implementation

io.github.54yyyu · Publisher source ↗

Community implementation

github:aminforou · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 13, 2026

Package: Aug 6, 2026

Repo: Jul 29, 2026

Package: Not documented

Popularity evidence
GitHub stars

4,657

GitHub stars · checked 2026-08-14T18:46:26.000Z

1,355

GitHub stars · checked 2026-08-14T18:46:26.000Z

30-day package downloads

26,595

PyPI Stats package downloads · checked 2026-08-14T18:46:26.000Z

No reliable download data
External adoption evidence
  • github: repository stars: 4,657Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
  • PyPI Stats: package downloads: 26,595Non-comparable contextual signal.PyPI Stats: package downloads · Provider last month · checked 2026-08-14T18:46:26.000ZEvidence source ↗
  • github: repository stars: 1,355Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude CodeLocal stdio
Claude DesktopLocal stdio
CodexLocal stdio
VS CodeLocal stdio
CursorLocal stdio
OpenCodeLocal stdio
Claude CodeLocal stdio
Claude DesktopLocal stdio
CodexLocal stdio
VS CodeLocal stdio
CursorLocal stdio
OpenCodeLocal stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationLocal mode needs no API key. The reviewed README does not specify Web API credentials. Optional OpenAI and Gemini embeddings require provider API keys.Uses Google OAuth client-secrets JSON and browser login, or a Google service-account JSON whose email has access to the Search Console property.
CostThe MIT-licensed server lists no MCP fee. Optional embedding providers and external services can have separate costs.The MIT-licensed server lists no MCP fee. Google Cloud or Search Console quota and billing implications are not documented.
PermissionsReads Zotero metadata, collections, tags, full text, and annotations; performs semantic search and citations; and can create or update notes and annotations, add papers, manage collections, update metadata, tags, and duplicates.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.
Data handlingLocal mode reads the local library and attachments; Web API mode accesses cloud data; hybrid reads locally and writes through the API. Embeddings can use local models, OpenAI, Gemini, or Ollama; retention is not documented.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.
Limitations
Tradeoffs
  • Direct library context can improve research assistance, while local or API setup and access to notes and attachments increase privacy and synchronization concerns.
  • It reduces manual reporting work, but the assistant can see sensitive search-performance data and optional destructive site or sitemap operations require an explicit flag.
Risk contextWrite tools can alter a research library, while PDFs, full text, and cloud integrations can expose sensitive research. Start local and read-focused, restrict libraries, and supervise writes.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.
Evidence date
Editorial review2026-08-112026-08-11
Candidate evidence2026-08-14T18:46:26.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →