Scopus vs Scopus Plus MCP
A side-by-side look at the Scopus and Scopus Plus MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Scopus for research work; choose Scopus Plus 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 Scopus when
- You need dedicated capabilities in the Research domain.
- You have the keys it needs:
SCOPUS_API_KEY. - You want tools like
scopus_search, scopus_abstract, scopus_author.
Choose Scopus Plus MCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 40/100 · Fair | 36/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SCOPUS_API_KEY | SCOPUS_API_KEY |
| Verified owner |
Tools & capabilities
Scopus tools 6
scopus_searchSearch by keyword, title, author, affiliation, DOI, or advanced queryscopus_abstractRetrieve full abstract and metadata for a specific recordscopus_authorLook up author profiles (h-index, document count, subject areas)scopus_author_papersList an author's publicationsscopus_export_risExport results as RIS (for Zotero, EndNote, etc.)scopus_export_bibtexExport results as BibTeX
Scopus Plus MCP tools
No tool names declared yet. Check the project README from the listing page.
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.
Scopus
No confirmed install command for Scopus yet — follow the setup steps linked from its listing page rather than a guessed package name.
Scopus Plus MCP
{
"mcpServers": {
"scopus-plus-mcp": {
"command": "uvx",
"args": [
"scopus-plus-mcp"
],
"env": {
"SCOPUS_API_KEY": "YOUR_SCOPUS_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Scopus is categorized under Research and uses an install path we have not confirmed yet. Scopus Plus MCP belongs to Research and uses a local stdio subprocess. Pick Scopus for research work and Scopus Plus 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. Scopus has no confirmed install command yet — follow its own setup instructions.
Scopus has no declared pricing — check the project's own site. Scopus Plus 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 scopus and scopus-plus-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Scopus has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Scopus Plus MCP has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.