Compatible with every major AI agent and IDE
What is the Elsevier ScienceDirect MCP Server?
Connect to Elsevier ScienceDirect to empower your AI agent with the world's leading source of scientific, technical, and medical research. This MCP server allows for deep exploration of peer-reviewed literature, metadata retrieval, and access rights verification.
What you can do
- Search & Discovery — Use advanced Boolean queries via
search_sciencedirectto find articles, journals, and books across the entire database. - Full-Text & Abstracts — Retrieve complete article content or concise abstracts using
get_articlewith PII, DOI, or Scopus IDs. - Metadata & Citations — Fetch detailed metadata for institutional repositories or citation management using
get_article_metadata. - Journal & Book Insights — Access specific metadata for serials (ISSN) via
get_serial_titleand non-serials (ISBN) viaget_nonserial_title. - Access Verification — Check entitlements and hosting permissions using
get_article_entitlementandget_hosting_permissionsto ensure compliant content usage.
How it works
- Subscribe to this server
- Enter your Elsevier API Key (and optional Institutional Token)
- Start querying scientific literature from Claude, Cursor, or any MCP-compatible client
No more manual searching through web portals. Your AI acts as a research assistant capable of fetching precise data from the ScienceDirect ecosystem.
Who is this for?
- Researchers & Academics — instantly retrieve paper abstracts and full texts without leaving the research environment
- Data Scientists — automate the collection of metadata and subject classifications for literature reviews
- Librarians & Repository Managers — verify hosting permissions and entitlements for institutional compliance
Built-in capabilities (9)
Retrieve full-text or abstract of an article
Check user access rights for an article
Retrieve article metadata lookups
Retrieve embargo and hosting information
Retrieve metadata for books by ISBN
Retrieve multimedia or attachments for an article
Retrieve metadata for journals by ISSN
Retrieve subject categories
Search full-text content on ScienceDirect
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Elsevier ScienceDirect through native MCP adapters. Connect 9 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Elsevier ScienceDirect MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Elsevier ScienceDirect queries for multi-turn workflows
Elsevier ScienceDirect in LangChain
Elsevier ScienceDirect and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Elsevier ScienceDirect to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Elsevier ScienceDirect in LangChain
The Elsevier ScienceDirect MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Elsevier ScienceDirect for LangChain
Every tool call from LangChain to the Elsevier ScienceDirect MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for specific authors or titles using this server?
Yes! Use the search_sciencedirect tool with specific query syntax like auth(name) for authors or tak(query) for Title/Abstract/Keywords to find exactly what you need.
How do I check if my institution has access to a specific paper?
You can use the get_article_entitlement tool. By providing the DOI or PII, the agent will verify if the authenticated user or institution has the rights to access the full text.
Can I retrieve metadata for a journal if I only have the ISSN?
Absolutely. Use the get_serial_title tool and provide the ISSN. The agent will return the journal's metadata, including title and subject classifications.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
ProcessOn
10 toolsOnline flowchart and mind mapping platform — manage diagrams, collaborations, and exports via AI.

Capsulink
9 toolsManage shortened URLs via Capsulink — create links, track clicks, and monitor analytics directly from any AI agent.

MENU TIGER
10 toolsCreate digital restaurant menus with QR code ordering, table management, and payment integration that modernize the dining experience.

Surveypal
12 toolsDesign employee experience surveys and customer feedback programs with analytics that turn responses into actionable improvements.
