In-depth architectural comparison of the Sourcelibrary V2 and Source Library 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
Sourcelibrary V2
Research · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Source Library
Research · Local stdio
Quality: 37/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Sourcelibrary V2 if you need specialized Research tools running via a local process. Choose Source Library 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 Sourcelibrary V2 when:
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
Primary tools included: Full-text search across OCR and translations, AI-assisted OCR and English translation, Book and page bibliographic metadata.
Sourcelibrary V2 is categorized under Research and uses a local stdio subprocess. In contrast, Source Library belongs to Research using local stdio subprocess. Select Sourcelibrary V2 when you need capabilities focused on research and Source Library when you require tools for research.