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 · Remote HTTP/SSE
Quality: 41/100 (Fair) | Auth: No auth required
Sourcelibrary V2
Research · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose Source Library if you need specialized Research tools running via a hosted cloud SSE transport. Choose Sourcelibrary V2 if your workspace requires Research integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
S
Choose Source Library when:
You need dedicated capabilities in the Research domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Research domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: MONGODB_ATLAS_URI, GOOGLE_GEMINI_API_KEY, VERCEL_BLOB_TOKEN.
Primary tools included: AI-powered OCR and language-specific text recognition, Context-aware translation maintaining scholarly accuracy, Full-text and semantic search across texts and translations.
Source Library is categorized under Research and uses a remote streaming HTTP/SSE transport. In contrast, Sourcelibrary V2 belongs to Research using remote streaming HTTP/SSE transport. Select Source Library when you need capabilities focused on research and Sourcelibrary V2 when you require tools for research.