Scopus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCOPUS_API_KEY | Yes | Your API key for the Elsevier Scopus API, obtainable from the Elsevier Developer Portal (https://dev.elsevier.com/). |
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": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_scopusC | Search for documents in Scopus using a query string. |
| get_abstract_detailsC | Retrieve full details for a specific document by Scopus ID. |
| get_author_profileC | Retrieve an author's profile by Author ID. |
| get_citing_papersC | Retrieve a list of papers that have cited the specified document (Forward Citations). |
| get_quota_statusA | Get the current API quota status (remaining/limit). Note: Values are updated only after making a request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| research-summary | Search for papers on a topic and generate a research summary |
| author-analysis | Analyze an author's research impact and recent work |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: get_abstract_details retrieves document details, get_author_profile gets author information, get_citing_papers finds citations, get_quota_status checks API limits, and search_scopus performs searches. The descriptions make it easy to differentiate between document, author, citation, quota, and search operations.
All tools follow a consistent verb_noun pattern using snake_case: get_abstract_details, get_author_profile, get_citing_papers, get_quota_status, and search_scopus. The naming is predictable and readable throughout the set, with 'get_' prefix for retrieval operations and 'search_' for the search function.
With 5 tools, this server is well-scoped for a Scopus API interface. Each tool serves a distinct and essential function for academic research workflows, such as retrieving documents, authors, citations, checking quotas, and searching. The count is neither too sparse nor bloated, fitting the domain appropriately.
The tool set covers core Scopus operations well: search, retrieve document details, author profiles, and citations, plus quota management. A minor gap is the lack of tools for related operations like backward citations (references) or advanced filtering options, but agents can work around this with the provided tools for most common tasks.