scopus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELSEVIER_API_KEY | Yes | Required for all tools except `subject_classifications`. | |
| ELSEVIER_INST_TOKEN | No | Institutional token, if provided by your institution. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scopus_searchA | Search Scopus publications with its native query syntax. Returns one page of the original Elsevier JSON, including search-results, entry and pagination. Example: TITLE-ABS-KEY(machine learning) AND PUBYEAR > 2020. Credentials come from the server environment. Access to views and cursor pagination depends on your Scopus entitlements. |
| author_searchA | Search Scopus author profiles using native queries, or supply co-author to find an author’s collaborators. Returns one page of native Elsevier JSON, including search-results and pagination. Example: AUTHLASTNAME(Smith) AND AUTHFIRST(John). Credentials come from the server environment. Access depends on your Scopus entitlements. |
| affiliation_searchA | Search Scopus institution profiles using native affiliation query syntax. Returns one page of native Elsevier JSON, including search-results and pagination. Example: AFFIL(university) AND AFFIL(London). Credentials come from the server environment. Access depends on your Scopus entitlements. |
| author_retrievalA | Retrieve Scopus author profiles by author_id, eid, or orcid. Comma-separated author_id or eid values use one native batch request. Returns the original Elsevier JSON; view access depends on entitlements. Pagination and superseded-profile resolution are explicit. |
| affiliation_retrievalA | Retrieve a Scopus institution profile by affiliation_id or eid. Returns the original Elsevier JSON, including profile data or one page of related documents/authors when requested through view. Access depends on entitlements; no linked records or additional pages are fetched automatically. |
| plumx_metricsA | Retrieve native PlumX metrics for one publication or artifact by identifier. Returns the original Elsevier JSON, including metric categories, count types and sources. Requires active Scopus access. HTTP 404 can mean that no metrics are available or that the identifier is unknown. |
| citation_overviewA | Retrieve yearly citation counts and summaries for Scopus documents. Supply one native document identifier type, with comma-separated values for multiple documents. Returns the original Elsevier JSON in one request. Citation Overview access must be enabled for your API key. |
| subject_classificationsA | Retrieve or filter Scopus subject classifications. Returns the original Elsevier JSON, including subject codes, descriptions, details, and abbreviations. Omit filters to list all classifications. This public endpoint does not require an API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool pairs a distinct entity with a distinct action: author_search/author_retrieval and affiliation_search/affiliation_retrieval are cleanly separated by query-vs-id, and citation_overview, plumx_metrics, scopus_search, and subject_classifications each target unique resources. There is no meaningful overlap that would cause misselection.
Most tools follow a predictable entity_action pattern (author_search, affiliation_retrieval, scopus_search, etc.), which is easy to parse. However, citation_overview, plumx_metrics, and subject_classifications are noun-only with no verb, a minor deviation from the dominant convention.
Eight tools is well-scoped for a Scopus API wrapper, with two search/retrieve pairs for authors and affiliations plus publication search, citations, metrics, and classifications. Each tool earns its place without redundancy.
Coverage is broad: search and retrieval for authors and affiliations, publication search, citation overview, PlumX metrics, and subject classifications. The main gap is a document-level retrieval tool (e.g., fetch a specific publication by DOI/EID), which agents must currently work around.