literature-bot-mcp
Related Servers
Alternatives to literature-bot-mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityBmaintenanceEnables users to build and query a project-local literature database by ingesting papers from Semantic Scholar, PubMed, arXiv, and OpenAlex, caching open-access PDFs, extracting full text, ranking results, and exposing MCP tools for search, seeds, feedback, and pipeline status over stdio.16-
- FlicenseNot gradedqualityCmaintenanceA local, rule-based MCP server for searching and analyzing academic papers from arXiv. Enables paper search, ranking, smart summarization, keyword extraction, and citation generation without API keys or LLM calls.-
- AlicenseNot gradedqualityDmaintenanceEnables searching arXiv, fetching metadata, reading papers as section-aware Markdown, listing recent papers, and downloading PDFs via five MCP tools.16 npm2MIT
- AlicenseAqualityDmaintenanceEnables searching, downloading, and managing academic papers from arXiv.org through natural language interactions. Provides tools for paper discovery, PDF downloads, and local paper collection management.41MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search, retrieve, and manage a personal arXiv paper library over MCP, with explainable relevance ranking, trend analysis, saved papers, and reading suggestions — all running locally without accounts or external services.MIT
- AlicenseNot gradedqualityDmaintenanceEnables arXiv paper search, PDF download, text extraction, and context chunking for LLM pipelines, along with advanced features like citation graphs and reproducibility scoring.2MIT
TDQS
Scored across 4 tools
Each tool targets a distinct stage: search, metadata details, preparation/download, and evidence retrieval. The only mild overlap is prepare_paper vs retrieve_paper_evidence, since retrieve auto-prepares when needed, but descriptions clarify the distinction well.
All four tools follow a strict literature_verb_noun pattern (search_papers, get_paper_details, prepare_paper, retrieve_paper_evidence), making the namespace and conventions fully predictable.
Four tools is slightly lean but well-matched to a focused paper search-and-retrieval server. Each tool earns its place with a distinct role in the pipeline.
The surface covers a coherent lifecycle: search, inspect metadata, prepare, and retrieve cited evidence. Minor gaps exist (no listing/clearing of the local cache), but core literature workflows are fully supported.