Scholar vs Next Devtools MCP
A side-by-side look at the Scholar and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Scholar for research work as a local process; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Scholar when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SCOPUS_API_KEY, S2_API_KEY, SCIHUB_MIRRORS, LIBGEN_MIRRORS, SCOPUS_INST_TOKEN, CONTACT_EMAIL. - You want tools like
search_papers_tool, search_papers_s2_tool, get_paper_details_tool.
Choose Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Developer Tools |
| Quality signal | 48/100 · Fair | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SCOPUS_API_KEYS2_API_KEYSCIHUB_MIRRORSLIBGEN_MIRRORSSCOPUS_INST_TOKENCONTACT_EMAIL | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 832 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 1 upvotes |
| Tools | 27 | 4 |
| Full listing | View Scholar | View Next Devtools MCP |
Tools & capabilities
Scholar tools 27
search_papers_toolSearch papers via Scopus (Boolean syntax) or OpenAlex. Sort by `cited_by_count` or `publication_year`.search_papers_s2_toolSearch papers via Semantic Scholar. Note: strictly rate-limited to 1 request/sec.get_paper_details_toolFetch full metadata and abstract by Scopus ID, DOI, or OpenAlex ID (with automatic routing).get_paper_details_s2_toolFetch full metadata from Semantic Scholar, including **AI-generated TLDRs**. Accepts S2 ID or DOI.search_titles_unpaywall_toolSearch Unpaywall's database directly by title. Set `is_oa=True` for strictly OA results.get_related_works_toolFind related/similar papers using OpenAlex's bibliographic coupling.search_books_toolSearch for book metadata via Google Books or Open Library.get_book_details_toolFetch complete book details, descriptions, and ISBNs.search_libgen_toolSearch Library Genesis for books to retrieve their download MD5 hashes.interact_with_book_toolSmart extraction from Libgen. Actions: `toc` (Table of Contents), `search` (keywords), `pages` (range).autocomplete_authors_toolRapidly disambiguate author names and resolve OpenAlex Author IDs.search_authors_toolDetailed bibliometric profiles: H-index, i10-index, ORCID, and research concepts.- +15 more on the listing page
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Scholar
{
"mcpServers": {
"scholar": {
"command": "uvx",
"args": [
"scholar-academic-mcp"
],
"env": {
"SCOPUS_API_KEY": "YOUR_SCOPUS_API_KEY_HERE",
"S2_API_KEY": "YOUR_S2_API_KEY_HERE",
"SCIHUB_MIRRORS": "YOUR_SCIHUB_MIRRORS_HERE",
"LIBGEN_MIRRORS": "YOUR_LIBGEN_MIRRORS_HERE",
"SCOPUS_INST_TOKEN": "YOUR_SCOPUS_INST_TOKEN_HERE",
"CONTACT_EMAIL": "YOUR_CONTACT_EMAIL_HERE"
}
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Scholar is categorized under Research and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Scholar for research work and Next Devtools MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Scholar has no declared pricing — check the project's own site. Next Devtools MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add scholar and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Scholar has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.