Google Scholar Search MCP Server

Google Scholar Search MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Google Scholar Search MCP directly instead of describing what you should do. An MCP (Model Context Protocol) server for searching Google Scholar, built for AI assistants and automation workflows that need papers, authors, citations, and BibTeX entries.

What you get

• Paper Search — Query Google Scholar by keyword with filtering, sorting, and pagination
• Author Lookup — Find researcher profiles with publication lists and h-index metrics
• Citation Tracking — Retrieve papers that cite a given work
• Paper Details — Get full metadata, citations-per-year graphs, and public access info
• BibTeX Export — Generate citation entries in BibTeX format
• Bulk Search — Batch search multiple queries with automatic rate limiting

Setting it up

The server ships on PyPI as google-scholar-search-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Google Scholar Search MCP is connected, these are the calls the assistant has available:

• Requirements — The Requirements tool exposed by this server

Configuration and credentials

You will need 7 environment variables: GS_MIN_DELAY, GS_MAX_DELAY, GS_PROXY_TYPE, GS_PROXY_HTTP, GS_PROXY_HTTPS, GS_SCRAPERAPI_KEY, GS_MAX_RETRIES. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.11 or later - Dependencies: mcp[cli]>=1.4.0, scholarly>=1.7.11, pydantic>=2.0 (see pyproject.toml) - project uses uv for dependency management

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the google scholar search mcp mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Google Scholar Search MCP's toolset — Requirements — is a fair guide to whether it matches your workflow. It is maintained by lwaetzig; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Google Scholar Search MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.