Verified

Google Scholar Search MCP Server

Academic search tool for retrieving papers, citations, and BibTeX metadata.

Data last scanned yesterday · Reviewed last month

29★ 2PythonMIT

Overview

The Google Scholar Search MCP server integrates scholarly data directly into AI assistants. It enables users to perform keyword searches, retrieve researcher profiles including h-index metrics, and track citation history. The tool provides structured outputs like BibTeX entries, facilitating automated research workflows. The server includes built-in rate limiting and supports various proxy configurations, such as ScraperAPI, to manage request flow and avoid blocks from Google Scholar. It is built in Python and designed to work within existing MCP-compatible environments.

Our verdict

With a security score of 35/100, this server is classified as high-risk. This rating stems primarily from its nature as a community-maintained project rather than an official integration, alongside a single-contributor development model that presents potential bus-factor risks. Prospective users should be cautious regarding potential authentication and proxy handling gaps, as these aspects have not been formally reviewed for security.

Includes built-in rate limiting to manage request frequency
Supports multiple proxy configurations including ScraperAPI
Provides BibTeX export and citation tracking capabilities
Zero direct dependencies reduce the supply-chain surface

Community-maintained with no official vendor affiliation
High bus-factor risk due to single-contributor status
Authentication and read-only mode security remain unreviewed

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›What are the system requirements to run this server?

You need Python 3.11 or later and the mcp, scholarly, and pydantic libraries installed.

›Can I use this server without a proxy?

Yes, the default configuration is set to no proxy (GS_PROXY_TYPE=none), but you must respect the built-in rate limits to avoid being blocked by Google Scholar.

›How does the server handle rate limiting?

The server automatically enforces randomized delays between 5 and 15 seconds by default and supports up to 3 retries for failed requests.

›What should I do if my IP address gets blocked by Google Scholar?

You may need to wait 24-48 hours for the block to expire, or alternatively, use a proxy service like ScraperAPI or a free proxy to rotate your IP address.

›Which proxy types are supported by the configuration?

The server supports 'free' proxies, 'single' proxy connections via HTTP/HTTPS URLs, and integration with the 'scraperapi' service.