Openreview vs Scopus MCP — MCP Server Comparison | AllMCPs
Openreview vs Scopus MCP
A side-by-side look at the Openreview and Scopus MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Openreview for research work as a local process; choose Scopus MCP for research as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Openreview when
You need dedicated capabilities in the Research domain.
No tool names declared yet. Check the project README from the listing page.
Scopus MCP tools 6
query
count
sort
coverDate
scopus_id
author_id
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.
Openreview is categorized under Research and uses a local stdio subprocess. Scopus MCP belongs to Research and uses a local stdio subprocess. Pick Openreview for research work and Scopus MCP for research.
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.
Openreview has no declared pricing — check the project's own site. Scopus MCP has no declared pricing — check the project's own site. 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 openreview and scopus-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openreview has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Scopus MCP has 53/100 (Good) with 1 views, 0 installs and 46 GitHub stars.