In-depth architectural comparison of the Source Library and Sourcelibrary V2 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
Source Library
Research · Local stdio
Quality: 37/100 (Fair) | Auth: API Key required
Sourcelibrary V2
Research · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Source Library if you need specialized Research tools running via a local process. Choose Sourcelibrary V2 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 Source Library 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: OCR for historical texts using Gemini Vision, Context-aware translation across pages, Full-text and semantic search.
Source Library is categorized under Research and uses a local stdio subprocess. In contrast, Sourcelibrary V2 belongs to Research using local stdio subprocess. Select Source Library when you need capabilities focused on research and Sourcelibrary V2 when you require tools for research.