Bring Open Access
to CrewAI
Learn how to connect CORE (Open Access Research) 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.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the CORE (Open Access Research) MCP Server?
Connect to CORE, the world's largest aggregator of open access research papers. This MCP server allows your AI agent to search, retrieve, and analyze millions of scholarly articles, journals, and institutional repositories through natural conversation.
What you can do
- Global Search — Search across all CORE resources including articles, journals, and repositories using a single text query.
- Article Retrieval — Fetch full metadata, version history, and direct PDF download links for specific research papers using CORE IDs.
- Journal & Repository Discovery — Search and inspect specific journals by ISSN or explore institutional repositories to find authoritative sources.
- OAI Resolution — Resolve Open Archives Initiative (OAI) identifiers to access original metadata and repository pages.
- Deep Metadata Inspection — Analyze article history and updates to ensure you are working with the latest scientific information.
How it works
- Subscribe to this server
- Enter your CORE API Key
- Start researching directly from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Researchers & Academics — quickly find relevant papers and download PDFs without leaving your writing or coding environment.
- Students — gather citations, explore related research history, and find open access versions of paywalled content.
- Data Scientists — access a massive corpus of open access metadata for literature reviews and scientific data analysis.
Built-in capabilities (10)
Get a specific article by CORE ID
Get the history of an article
Get the PDF download URL for an article
Get a specific journal by ISSN
Get a specific repository by ID
Global search across CORE
Resolve an OAI identifier
Search for articles
Search for journals
Search for repositories
Why CrewAI?
When paired with CrewAI, CORE (Open Access Research) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CORE (Open Access Research) 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
CORE (Open Access Research) in CrewAI
CORE (Open Access Research) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect CORE (Open Access Research) 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 CORE (Open Access Research) in CrewAI
The CORE (Open Access Research) 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
CORE (Open Access Research) for CrewAI
Every tool call from CrewAI to the CORE (Open Access Research) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I get the PDF of a specific research article?
Use the get_article_pdf tool with the CORE Article ID. The agent will return the direct download URL for the open access PDF version of the paper.
Can I search for specific journals or repositories?
Yes! You can use search_journals or search_repositories for general text queries, or use get_journal (with an ISSN) and get_repository (with a Repository ID) for direct lookups.
What does the OAI resolution tool do?
The resolve_oai tool takes an OAI identifier (like oai:oro.open.ac.uk:75049) and resolves it to the CORE metadata page or the original repository link, helping you find the source of the research.
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 →
QuickNode
18 toolsManage blockchain infrastructure via QuickNode — create data streams, configure webhooks, and interact with RPC nodes directly from your AI agent.
Conduit
8 toolsEquip your AI agent to observe data streams, manage integration pipelines, and monitor nodes on the Conduit platform.
Kisi
10 toolsControl building access with cloud-managed smart locks, mobile credentials, and audit trails that replace traditional key cards.
Wrike
12 toolsCollaborative project management to manage tasks, projects, and team workflows with AI.