Skip to main content
Glama
ridhwaan-ai

io.github.ridhwaan-ai/pressready

by ridhwaan-ai
README.md
# 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 -->
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

## 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.

## 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.

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 issues