Compatible with every major AI agent and IDE
What is the Calibre-Web MCP Server?
Connect your Calibre-Web instance to any AI agent and interact with your digital book collection using natural language. This server provides tools to navigate your library structure and prepare books for e-reader synchronization.
What you can do
- OPDS Catalog Access — Retrieve the main OPDS XML feed to browse your entire library structure, categories, and recent additions.
- Shelf Browsing — Query specific shelf IDs to list books within curated collections or user-defined categories.
- Kobo Synchronization — Fetch structured metadata and secure download links optimized for Kobo devices using your dedicated sync token.
- Library Inspection — Use the AI to find specific book entries and metadata within your self-hosted instance.
How it works
- Subscribe to this server
- Enter your Calibre-Web instance URL and optional credentials
- Start exploring your library from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Avid Readers — quickly find books in large collections without manual searching
- Digital Librarians — verify shelf contents and catalog structures via chat
- Kobo Users — automate the retrieval of sync metadata for your e-reader devices
Built-in capabilities (3)
Useful for browsing the library structure. Get the main OPDS catalog feed
Get the OPDS feed for a specific shelf
Requires Kobo Token. Sync Kobo library
Why CrewAI?
When paired with CrewAI, Calibre-Web becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Calibre-Web 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
Calibre-Web in CrewAI
Calibre-Web and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Calibre-Web 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 Calibre-Web in CrewAI
The Calibre-Web 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 3 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
Calibre-Web for CrewAI
Every tool call from CrewAI to the Calibre-Web MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I browse my entire library structure through the AI?
Yes. By using the get_opds_catalog tool, the agent retrieves the root XML feed of your Calibre-Web instance, allowing it to see categories, authors, and series as defined in your OPDS settings.
How do I list books from a specific custom shelf?
You can use the get_opds_shelf tool by providing the specific shelf_id. The AI will then return the list of books and metadata associated with that particular shelf.
Does this support syncing my Kobo e-reader?
Yes. If you provide your CALIBRE_WEB_KOBO_TOKEN, you can use the sync_kobo_library tool to get structured metadata and download links specifically formatted for Kobo device synchronization.
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 →
Cohere (Embed & Rerank)
6 toolsEmpower RAG via Cohere — generate high-quality text embeddings, rerank documents for better accuracy, and perform AI classification directly from any AI agent.

Pipeliner
10 toolsManage sales pipelines and opportunities via Pipeliner CRM — list leads, track deals, and monitor activities directly from any AI agent.

FCC Telecom
2 toolsSearch the official USA telecommunications database to audit corporate Internet Providers and Interconnected VoIP carriers.

NVIDIA Vision
9 toolsGenerate images, analyze visuals, detect objects, and caption images via NVIDIA Vision APIs.
