Scopus MCP integration for AI agents.
Connect AI agents to Scopus through 7 structured actions, including get abstract, get affiliation, and get author. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Scopus integration exposes
The Scopus Agent App exposes 7 provider-backed actions for data work. Its current contract lets an authorized agent get one scopus abstract record by a documented document identifier, get scopus affiliation profile data by affiliation id or eid, and get scopus author profile data by author id, eid, or orcid. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Scopus account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Scopus capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_abstractREADGet one Scopus abstract record by a documented document identifier.
INPUTS: identifierType / identifier / view / fields / referenceStart
get_affiliationREADGet Scopus affiliation profile data by affiliation ID or EID.
INPUTS: identifierType / identifier / view / fields / referenceStart
get_authorREADGet Scopus author profile data by author ID, EID, or ORCID.
INPUTS: identifierType / identifier / view / fields / resolveAliases
search_affiliationsREADSearch Scopus affiliation profiles with the official Boolean query syntax and return one normalized result page.
INPUTS: query / fields / start / count / sort
search_authorsREADSearch Scopus author profiles with the official Boolean query syntax and return one normalized result page.
INPUTS: query / fields / start / count / sort
search_documentsREADSearch Scopus documents with the official Boolean query syntax and return one normalized result page.
INPUTS: query / view / fields / start / count
search_sourcesREADSearch Scopus serial sources by title, ISSN, publisher, subject, content type, or open-access status.
INPUTS: title / issn / publisher / subjectArea / subjectCode
INPUT CONTRACTS
Know what the action needs before it runs.
get_abstract
identifierTypeREQUIRED- The identifier namespace used by the supplied value.
identifierREQUIRED- The document identifier in the selected namespace.
viewOPTIONAL- The Abstract Retrieval response view.
fieldsOPTIONAL- A comma-separated list of official Elsevier response fields. Supplying fields overrides the selected view.
referenceStartOPTIONAL- The zero-based result offset.
get_affiliation
identifierTypeREQUIRED- The identifier namespace used by the supplied value.
identifierREQUIRED- The affiliation identifier in the selected namespace.
viewOPTIONAL- The Affiliation Retrieval response view.
fieldsOPTIONAL- A comma-separated list of official Elsevier response fields. Supplying fields overrides the selected view.
referenceStartOPTIONAL- The zero-based result offset.
get_author
identifierTypeREQUIRED- The identifier namespace used by the supplied value.
identifierREQUIRED- The author identifier in the selected namespace.
viewOPTIONAL- The Author Retrieval response view.
fieldsOPTIONAL- A comma-separated list of official Elsevier response fields. Supplying fields overrides the selected view.
resolveAliasesOPTIONAL- Whether Elsevier should substitute a superseded author profile with its current alias.
search_affiliations
queryREQUIRED- The official Scopus Affiliation Search query, such as AFFIL(University of Oxford).
fieldsOPTIONAL- A comma-separated list of official Elsevier response fields. Supplying fields overrides the selected view.
startOPTIONAL- The zero-based result offset.
countOPTIONAL- The maximum number of results to return.
sortOPTIONAL- An official Elsevier sort expression. Prefix a field with + or - and separate up to three fields with commas.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Abstract
Get one Scopus abstract record by a documented document identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_abstractVerify with Get Affiliation
Get Scopus affiliation profile data by affiliation ID or EID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_affiliationSAFETY BOUNDARY
Operate Scopus with explicit limits
- Authorize Scopus with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Scopus data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Scopus rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Scopus task completed successfully.
CONNECTION MODEL
API key
Elsevier API key sent in the X-ELS-APIKey header. Create or manage a key at https://dev.elsevier.com/apikey/manage and review the official API policies at https://dev.elsevier.com/policy.html
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Scopus.