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

Bring Academic Research
to CrewAI

Learn how to connect DOAJ to CrewAI and start using 8 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
Bulk Create ArticlesCreate ApplicationCreate ArticleDelete ArticleGet ArticleSearch ArticlesSearch JournalsUpdate Article

Compatible with every major AI agent and IDE

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

What is the DOAJ MCP Server?

Connect to the Directory of Open Access Journals (DOAJ) to explore millions of open access articles and journals. This server allows researchers to query metadata and publishers to manage their records through natural conversation.

What you can do

  • Journal Discovery — Search the DOAJ database for journals using Elasticsearch syntax, including title, ISSN, and subject filters.
  • Article Search — Find specific research papers and articles across thousands of open access publications.
  • Metadata Retrieval — Fetch complete metadata for specific articles using their unique DOAJ IDs.
  • Publisher Management — Create, update, or delete article records directly from your AI agent (requires API key).
  • Bulk Operations — Upload high-volume batches of articles asynchronously for efficient catalog management.
  • Journal Applications — Submit update requests for existing journals to keep directory information current.

How it works

  1. Subscribe to this server
  2. (Optional) Enter your DOAJ API Key for publisher features
  3. Start searching or managing academic content from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Researchers & Academics — quickly find open access sources and metadata without manual database browsing
  • Publishers — manage article listings and journal updates directly from a command-line or AI interface
  • Librarians & Data Scientists — automate the retrieval of scholarly metadata for analysis or cataloging

Built-in capabilities (8)

bulk_create_articles

Requires publisher API key. Keep batch sizes around 600KB. Bulk upload articles to DOAJ

create_application

Include the journal ID in admin.current_journal. Submit an update request (application) for an existing journal

create_article

Requires publisher API key. Creating an article with an existing DOI or full-text URL will overwrite the existing record. Create a new article in DOAJ

delete_article

Requires publisher API key. Delete an article from DOAJ

get_article

Retrieve a specific DOAJ article by ID

search_articles

Supports fielded search (e.g., bibjson.title:"Quantum"). Search DOAJ articles using Elasticsearch query string syntax

search_journals

Supports fielded search (e.g., bibjson.title:"Journal of Science"). Search DOAJ journals using Elasticsearch query string syntax

update_article

Requires publisher API key. Update an existing DOAJ article

Why CrewAI?

When paired with CrewAI, DOAJ becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call DOAJ 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

DOAJ in CrewAI

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

DOAJ and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect DOAJ 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 DOAJ in CrewAI

The DOAJ 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 8 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.

DOAJ
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 DOAJ for CrewAI

Every tool call from CrewAI to the DOAJ 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 journals using specific fields like title or ISSN?

Yes! Use the search_journals tool with Elasticsearch query string syntax. For example, you can query bibjson.title:"Journal of Science" or bibjson.pissn:"1234-5678" to find exact matches.

02

How do I submit a batch of new articles at once?

You can use the bulk_create_articles tool. It allows you to submit a JSON array of article objects asynchronously. This is ideal for publishers managing high volumes of data.

03

Is it possible to request updates for an existing journal listing?

Yes, publishers can use the create_application tool to submit an update request for an existing journal by providing the updated metadata and referencing the current journal ID.

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 →