# Limits, credits and privacy

> The MCP follows your plan exactly as the app does. Here is what it costs, how far it goes, and what data goes where.

Web page: https://brollss.com/mcp/limits. All MCP pages: https://brollss.com/llms.txt (index) and https://brollss.com/mcp/llms-full.txt (everything in one file).

## Who can use it

Every Brollss account the app lets work, free plan and trials included. A paused account is refused until it is settled in the app.

## Plan limits

The number of projects of your plan and the largest file you can import are the app's, enforced by the same code, with the same message. A gesture the Studio refuses is refused here with the reason. Your agent should tell you and stop, not try another way.

## Credits

Three tools spend Brollss credits, the same credits as the app and at its prices: `generate_image` (50 credits per image), the transcription of `import_media` (10 credits per started 2 minutes of media) and `export_video` (10 credits per started minute of the edited video). They stop the same way as the app when the credits run out. Cutting, measuring scenes, rendering frames and checking the edit are free; those check renders have a daily allowance per account, which `whoami` shows. Your agent's own model usage is billed by its provider.

## Server limits

- Renders (`look_at_montage`, `measure_scene`, `insert_scene`, `add_marker`, the measure of `check_edit`) run one at a time per account. A call waits up to 90 seconds for its turn, then is refused with a message to try again.
- `measure_scene` accepts 12 measures per scene per hour. A scene needs two or three.
- A scene page weighs at most 3 MB with images, 600 KB without.
- On the hosted server, one `wait_for_job` call waits 120 seconds by default and 300 at most. Call it again until the job is done.
- One media file per project.
- A `path` on the machine works only with a Brollss server running locally. The hosted server takes a file upload or a direct link.

## Privacy

- Brollss transcribes the voice of an imported video to build its transcript.
- The thinking happens in the agent you connect. Besides the transcription, the only Brollss model an MCP tool calls is the image generator of `generate_image`, and only when your agent asks for an image.
- Your agent receives what its tools return: project state, transcript text, frames of the video, scene pages and measures. Its provider handles that data under its own terms. Read them before you connect a client that may train on your conversations.
- The agent reaches only the projects your account can open, with the same role: read-only access stays read-only.

The full policy is on the [privacy page](https://brollss.com/legal/privacy).