4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Scopus MCP Server

Bring Academic Literature
to CrewAI

Learn how to connect Scopus to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get AbstractGet AffiliationGet AuthorGet Citation CountGet Citation OverviewGet Plumx MetricsGet Serial TitleSearch AffiliationSearch AuthorSearch Scopus

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Scopus

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

  1. Subscribe to this server
  2. Enter your Scopus API Key (and optional Institutional Token)
  3. 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_abstract

Get detailed metadata for a specific document

get_affiliation

Get detailed profile for an institution

get_author

Get detailed profile for a specific author

get_citation_count

Get abstract citation count

get_citation_overview

Get citation counts and summaries by year

get_plumx_metrics

Get Altmetrics for Scopus documents

get_serial_title

Get metadata about journals (metrics like CiteScore, SJR, SNIP)

search_affiliation

Search Scopus institutional profiles

search_author

Search Scopus author profiles

search_scopus

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 mcps parameter 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

See it in action

Scopus in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

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.

Scopus
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

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.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

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 →