Zotero MCP Server for CrewAIGive CrewAI instant access to 23 tools to Create Items, Delete Item, Delete Items, and more

Name: Zotero
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Zotero MCP Server for CrewAI is a standout in the Productivity category — giving your AI agent 23 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

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Zotero Specialist",
    goal="Help users interact with Zotero effectively",
    backstory=(
        "You are an expert at leveraging Zotero 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 Zotero "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 23 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Zotero MCP Server

Connect your Zotero library to any AI agent and take full control of your research workflow through natural conversation.

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

Collections & Organization — List top-level collections, subcollections, and specific collection details to navigate your library structure.
Item Management — Query all items, including notes and attachments, with support for advanced filtering by type, tag, or keyword.
Metadata Inspection — Fetch complete bibliographic data, creator information, and publication details for any specific item.
Tags & Publications — Access your personal publications and manage tags to categorize your research effectively.
Group Libraries — Seamlessly switch between your personal library and shared group libraries using specific IDs.

The Zotero MCP Server exposes 23 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 23 Zotero tools available for CrewAI

When CrewAI connects to Zotero through Vinkius, your AI agent gets direct access to every tool listed below — spanning reference-management, citation-tools, academic-research, 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.

create

Create items on Zotero

Use get_new_item_template first to get the correct schema. Create new items in the Zotero library

delete

Delete item on Zotero

Delete a single item

delete

Delete items on Zotero

Delete multiple items (up to 50)

get

Get collection on Zotero

Get a specific collection by key

get

Get deleted on Zotero

Get deleted objects since a specific library version

get

Get item on Zotero

Get a specific item by key

get

Get item type fields on Zotero

List valid fields for a specific item type

get

Get new item template on Zotero

Get a JSON template for creating a new item of a specific type

get

Get tag on Zotero

Get tags matching a specific name

list

List collection items on Zotero

List items in a specific collection

list

List collections on Zotero

List all collections in the Zotero library

list

List item children on Zotero

List child items (notes, attachments) for a specific item

list

List item fields on Zotero

List all available Zotero item fields

list

List item tags on Zotero

List tags for a specific item

list

List item types on Zotero

List all available Zotero item types

list

List items on Zotero

List items in the Zotero library

list

List publications on Zotero

List items in My Publications

list

List subcollections on Zotero

List subcollections of a specific collection

list

List tags on Zotero

List all tags in the library

list

List top collections on Zotero

List top-level collections in the Zotero library

list

List top items on Zotero

List top-level items in the Zotero library

list

List trash items on Zotero

List items in the trash

update

Update item on Zotero

Update an existing item (Partial Update / PATCH)

Connect Zotero to CrewAI via MCP

Follow these steps to wire Zotero into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 23 tools from Zotero

Why Use CrewAI with the Zotero MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Zotero through the Model Context Protocol.

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

Zotero + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Zotero MCP Server delivers measurable value.

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

Scheduled intelligence reports: set up a crew that periodically queries Zotero, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Zotero tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Zotero against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Zotero in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Zotero immediately.

"List all my top-level collections in Zotero."

"Search for items in my library with the tag 'artificial-intelligence'."

"Get the complete bibliographic details for item key ABCD1234."

Troubleshooting Zotero MCP Server with CrewAI

Common issues when connecting Zotero to CrewAI through Vinkius, and how to resolve them.

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.

Zotero + CrewAI FAQ

Common questions about integrating Zotero MCP Server with CrewAI.

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.