4,000+ servers built on vurb.ts
Vinkius

CORE (Open Access Research) MCP Server for CrewAIGive CrewAI instant access to 10 tools to Get Article, Get Article History, Get Article Pdf, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to CORE (Open Access Research) through Vinkius, pass the Edge URL in the `mcps` parameter and every CORE (Open Access Research) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The CORE (Open Access Research) MCP Server for CrewAI is a standout in the Knowledge Management category — giving your AI agent 10 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="CORE (Open Access Research) Specialist",
    goal="Help users interact with CORE (Open Access Research) effectively",
    backstory=(
        "You are an expert at leveraging CORE (Open Access Research) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in CORE (Open Access Research) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
CORE (Open Access Research)
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

About 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.

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.

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.

The CORE (Open Access Research) MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 10 CORE (Open Access Research) tools available for CrewAI

When CrewAI connects to CORE (Open Access Research) through Vinkius, your AI agent gets direct access to every tool listed below — spanning open-access, research-papers, academic-search, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get article on CORE (Open Access Research)

Get a specific article by CORE ID

get

Get article history on CORE (Open Access Research)

Get the history of an article

get

Get article pdf on CORE (Open Access Research)

Get the PDF download URL for an article

get

Get journal on CORE (Open Access Research)

Get a specific journal by ISSN

get

Get repository on CORE (Open Access Research)

Get a specific repository by ID

global

Global search on CORE (Open Access Research)

Global search across CORE

resolve

Resolve oai on CORE (Open Access Research)

Resolve an OAI identifier

search

Search articles on CORE (Open Access Research)

Search for articles

search

Search journals on CORE (Open Access Research)

Search for journals

search

Search repositories on CORE (Open Access Research)

Search for repositories

Connect CORE (Open Access Research) to CrewAI via MCP

Follow these steps to wire CORE (Open Access Research) into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from CORE (Open Access Research)

Why Use CrewAI with the CORE (Open Access Research) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with CORE (Open Access Research) through the Model Context Protocol.

01

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

02

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

03

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

04

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) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the CORE (Open Access Research) MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries CORE (Open Access Research) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries CORE (Open Access Research), analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain CORE (Open Access Research) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries CORE (Open Access Research) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for CORE (Open Access Research) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with CORE (Open Access Research) immediately.

01

"Search CORE for the latest research on transformer architectures in NLP."

02

"Get the PDF download link for the article with CORE ID 123456."

03

"Find information about the journal with ISSN 2041-1723."

Troubleshooting CORE (Open Access Research) MCP Server with CrewAI

Common issues when connecting CORE (Open Access Research) to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

CORE (Open Access Research) + CrewAI FAQ

Common questions about integrating CORE (Open Access Research) MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →