| name | bookstack-mcp-connector |
| description | MCP connector for BookStack documentation platform – enables AI-powered documentation creation, organization, and search through Claude |
| license | MIT |
| tags | ["dev","documentation","mcp","bookstack","wiki"] |
| difficulty | beginner |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Bookstack MCP Connector
Overview
This skill enables Claude to interact with Bookstack through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Bookstack's REST API, allowing natural language control of Bookstack operations, intelligent automation, and AI-powered assistance for Bookstack workflows.
When to Use This Skill
- Book/chapter/page hierarchy creation from outlines
- Content generation and formatting
- Search and cross-reference management
- Permission and role configuration
- Export and backup management
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Bookstack │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Bookstack operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/api/books, /api/chapters, /api/pages, /api/shelves, /api/search
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "bookstack-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Bookstack resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/api/books`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"bookstack-mcp-connector": {
"command": "node",
"args": ["path/to/bookstack-mcp-connector/index.js"],
"env": {
"BOOKSTACK_API_KEY": "your-api-key",
"BOOKSTACK_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Bookstack API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Bookstack API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a technical documentation book with chapters for Setup, API Reference, and Troubleshooting"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.