Compatible with every major AI agent and IDE
What is the Scopus MCP Server?
Connect your Scopus API credentials to any AI agent and unlock the power of Elsevier's massive research database through natural conversation.
What you can do
- Advanced Search — Query Scopus abstracts and metadata using Boolean syntax and field codes like TITLE-ABS-KEY() or PUBYEAR
- Author & Institution Profiles — Retrieve detailed profiles, including H-index, affiliation history, and publication lists
- Citation Metrics — Get comprehensive citation overviews, counts, and summaries by year for any document via DOI or Scopus ID
- Journal Insights — Access metadata for serials including CiteScore, SJR, and SNIP metrics to evaluate publication impact
- PlumX Metrics — Inspect social media mentions, usage, and altmetrics to understand the broader reach of scientific work
How it works
- Subscribe to this server
- Enter your Scopus API Key (and optional Institutional Token)
- Start conducting literature reviews and bibliometric analysis from Claude, Cursor, or any MCP client
Who is this for?
- Researchers & Academics — quickly find relevant literature and track citation trends without manual database exports
- Data Scientists — integrate high-quality metadata and metrics into research workflows and knowledge graphs
- University Administrators — audit institutional output and author profiles with ease
Built-in capabilities (10)
Get detailed metadata for a specific document
Get detailed profile for an institution
Get detailed profile for a specific author
Get abstract citation count
Get citation counts and summaries by year
Get Altmetrics for Scopus documents
Get metadata about journals (metrics like CiteScore, SJR, SNIP)
Search Scopus institutional profiles
Search Scopus author profiles
Search Scopus abstracts and metadata
Why CrewAI?
When paired with CrewAI, Scopus becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Scopus tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Scopus in CrewAI
Scopus and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Scopus to CrewAI 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 Scopus in CrewAI
The Scopus 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 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI 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
Scopus for CrewAI
Every tool call from CrewAI to the Scopus 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 using their names or ORCID?
Yes! Use the search_author tool to find profiles by name or affiliation, or use get_author if you already have a specific Scopus Author ID to retrieve their full metrics and H-index.
How do I get a breakdown of citations per year for a specific paper?
You can use the get_citation_overview tool. Provide the DOI or Scopus ID and an optional date range (e.g., 2018-2023) to see how the document's impact has evolved over time.
Can the AI help me evaluate the quality of a journal?
Absolutely. By using the get_serial_title tool, your agent can retrieve official metrics like CiteScore, SJR (SCImago Journal Rank), and SNIP (Source Normalized Impact per Paper) for any journal.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
OpenCritic
8 toolsUnified video game review platform — access scores, critic reviews, and rankings via AI.

Chameleon.io
8 toolsManage product adoption and onboarding via Chameleon — trigger tours, analyze surveys, and track user events directly from any AI agent.

Travelport
21 toolsAccess Travelport's Global Distribution System to search and book flights, hotels, and manage travel reservations directly through AI.

Stigg
12 toolsAutomate billing and subscription management via Stigg — provision customers, manage plans, and report usage directly from any AI agent.
