Skip to main content
Glama
Remus-cloud

literature-bot-mcp

by Remus-cloud

Related Servers

Alternatives to literature-bot-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      B
      maintenance
      Enables 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
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching arXiv, fetching metadata, reading papers as section-aware Markdown, listing recent papers, and downloading PDFs via five MCP tools.
      16 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      4
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables arXiv paper search, PDF download, text extraction, and context chunking for LLM pipelines, along with advanced features like citation graphs and reproducibility scoring.
      2
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues