MCP MCP Server

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. An MCP (Model-Context-Protocol) Server for Deep Academic Research.

What you get

McpDeepResearch is a lightweight but powerful MCP (Model-Context-Protocol) server that helps you quickly discover, retrieve, and read academic papers from the web using the familiar Google Scholar interface.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

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

• search_scholar_papers — Google Scholar search with optional year-filter & date-sort
• fetch_md — Convert any public web page to clean Markdown
• fetch_paper — Auto-detect the paper content (title, abstract, body, references) and strip the rest

Configuration and credentials

You will need 2 environment variables: CDP_ENDPOINT, GOOGLE_PROXY. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the 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. MCP's toolset — search_scholar_papers, fetch_md, fetch_paper — is a fair guide to whether it matches your workflow.

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