Awesome Paper MCP
Related Servers
Alternatives to Awesome Paper MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceUnifies academic literature retrieval from multiple sources like Scopus, ArXiv, PubMed, and Google Scholar into a single standardized API for LLM agents.2926 PyPI11AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search across major research-paper indexes and retrieve metadata, full text, and PDFs through an unpaywalled fallback chain, with biomedical sciences prioritized.MIT
- FlicenseNot gradedqualityAmaintenanceEnables searching for academic papers and preprints across multiple platforms including Semantic Scholar, arXiv, PubMed, and CrossRef. It provides access to research records, DOI lookups, and journal metadata through a unified interface deployed on Cloudflare Workers.2-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search across multiple academic databases (PubMed, arXiv, bioRxiv, medRxiv, Semantic Scholar) through a unified interface. Supports advanced filtering, metadata retrieval, PDF downloads, and comprehensive research workflows with citation analysis.5-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to search, analyze, and summarize academic research papers in real-time from arXiv, Semantic Scholar, and PubMed. Provides automatic deduplication, citation analysis, and BibTeX generation across multiple research databases.23 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run reproducible, high-recall literature search across seven source families with RRF fusion, fetch open-access full texts (falling back to abstracts), expand citations, export BibTeX/RIS, and audit reference coverage — all without any LLM API key, leaving query planning and writing to the agent. Multiple agent clients share one accumulating literature pool and background search jobs that keep running after sessions close.3MIT
TDQS
Scored across 6 tools
The core wrappers (list_sources, search_papers, get_paper, get_paper_text) target clearly distinct steps, and the metadata-vs-full-text split is explicitly documented. However, call_source_tool is a generic escape hatch that can perform the same operations as every wrapper, so an agent could plausibly misselect it instead of search_papers or get_paper without reading carefully.
All six tools use snake_case with a leading verb (list_, search_, get_, call_, run_), giving a predictable verb_noun pattern throughout. The paired get_paper / get_paper_text naming even signals their relationship clearly.
Six tools is lean for a multi-backend aggregation server and each has a distinct role: discovery, search, metadata, full text, escape hatch, and pipeline. Nothing feels redundant or padded.
The surface covers the full lifecycle: discover backends, search across them, fetch metadata, retrieve full text, and reach any backend-specific feature (reviews, LaTeX, conference listings) via call_source_tool. Citation-graph traversal is not a dedicated wrapper but is reachable through the escape hatch, so there are no real dead ends.