# Toolako developer documentation

Toolako publishes a public catalog for six ready browser image tools: compress, resize, crop, rotate and flip, convert, and watermark.

## Discovery and schemas

- [Machine-readable catalog](/tools.json): localized entries include strict input, options, and result JSON Schemas, formats, limits, and links.
- [English setup guide](/setup.md): local MCP companion installation and host configuration.
- Localized developer pages: [/en/developers/](/en/developers/), [/ar/developers/](/ar/developers/), [/pt/developers/](/pt/developers/).

Every catalog entry declares executionLocation: user-browser, remoteExecution: false, and requiresLocalBrowser: true. Hosted discovery is metadata-only. It does not accept image bytes, Base64, local paths, or image URLs, and it does not execute image operations remotely.

## Execution

Human users select files in the browser workbench. Browser agents can act only when their environment is authorized to access that active workbench tab and the user-selected assets. The local MCP companion uses stdio to launch a fresh local browser and the same image engine. A cloud-only MCP host cannot access private files on the user’s device.

## Limits

Ordinary single-tool calls accept one static JPEG, PNG, or WebP source image. Each source is limited to 20 MiB, 16 megapixels, and 8,192 pixels per side; an optional watermark logo is subject to the same limits. The separate local MCP batch tools import up to 50 source images per call, up to 20 MiB each and 100 MiB aggregate input including an optional shared logo. Retained batch outputs are limited to 100 MiB aggregate. Output limits are 16 megapixels, 8,192 pixels per side, and 100 MiB per image. Animated images, SVG, HEIC, and AVIF are not supported.

## Privacy

Image pixels are processed in the browser and are not uploaded to the hosted catalog. With an AI provider, selected filenames or paths, tool arguments, and returned metadata may be visible to that provider. Image bytes and pixels are not included in results by default. Local MCP file access is restricted to input and output roots configured by the user.