Log inSubmit server
Scopus logo

Scopus

Search Scopus publications, profiles, citations, and PlumX metrics through Elsevier APIs over MCP stdio.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Scopus

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "scopus-2": {
      "command": "npx",
      "args": [
        "-y",
        "scopus-mcp"
      ],
      "env": {
        "ELSEVIER_API_KEY": "YOUR_VALUE_HERE",
        "ELSEVIER_INST_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 8 tools correctly (5d ago).

Overview

The Scopus MCP server connects MCP clients to Elsevier’s Scopus API for publication, author, affiliation, citation, and PlumX metric queries. It runs over stdio through npx and preserves the API’s parameter names and JSON response structure. Use it when an agent needs structured Scopus data and you have the required Elsevier credentials and access. Subject classification lookups are available without an API key.

Use cases

  • Search Scopus publications by query parameters
  • Find authors and institutional affiliations
  • Retrieve author and institution profiles
  • Review yearly citation counts
  • Fetch PlumX metrics for publications

Key features

  • Scopus publication search
  • Author and affiliation lookup
  • Author and institution profile retrieval
  • Citation overviews
  • PlumX publication metrics
  • Subject classification lookup

Tools8

What Scopus lets your agent do. Expand a tool for its parameters.

Verified live~4.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 15d

What it can do

From the 8 tools this server returned when we ran it; 8 declare their own safety hints.

Handles credentials · 5Makes network requests · 8Read-only tools · 8
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceSigned build
Package age17 days
Maintainers1

Observed 2026-10-23 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · scopus-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads958Package downloads in the last 30 days.
Last commit22d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed8Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Scopus works

What Scopus does

The Scopus MCP server exposes selected Elsevier Scopus API operations as MCP tools for research workflows. It can search publications, authors, and affiliations; retrieve author and institution profiles; return yearly citation counts and summaries; fetch PlumX metrics; and look up subject classification codes.

The server is listed in the 🔬 Research category and is suited to agents that need bibliographic or researcher-related data from Scopus. It does not reshape the API response into a custom format: returned JSON retains the original API fields and values.

How it works

Scopus MCP server runs as a Node.js process over stdio. An MCP client starts it with npx, and each tool invocation makes one request to the Elsevier API. Pagination is controlled through the relevant tool parameters, so additional result pages require additional calls.

Responses are available as structured MCP content and as a text content block. The server also exposes available quota information, including request limits, remaining quota, reset timing, and retry guidance, in MCP metadata. Requests support cancellation and have a 30-second timeout. Retries and redirects are not performed automatically.

Setup and configuration

The Scopus MCP server requires Node.js 22.22.0 or newer, npm, an MCP client with stdio support, and an API key from the Elsevier Developer Portal. Configure the server with the npx command and the scopus-mcp package, then place credentials in the client’s environment configuration. A pinned package version can be used by changing the package argument to scopus-mcp@<version>.

ELSEVIER_API_KEY is required by every tool except subject_classifications. ELSEVIER_INST_TOKEN can be added when an institution provides an institutional token. The process does not load .env files, so credentials must be supplied by the MCP client or execution environment.

Access to specific data and API views depends on the Elsevier subscription and institutional access available to the account. Reload the MCP client after adding or changing the server configuration.

Tools and capabilities

Available tools include:

  • scopus_search for finding publications.
  • author_search for finding authors and co-authors.
  • affiliation_search for finding institutions.
  • author_retrieval for author profiles identified by ID, EID, or ORCID.
  • affiliation_retrieval for institution profiles identified by ID or EID.
  • citation_overview for yearly citation counts and summaries.
  • plumx_metrics for publication metrics by identifier.
  • subject_classifications for subject code lookups without an API key.

Limitations and notes

Authentication failures, subscription restrictions, institutional access problems, rate limits, network failures, timeouts, and unexpected API responses are returned as MCP errors. Invalid arguments are rejected before a request is sent. For HTTP 429 responses, inspect the quota metadata and Retry-After value before deciding whether to retry.

The Scopus MCP server does not automatically retry failed requests or follow redirects. API credentials are redacted from error output. The project is an independent implementation and is not affiliated with Elsevier.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Scopus

Scopus is an MCP server that connects AI clients to Elsevier's Scopus API. Its main tools search publications, authors, and affiliations, retrieve author and institution profiles, return citation overviews and PlumX metrics, and look up subject classifications. It runs over stdio and uses an Elsevier API key for most operations.

Install it through an MCP client configuration that runs `npx -y scopus-mcp`. The client must support stdio, and the environment should include `ELSEVIER_API_KEY`. Node.js 22.22.0 or newer and npm are required. Reload the client after saving the configuration.

`ELSEVIER_API_KEY` is required for every tool except `subject_classifications`. Add `ELSEVIER_INST_TOKEN` when your institution supplies an institutional token. Set both values in the MCP client's environment configuration; the server does not read `.env` files.

Yes, pagination is supported through each tool's pagination parameters. Request additional pages with subsequent tool calls. Each call makes one Elsevier API request, and retries are not automatic.

Check the API key, Scopus subscription, institutional access, and institutional token for 401 or 403 responses. For 429 responses, inspect the returned quota headers and `Retry-After` value before retrying. Network and timeout errors should be checked against connectivity to `api.elsevier.com`.

Related MCP servers

All in Research All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewScopus AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/scopus-2?style=directory)](https://allmcps.com/mcp/scopus-2)
HTML Embed
<a href="https://allmcps.com/mcp/scopus-2"><img src="https://allmcps.com/api/badge/scopus-2?style=directory" alt="Scopus on AllMCPs" /></a>