Google Scholar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CORE_API_KEY | No | API key for CORE API (optional, for full-text access) | |
| SERPAPI_API_KEY | Yes | API key for SerpAPI (required for Google Scholar search) |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_articlesA | Search for academic articles on Google Scholar. Returns articles with title, authors, year, citation count, and links. Use citation_id for get_citations and cluster_id for get_article_versions. |
| get_citationsA | Get articles that cite a specific paper. Use the citation_id from search_articles results. |
| get_article_versionsA | Get all versions of a specific article from different sources. Use the cluster_id from search_articles results. |
| get_fulltextA | Get full text of an Open Access article via CORE API. Provide at least one identifier: DOI, title, or CORE ID. Returns full text if available, otherwise abstract and download link. |
| search_open_accessA | Search for Open Access articles with full-text available. Returns articles from CORE aggregator with direct download links. |
| ask_research_questionA | Answer a research question using evidence from Open Access papers. Searches CORE API for relevant papers and returns abstracts and text snippets as evidence. Use this for literature review and evidence-based answers. The AI will synthesize the answer from the returned 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 6 tools
Tools are mostly distinct with clear purposes. search_articles and search_open_access target different sources (Google Scholar vs. CORE), and ask_research_question synthesizes evidence, so overlap is minimal and well-explained.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_articles, get_citations), which is predictable and easy for agents to parse.
6 tools cover the core functionalities of a Google Scholar MCP server (search, citations, versions, full text, Q&A) without being excessive or insufficient.
The set covers essential workflows like searching, retrieving citations, versions, and full text. Minor gaps exist (e.g., no author-specific search or journal filtering), but overall it's well-scoped.