semantic-scholar-mcp
Related Servers
Alternatives to semantic-scholar-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server that provides access to Semantic Scholar's academic paper database, enabling paper search, detailed retrieval, author info, and citation export.410-
- AlicenseBqualityDmaintenanceMCP server that provides Semantic Scholar academic search capabilities, including paper search, detail query, citation analysis, author search, and intelligent recommendations.984 npm6MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching and retrieving academic papers, authors, citations, and references from Semantic Scholar via an HTTP MCP server with caching and rate limiting.118 npmMIT
- AlicenseBqualityCmaintenanceAn MCP server that provides access to Semantic Scholar's academic graph, recommendations, and datasets APIs, enabling paper search, citation analysis, author lookups, and dataset discovery through 20+ tools.223MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for academic research combining local document search with Semantic Scholar API integration.MIT
- FlicenseNot gradedqualityDmaintenanceA unified MCP server providing programmatic access to three major academic research APIs: Semantic Scholar, OpenAlex, and PubMed.2-
TDQS
Scored across 9 tools
Most tools target clearly distinct operations: paper lookup, author lookup, search, citations, and recommendations. The main overlap is s2_recommend_single vs s2_recommend_multi, where the single-seed version is effectively a special case of the multi-seed one, which could cause misselection.
All tools use a consistent s2_ prefix and snake_case, with mostly verb_noun naming (s2_get_author, s2_search_papers, s2_batch_papers). A few are noun-only or noun_noun (s2_citations, s2_author_papers, s2_recommend_single vs _multi), but the convention remains readable and predictable.
Nine tools is well within the ideal range and each maps to a meaningful Semantic Scholar capability. No bloat or padding; the only questionable one is the redundant recommend_single, which is minor.
The surface covers the core read-only scholarly workflows: paper search/get/batch, author search/get/papers, citation graph traversal, and recommendations. Minor gaps exist (e.g., separate references vs citations listing, venue/field enumeration, batch author lookup), but agents can work around them for most tasks.