In-depth architectural comparison of the Paperboy and Semantic Scholar MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Paperboy
Research · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Semantic Scholar MCP
Research · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Verdict Summary: Choose Paperboy if you need specialized Research tools running via a local process. Choose Semantic Scholar MCP if your workspace requires Research integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Paperboy when:
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ZOTERO_API_KEY, ZOTERO_LIBRARY_ID, SMTP_HOST, SMTP_PORT, SMTP_USERNAME, SMTP_PASSWORD, DROPBOX_ACCESS_TOKEN, DROPBOX_FOLDER.
Primary tools included: Search papers by arXiv ID, DOI, or title with fuzzy matching, Recommend related papers using Semantic Scholar citation graph, Queue papers in Zotero Reading Queue collection with duplicate protection.
Send research papers from Claude to a Kindle or Kobo, with Zotero as the source of truth. Searches arXiv and OpenAlex, recommends related work via the Semantic Scholar citation graph, queues papers in a Zotero collection, and delivers the PDFs by email or Dropbox. Receipts report file sizes and name anything that could not be sent.
Paperboy is categorized under Research and uses a local stdio subprocess. In contrast, Semantic Scholar MCP belongs to Research using local stdio subprocess. Select Paperboy when you need capabilities focused on research and Semantic Scholar MCP when you require tools for research.