Anthra developer platform

Build with Anthra

Anthra exposes two programmatic surfaces on top of the same studio that powers /dashboard:

  • REST API at /api/v1/* — JSON in, JSON out (plus streamed text/plain for chapter generation).
  • MCP server at /api/mcp — connect Claude, Cursor, or any Model Context Protocol client with a personal access token and Anthra appears as a set of callable tools.

Both surfaces use the same authentication, the same scopes, and the same underlying database — you can mix them freely.

Start here

What you can do

CapabilityRESTMCP toolScope
List / read booksGET /v1/bookslist_books, get_bookbooks:read
Create or edit a bookPOST /v1/books, PATCH /v1/books/{id}create_book, update_bookbooks:write
Generate outlinePOST /v1/books/{id}/outlinegenerate_outlinegeneration:run
Write / rewrite a chapterPOST …/chapters/{cid}/write (stream)write_chapter, rewrite_chaptergeneration:run
Narrate with ElevenLabsPOST …/chapters/{cid}/narratenarrate_chaptergeneration:run
Publish / unpublishPOST /v1/books/{id}/publishpublish_book, unpublish_bookpublish:write
Reader analyticsGET /v1/books/{id}/analyticsget_reader_analyticsanalytics:read
Account + token usageGET /v1/account, GET /v1/usageget_usageaccount:read

Versioning

The REST surface is namespaced by version (/api/v1). Anthra will introduce a new namespace before making any breaking change; v1 is stable and additive-only.