BookStack (Wiki) MCP Server for CrewAIGive CrewAI instant access to 32 tools to Create Attachment, Create Book, Create Chapter, and more

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

GDPR Free for Subscribers

Connect your CrewAI agents to BookStack (Wiki) through Vinkius, pass the Edge URL in the `mcps` parameter and every BookStack (Wiki) 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 BookStack (Wiki) MCP Server for CrewAI is a standout in the Collaboration category — giving your AI agent 32 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="BookStack (Wiki) Specialist",
    goal="Help users interact with BookStack (Wiki) effectively",
    backstory=(
        "You are an expert at leveraging BookStack (Wiki) 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 BookStack (Wiki) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 32 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 BookStack (Wiki) MCP Server

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

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.

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.

The BookStack (Wiki) MCP Server exposes 32 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 32 BookStack (Wiki) tools available for CrewAI

When CrewAI connects to BookStack (Wiki) through Vinkius, your AI agent gets direct access to every tool listed below — spanning wiki, documentation, knowledge-base, 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 attachment on BookStack (Wiki)

Create a new attachment link

create

Create book on BookStack (Wiki)

Create a new book

create

Create chapter on BookStack (Wiki)

Create a new chapter

create

Create page on BookStack (Wiki)

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

create

Create shelf on BookStack (Wiki)

Create a new shelf

delete

Delete attachment on BookStack (Wiki)

Delete an attachment

delete

Delete book on BookStack (Wiki)

Delete a book

delete

Delete chapter on BookStack (Wiki)

Delete a chapter

delete

Delete page on BookStack (Wiki)

Delete a page (moves to recycle bin)

delete

Delete shelf on BookStack (Wiki)

Delete a shelf

export

Export book on BookStack (Wiki)

Export book content

export

Export chapter on BookStack (Wiki)

Export chapter content

export

Export page on BookStack (Wiki)

Export page content

get

Get attachment on BookStack (Wiki)

Get details for a specific attachment

get

Get book on BookStack (Wiki)

Get details for a specific book

get

Get chapter on BookStack (Wiki)

Get details for a specific chapter

get

Get page on BookStack (Wiki)

Get details for a specific page

get

Get shelf on BookStack (Wiki)

Get details for a specific shelf

get

Get system status on BookStack (Wiki)

Check system version and status

list

List attachments on BookStack (Wiki)

List all attachments in BookStack

list

List audit log on BookStack (Wiki)

View system activity audit log

list

List books on BookStack (Wiki)

List all books in BookStack

list

List chapters on BookStack (Wiki)

List all chapters in BookStack

list

List pages on BookStack (Wiki)

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

list

List recycle bin on BookStack (Wiki)

List deleted items in the recycle bin

list

List shelves on BookStack (Wiki)

List all shelves in BookStack

action

Search on BookStack (Wiki)

Search across all content in BookStack

update

Update attachment on BookStack (Wiki)

Update an existing attachment

update

Update book on BookStack (Wiki)

Update an existing book

update

Update chapter on BookStack (Wiki)

Update an existing chapter

update

Update page on BookStack (Wiki)

Update an existing page

update

Update shelf on BookStack (Wiki)

Update an existing shelf

Connect BookStack (Wiki) to CrewAI via MCP

Follow these steps to wire BookStack (Wiki) 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 32 tools from BookStack (Wiki)

Why Use CrewAI with the BookStack (Wiki) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with BookStack (Wiki) 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

BookStack (Wiki) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the BookStack (Wiki) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries BookStack (Wiki) 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 BookStack (Wiki), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain BookStack (Wiki) 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 BookStack (Wiki) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for BookStack (Wiki) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with BookStack (Wiki) immediately.

"Search my BookStack wiki for 'security policy'."

"Create a new page titled 'Onboarding' in book ID 5 with some basic HTML content."

"Export the 'API Reference' page (ID: 88) as a PDF."

Troubleshooting BookStack (Wiki) MCP Server with CrewAI

Common issues when connecting BookStack (Wiki) 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.

BookStack (Wiki) + CrewAI FAQ

Common questions about integrating BookStack (Wiki) 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.