BrowserAI Dev vs Paperboy — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
BrowserAI Dev vs Paperboy
In-depth architectural comparison of the BrowserAI Dev and Paperboy 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
BrowserAI Dev
Research · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Paperboy
Research · Local stdio
Quality: 45/100 (Fair) | Auth: other
Verdict Summary: Choose BrowserAI Dev if you need specialized Research tools running via a local process. Choose Paperboy 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 BrowserAI Dev when:
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: LASTSEARCH_API_KEY.
BrowserAI Dev is categorized under Research and uses a local stdio subprocess. In contrast, Paperboy belongs to Research using local stdio subprocess. Select BrowserAI Dev when you need capabilities focused on research and Paperboy when you require tools for research.
Evidence-backed web research for AI agents. Real-time search with cited claims, confidence scores, and compare mode (raw LLM vs evidence-backed). MCP server, REST API, and Python SDK.
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.