paperqa-mcp-server
Related Servers
Alternatives to paperqa-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables searching for scientific papers across OpenAlex, CrossRef, and Unpaywall, and downloading open-access PDFs directly through Claude Desktop.51MIT
- FlicenseAqualityCmaintenanceEnables Claude to search a local hybrid retrieval index of research papers and ingest new PDFs, providing research-paper memory queryable directly through natural language.2-
- AlicenseAqualityCmaintenanceSearch and read arXiv papers directly from Claude. Supports keyword, author, category, and date filtering plus full PDF text extraction so Claude can read, summarise, and reason over entire papers, not just abstracts.524MIT
- AlicenseBqualityCmaintenanceA second brain for researchers — gives Claude persistent memory of your papers, field, and working history, with answers cited from your own indexed library1003AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables semantic search and conversational querying across a personal research library of PDFs, DOCX, and other documents using a vector database. It provides tools for document summarization, finding related papers, and high-accuracy retrieval for AI clients like Claude Desktop.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to search and query personal document collections (PDF, Word, Markdown, text) using semantic search and conversational AI with full context preservation across exchanges.MIT
TDQS
Scored across 2 tools
The two tools have completely distinct purposes with no overlap: index_status is for health/status monitoring of the indexing system, while paper_qa is for querying and synthesizing content across papers. Their descriptions clearly differentiate diagnostic vs. query functionality.
Both tools follow a consistent snake_case naming pattern with clear verb_noun structure: index_status (verb: check/status, noun: index) and paper_qa (verb: query/answer, noun: paper). The naming is predictable and readable throughout.
With only 2 tools, the server feels severely under-scoped for a paper query and synthesis domain. A typical paper/library server would need at least basic CRUD operations for papers, search filtering, or metadata management, but here the surface is minimal and relies heavily on external Zotero tools.
The toolset is incomplete for the apparent domain of paper querying and synthesis. There are no tools for managing papers (add/remove), browsing the library, filtering searches, or handling indexing beyond status checks. The server delegates core functionality to Zotero tools, creating significant gaps for agent workflows.