Google Scholar MCP Server
Related Servers
Alternatives to Google Scholar MCP Server
- AlicenseAqualityAmaintenanceA hosted MCP server that returns DuckDuckGo search results as structured JSON, with ranked organic results, separate ads, AI answers, and 37 region/language targets for any MCP client.152 npm132 PyPI7MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to perform live Google searches and retrieve structured SERP data including organic results, AI Overviews, People Also Ask, AI Mode answers, news, shopping, and short-video results via eight read-only tools.10413 npm178 PyPI18MIT
- AlicenseAqualityAmaintenanceEnables fetching any public web page through managed proxies, with optional JavaScript rendering, returning markdown, text, HTML, or structured JSON.135 npm246 PyPI11MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables searching Google Scholar for academic papers, citations, and author profiles, returning structured JSON results including titles, authors, citation counts, abstracts, and PDF links.1MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search and analyze Google Scholar publications, authors, citations, and download papers.112MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching academic papers, exploring citation graphs, and looking up authors from Semantic Scholar's database of 200M+ papers.4MIT
- AlicenseAqualityDmaintenanceEnables searching academic literature via Semantic Scholar with relevance filters, batch metadata retrieval, and citation-graph recommendations.5AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables academic research through Google Scholar by searching for papers, finding author publications, discovering recent research, and identifying highly cited works through web scraping with natural language queries.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to access academic citations, fetch metadata, and generate BibTeX entries directly from Google Scholar via MCP tools.1133 PyPI1MIT
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: one performs searches across Google Scholar, while the other retrieves citation formats for a previously returned result. There is no functional overlap, and their complementary relationship is explicit.
Both names share the same provider prefix and follow a snake_case get-style verb, making them predictable. The resource segment differs (cite vs scholar), but this is minor and does not obscure meaning.
With only two tools, the server feels thin for a domain as broad as Google Scholar. However, the two tools cover the most essential scholarly search and citation workflows, so the count is borderline but not unreasonable.
The core workflow of searching for scholarly results and retrieving citation formats is well covered. Missing capabilities like fetching a full author profile or a detailed cited-by list are notable but can be worked around via the existing search parameters.