Something broken?
Something missing?

One address reaches us, and a person reads it: hello@crate.tools.

There is no contact form here

A form would mean a server that receives what you type, and the whole point of Crate is that nothing you put into it is sent anywhere. Email keeps that promise intact: you decide what to send, from your own client, and you keep a copy of it.

What to send, and what helps

A tool produced the wrong result. Tell us which tool, which browser and version, and what you expected instead. Because processing happens on your device, we cannot see your file or look up what happened in a log — your description is genuinely all we have. A file that reproduces the problem helps enormously, but only send one you are comfortable sharing.

A tool is missing. Describe the task rather than the feature: what you were trying to get done, and what you did instead. That is how most of the tools here started.

You are building against the API or WebMCP. Read the developer portal first — it documents the catalog API, the OpenAPI description, and the limits — then write to us about whatever it failed to answer.

Privacy or security. Use the same address and say so in the subject line. If you believe you have found a vulnerability, please describe it privately first and give us a reasonable window to fix it before publishing. Our privacy page sets out what the site does and does not collect.

What to expect back

Replies are written by a person rather than generated, so they can take a few days. A broken tool is treated as urgent; a new-tool request goes onto a list that genuinely gets read. We do not send newsletters, we have no accounts to manage, and there is nothing to unsubscribe from — writing to us adds you to no list at all.

Anything you send is used to answer you and to fix the thing you reported. It is not sold, shared with advertisers, or used to train anything.