Support

Getting help

Write to hello@saybooks.io. Every message is read by Peter Varga, who builds Saybooks, and answered by him. Bugs and ideas can also go on GitHub.

What to put in the message

Connecting an assistant

The steps for Claude are in the docs, and Gemini has its own section; any other assistant that connects to MCP servers with a sign-in works the same way. The usual address is https://saybooks.io/mcp; narrower doors such as /mcp/household open one kind of books and keep the tool list short. You sign in with Google and choose which books to open and what the assistant may do.

The assistant can't see a command, or a tool takes fewer arguments than the docs say. Assistants keep a copy of a connector's tool list from when it was added. Remove the connector, add it again, and start a new chat.

A refusal you don't understand

A refusal is a rule doing its job: it names the reason and who can decide. Some acts are a person's only, whatever the assistant's role; approving a bill for payment is one. If a refusal looks wrong, send its exact words. If a rule let something through that it should have refused, say so first: that is the bug we care most about.

Your data

What is stored and for how long is on the privacy page. The rules of use are in the terms.

Saybooks for Mac and iPhone

Download, setup and what runs where are on the Mac and iPhone page. The apps keep your books on your own devices, so we can't see them to help: describe what you see, or send a screenshot with nothing private in it.

A security problem

Please report it by email to hello@saybooks.io rather than in a public GitHub issue, with enough detail to reproduce it. It will be looked at first and fixed before it is discussed in public.