Google Scholar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | HasData API key, created free at https://app.hasdata.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hasdata_google_scholar_cite_getScholarCitationFormatsA | Get Scholar Citation Formats Looks up citation formats and export links for a single Google Scholar organic search result, identified by its |
| hasdata_google_scholar_scholar_getScholarSearchResultsA | Get Scholar Search Results Scrapes Google Scholar for a query with author:/source: search helpers, year range (asYlo/asYhi), cited-by and all-versions lookups (cites/cluster), review-article and citation-inclusion filters, language/language-restrict, and start/num pagination. Returns each organic result with title, link, snippet, publication info (authors with profile links), cited-by count and link, related-articles link, and all-versions count and link. Use for academic research, literature review automation, citation tracking, and grounding research agents with scholarly sources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.