CrewAIFramework

BookStack (Wiki) MCP Server

Bring Wiki
to CrewAI

Name: BookStack (Wiki) MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect BookStack (Wiki) to CrewAI and start using 32 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Create AttachmentCreate BookCreate ChapterCreate PageCreate ShelfDelete AttachmentDelete BookDelete ChapterDelete PageDelete ShelfExport BookExport ChapterExport PageGet AttachmentGet BookGet ChapterGet PageGet ShelfGet System StatusList AttachmentsList Audit LogList BooksList ChaptersList PagesList Recycle BinList ShelvesSearchUpdate AttachmentUpdate BookUpdate ChapterUpdate PageUpdate Shelf

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the BookStack (Wiki) MCP Server?

Connect your BookStack instance to any AI agent and turn your documentation into an interactive knowledge base through natural conversation.

What you can do

Content Hierarchy — List and manage shelves, books, chapters, and pages using list_shelves, list_books, and list_pages to maintain perfect organization.
Smart Search — Find exactly what you need across your entire wiki instance with the powerful search tool.
Full Content Lifecycle — Create, update, or delete pages and chapters directly from your agent to keep documentation fresh.
Multi-format Export — Use export_page to retrieve content in PDF, Markdown, HTML, or Plaintext formats for external use.
System Oversight — Monitor your instance with get_system_status, check list_audit_log for recent changes, or manage the list_recycle_bin.
Attachments — Manage file attachments linked to your documentation using the dedicated attachment tools.

How it works

Subscribe to this server
Enter your BookStack URL, Token ID, and Token Secret
Start managing your knowledge base from Claude, Cursor, or any MCP-compatible client

Who is this for?

Documentation Leads — maintain and organize large wikis without manual navigation
Engineering Teams — search for technical specs and update READMEs directly from the IDE
Support Teams — quickly find and export help articles for customers

Built-in capabilities (32)

create_attachment

Create a new attachment link

create_book

Create a new book

create_chapter

Create a new chapter

create_page

Requires either book_id or chapter_id, name, and html or markdown. Create a new page in BookStack

create_shelf

Create a new shelf

delete_attachment

Delete an attachment

delete_book

Delete a book

delete_chapter

Delete a chapter

delete_page

Delete a page (moves to recycle bin)

delete_shelf

Delete a shelf

export_book

Export book content

export_chapter

Export chapter content

export_page

Export page content

get_attachment

Get details for a specific attachment

get_book

Get details for a specific book

get_chapter

Get details for a specific chapter

get_page

Get details for a specific page

get_shelf

Get details for a specific shelf

get_system_status

Check system version and status

list_attachments

List all attachments in BookStack

list_audit_log

View system activity audit log

list_books

List all books in BookStack

list_chapters

List all chapters in BookStack

list_pages

Supports pagination, sorting, and filtering. List all pages in BookStack

list_recycle_bin

List deleted items in the recycle bin

list_shelves

List all shelves in BookStack

Search across all content in BookStack

update_attachment

Update an existing attachment

update_book

Update an existing book

update_chapter

Update an existing chapter

update_page

Update an existing page

update_shelf

Update an existing shelf

Why CrewAI?

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

BookStack (Wiki) in CrewAI

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

BookStack (Wiki) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect BookStack (Wiki) 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 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

Unlock for AI Agents View step-by-step setup guide for CrewAI →

Enterprise Security

Why teams choose Vinkius for BookStack (Wiki) in CrewAI

The BookStack (Wiki) 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 32 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.

Unlock for AI Agents View full BookStack (Wiki) details →

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
BookStack (Wiki) for CrewAI

Every tool call from CrewAI to the BookStack (Wiki) 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

Can I search across all my books and chapters at once?

Yes! Use the search tool with your query string. It will return relevant results from pages, chapters, and books across your entire BookStack instance.

Is it possible to retrieve a page's content in Markdown format?

Absolutely. Use the export_page tool and set the format to 'markdown'. You can also export to PDF, HTML, or plaintext.

How do I see what was recently deleted?

You can use the list_recycle_bin tool to view items that have been moved to the recycle bin before they are permanently removed from the system.

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.