Skip to content

Kavita alongside Maki

Maki writes plain CBZ files with ComicInfo.xml, so Kavita can read the same library. Connecting Kavita is optional. It lets Maki ask Kavita to scan new files, send covers and metadata, and keep read status in step.

Point Kavita and Maki at the same folder. In Docker that means mounting the same host folder into both containers. See Docker Compose and Volumes and permissions.

Under Settings → Integrations → Kavita, enter the URL and API key (in Kavita under User Settings → 3rd Party Clients). If Kavita sees the folder under a different path, which is common in Docker, also set the path mapping:

  • Path as Maki sees it: the library folder as Maki sees it.
  • Path as Kavita sees it: the same folder as Kavita sees it, for example /manga.

Once Kavita is connected, none of this needs a switch:

  • After a download, import or move, Maki asks Kavita to scan that series folder. Kavita runs the scan about a minute later. If the request fails, Maki tries again after one, two and four minutes.
  • Chapter files carry your Maki tags in ComicInfo’s SeriesGroup field, so Kavita can build collections from them. Changing a tag rewrites no files: new downloads get the current tags, and the ComicInfo bulk action brings existing files up to date.
  • Once Kavita has created the series, Maki sends the MangaBaka poster as its cover, the web links and the publication status.
  • Reading in Kavita is scrobbled to your trackers, checked every 30 minutes by default. Sync now on the Scrobble page checks straight away. See Trackers.

Maki matches a series to its Kavita counterpart by title or folder name, ignoring punctuation. A Kavita series with a very different name does not link to a series in Maki.

Under Settings → Reading → Kavita read sync:

  • Mark chapters read in Kavita too sends reads from Maki to Kavita. It only applies to series that match a Kavita series.
  • Mark chapters read here as soon as they’re read in Kavita pulls reads from Kavita live. Kavita only sends reading updates to admin accounts, so the API key must belong to a Kavita admin. Maki shows a message when it does not.
  • Import read status copies read state from Kavita once. It is safe to run again, and it never marks anything unread. Kavita does not say when those chapters were read, so the import does not add them to Rewind.

Kavita has one API key, so its reading belongs to one Maki account. Choose it under Settings → Integrations → Kavita → Attribute Kavita’s reading to. If empty, the lowest-numbered admin is used. Only that account imports from Kavita or pushes reads back. If the read sync switches say Kavita’s reading belongs to another Maki account, the chosen account is not yours.

Scrobble reading from these libraries on the same card limits which Kavita libraries are read. Leave it empty to read all of them.