Skip to main content
Glama
io.github.ridhwaan-ai/pressready

io.github.ridhwaan-ai/pressready

by ridhwaan-ai

PressReady

Manuscript in, publish-ready book out. Give it Markdown chapters, metadata and a front-cover image. It returns:

  1. Kindle EPUB 3 (cover embedded, TOC, front/back matter)

  2. Print interior PDF at the requested trim size (5x8, 5.5x8.5, 6x9, 8.5x11)

  3. Full-wrap paperback cover PDF (spine width computed from page count and paper type)

  4. Upload checklist (JSON) with the values KDP asks for

mcp-name: io.github.ridhwaan-ai/pressready

Install: pip install pressready (or run without installing: uvx pressready mcp). Live API: https://pressready-wp38.onrender.com (agent docs: /llms.txt; pricing: /v1/pricing). Free tier: 3 builds a day per client; unlimited with a license key. The free host sleeps when idle, so the first request can take about a minute.

CLI

pip install pressready
pressready build manuscript/ --trim 5.5x8.5 --paper cream

Optional manuscript/book.json flags (used by the CLI and MCP; the API takes the same names as body fields): "print_toc": true adds a printed Contents page with page numbers to the interior PDF; "own_front_matter": true skips our title/copyright pages when your front matter already has them.

Related MCP server: cove-book-forge-mcp

MCP server

uvx pressready mcp

MCP client config:

{"mcpServers": {"pressready": {"command": "uvx", "args": ["pressready", "mcp"]}}}

Tools: build_book, spine_width, list_trim_sizes.

HTTP API

uvicorn pressready.api:app
  • POST /v1/books creates a job, GET /v1/books/{id} returns status and download URLs

  • GET /v1/limits, GET /v1/pricing: machine-readable limits and pricing

  • GET /llms.txt, GET /quickstart.txt: agent docs

  • GET /openapi.json: OpenAPI spec

  • GET /health: health check

Jobs are in memory and expire after about 15 minutes.

End-to-end example

HOST=https://pressready-wp38.onrender.com
COVER=$(base64 -w0 cover.png)   # PNG or JPG front cover
curl -X POST $HOST/v1/books -H 'content-type: application/json' -d '{
  "title": "My Book", "author": "A. Writer", "trim": "5.5x8.5", "paper": "cream",
  "chapters": [{"title": "One", "markdown": "# One\n\nHello."}],
  "cover_image_base64": "'"$COVER"'"}'
# -> {"id": "...", "status": "done", "checklist": {...}, "files": {"book.epub": "/v1/books/<id>/files/book.epub", ...}}
curl -O $HOST/v1/books/<id>/files/book.epub

Unlimited builds: add -H 'Authorization: Bearer <license key>' (key: https://stickfigurefiles.gumroad.com/l/zrvizy).

Claude Desktop / Cursor

Add the MCP client config above to claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor), restart the app, and ask it to build a book from your chapters.

Notes

PressReady produces files; it never logs in to KDP or any other site. Check the output in KDP's previewer before publishing. Output is generated by software; disclose AI use in KDP where its rules require it.

Available Tools

3 tools
build_bookA

Build a Kindle EPUB, print interior PDF, full-wrap cover PDF and KDP upload checklist.

manuscript_dir: folder containing book.json and Markdown chapters. cover_image: path to the front cover image (PNG/JPG). trim: one of 5x8, 5.5x8.5, 6x9, 8.5x11. paper: white or cream. Returns {"ok": true, ...checklist} or {"ok": false, "error": "what to fix"}.

Inputs: cover_image (required), manuscript_dir (required), trim, paper, +3 more.

list_trim_sizesA

List supported print trim sizes (inches).

Inputs: no named parameters.

spine_widthA

Compute KDP paperback spine width in inches for a page count and paper type (white or cream).

Inputs: pages (required), paper.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a highly specialized and distinct purpose within the book preparation workflow. One calculates a single dimension, one lists supported constants, and the other executes the entire complex build process.

    Naming Consistency4/5

    The tool names adhere to a consistent snake_case convention throughout. The verbs (spine_width, list_trim_sizes, build_book) are clear and follow a logical, action-oriented style.

    Tool Count4/5

    For the narrow, specialized scope of KDP preparation, three tools are reasonable. While the general guide suggests a slightly wider range, these tools cover the core lifecycle of dimension check, constraint listing, and final output.

    Completeness3/5

    The set covers basic dimensional requirements and the final output, but lacks critical intermediate steps. There are no tools for validating manuscript content against KDP requirements or handling the actual submission/upload process.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers