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

Zotero MCPGoogle Search Console MCP Server for SEOs

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

Comparable alternatives

Context7 MCPMCP100 RecommendedPlaywright MCPMCP100 RecommendedHugging Face MCPMCP100 RecommendedExa MCPMCP100 RecommendedFramelink MCP for FigmaMCP100 RecommendedAsana MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Zotero MCPShortlist candidate	Google Search Console MCP Server for SEOsMCP100 Recommended
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: Sep 15, 2026 Package: Not documented
Popularity evidence
GitHub stars	4,657 GitHub stars · checked 2026-08-14T18:46:26.000Z	1,712 GitHub stars · checked 2026-09-24T04:14:16.248000Z
Package downloads / 30 days	26,595 package downloads / 30 days · checked 2026-08-14T18:46:26.000Z	No reliable download data
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✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Local 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.
Cost	The 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.
Permissions	Reads 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 handling	Local 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 context	Write 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 review	2026-08-11	2026-08-11
Candidate evidence	2026-08-14T18:46:26.000Z	2026-09-24T04:25:05.554391Z

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

Read the evidence method →