Booklet

What the booklet MCP server does

The booklet MCP server gives MCP-compatible assistants access to Booklet's page-management API. It is intended for workflows where an assistant needs to publish Markdown, revise an existing page, inspect page content, enumerate pages, or remove a page. The server works with Booklet's authenticated API and uses the same API keys as the REST interface.

Published pages are also available as MCP resources. An assistant can browse or read a page through a booklet://pages/:id resource URI, in addition to calling page-management tools. The repository also defines five prompts for common document types: incident reports, Architecture Decision Records, release notes, RFCs, and runbooks.

How it works

The hosted service is available at https://booklet-mcp.ashwinsathian.com/mcp. Clients send the Booklet API key in an Authorization: Bearer <bklt_...> header. The MCP process then exposes Booklet operations through the protocol while Booklet handles page storage and API authentication.

The available tools are publish_page, update_page, get_page, list_pages, and delete_page. These correspond to creating a page, changing one, retrieving one, listing pages, and deleting one. Page content is Markdown, matching Booklet's normal publishing model. This makes the booklet MCP server suitable for assistants that generate documentation or maintain pages after reviewing source material.

Setup and configuration

Point an MCP-compatible client at the hosted endpoint and provide a Booklet API key as the bearer credential. The project documentation provides copy-ready setup examples for Claude Desktop, Claude.ai, Cursor, Windsurf, VS Code, and Zed. API keys are the same credentials used by Booklet's REST API.

For local development, enter the mcp-server directory and run npm run dev. The README describes the MCP implementation as a plain Node process run under PM2 alongside the main application. The hosted service is not described as a Cloudflare Worker; that earlier deployment approach was replaced.

Tools and capabilities

• Publish new Markdown pages with publish_page.
• Change existing pages with update_page.
• Read individual pages with get_page.
• Enumerate available pages with list_pages.
• Remove pages with delete_page.
• Read published pages through booklet://pages/:id resources.
• Fill and publish incident reports, ADRs, release notes, RFCs, and runbooks using built-in prompts.

The MCP layer focuses on page operations. Booklet itself also offers a CLI, REST API, version history, analytics, collections, password protection, custom slugs, and other product features, but those are not listed as separate MCP tools in the provided material.

Limitations and notes

The server requires a valid Booklet API key and an MCP client that can connect to the supplied endpoint. The provided documentation does not list environment variable names for configuring the hosted MCP connection. It also does not specify additional MCP tools for API-key administration, collections, analytics, version history, or webhooks.

The local command starts the MCP server for development, but the excerpt does not provide a separate local endpoint, a complete local configuration file, or detailed request schemas for each tool. Consult Booklet's MCP setup page and API documentation for client-specific configuration and payload details.