Scholar MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCHOLAR_TIMEOUT | No | HTTP timeout in seconds | 20 |
| PYTHONUNBUFFERED | No | Force stdout and stderr to be unbuffered. | 1 |
| SCHOLAR_MIN_DELAY | No | Minimum delay between requests (seconds) | 1.2 |
| SCHOLAR_PROXY_URL | No | HTTP/HTTPS proxy URL | |
| SCHOLAR_USER_AGENT | No | User-Agent header for requests | Chrome-like UA |
| SCHOLAR_MAX_RETRIES | No | Retry attempts on failure | 2 |
| SCHOLAR_MAX_PAGE_SIZE | No | Max results per request | 20 |
| SCHOLAR_RETRY_BACKOFF | No | Backoff multiplier between retries | 1.5 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_papers_by_topicC | Search Google Scholar papers by topic keywords. |
| get_author_papersB | Get papers filtered by author name from Google Scholar search. |
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 have clearly distinct purposes: one filters papers by author name, while the other searches by topic keywords. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the query.
Both tools follow a verb_noun pattern (get_author_papers, search_papers_by_topic), which is consistent and readable. The minor deviation is in the prepositional phrase 'by_topic' vs. no preposition in the first name, but this does not hinder clarity.
With only 2 tools, the server feels thin and under-scoped for a Google Scholar integration. Key operations like retrieving paper details, citations, or author profiles are missing, limiting the server's utility for comprehensive scholarly research.
The toolset is severely incomplete for a Google Scholar domain. It lacks basic CRUD operations such as getting paper metadata, author information, or citation counts, and there are no update or delete capabilities, leaving significant gaps for agent workflows.