Skip to main content
Glama
scholar-mcp

scholar-mcp

by pvliesdonk

Related Servers

Alternatives to scholar-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for scientific grounding: search and discover open-access research papers across arXiv, OpenAlex, Crossref, PubMed, and Semantic Scholar, and retrieve references/citations from paywalled journals via public DOI/abstract metadata.
      3
      124 PyPI
      7
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Unified MCP server for scientific literature search and extraction, integrating databases like Scopus, OpenAlex, Semantic Scholar, and Unpaywall to enable AI agents to discover papers, track citations, and analyze content.
      27
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A unified MCP server for academic paper discovery, citation exploration, and research intelligence workflows over multiple scientific knowledge sources.
      7
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AI-assisted research: paper ingestion, semantic search, citation graph traversal, cross-domain knowledge synthesis, and workflow automation.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A MCP server for academic literature retrieval, aggregating multiple data sources like arXiv, Crossref, OpenAlex, PubMed, and Semantic Scholar to provide search, details, citations, trends, and recommendations.
      4
      MIT

    TDQS

    A4.1/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, and forward vs. backward citation tools are well separated. Minor overlap exists between resolve_standard_identifier and get_standard fuzzy lookup, and between batch_resolve and single-record fetchers, but descriptions largely disambiguate them.

    Naming Consistency5/5

    Names consistently use snake_case and mostly follow a verb_noun pattern such as search_papers, get_citations, and generate_citations. Occasional forms like batch_resolve and enrich_paper are still readable and compatible with the overall convention.

    Tool Count4/5

    The server covers several domains—papers, citations, books, standards, and async job status—so a larger surface is justified. At 21 tools it is somewhat heavy, but each tool appears to have a distinct role rather than being redundant.

    Completeness4/5

    Core scholarly workflows are covered: search, metadata, authors, citations/references, citation graphs, recommendations, batch resolution, formatting, books, standards, and async job handling. Minor gaps remain, such as no dedicated paper PDF/full-text retrieval tool, but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessSyncing