The best API isn't in the cloud.
We do have an API — our CLI and our MCP server are the API. The difference: they run inside your shell and your agent, not on our servers. Your bytes never move, the network never wakes up, the bill never arrives.
Why a local API wins
Physics beats policy
Others promise your data is safe with a privacy policy. We guarantee it with physics — the bytes never leave your device. You can't leak what you never see.
Zero inference bill
Stop paying AWS tax on every image. The strongest server on earth is the one your user already turned on. We just put it to work.
Faster than the speed of light
The encoder was never slow — the network was. We deleted the network. What's left runs at the speed of RAM. That's the ceiling physics gives you.
CLI — a local API for your shell and your CI
@getwebp/cli v1.0 is live. One curl installs it on your build box, your laptop, your GitHub Actions runner. No API keys, no rate limits, no outbound requests.
- Single-file binary — native macOS, Linux, and Windows
- Drops into any CI/CD — batch conversion without asking for permission
- Same WASM engine as the extension — byte-for-byte identical output
MCP — a local image API for your AI agent
Plug GetWebP into Claude, Cursor, or any MCP-aware agent. Your agent can scan folders, inspect images, and batch-convert formats — all on your machine. Not a single byte ships to a model vendor.
- Agent-native — scan, convert, and status tools work out of the box
- stdio transport — zero network dependency, every MCP client supported
- Same engine as the CLI — what the agent ships is what you'd ship by hand
Paste into your claude_desktop_config.json, restart Claude, and your agent has a local image toolkit.
{
"mcpServers": {
"getwebp": {
"command": "npx",
"args": ["-y", "@getwebp/mcp-server"]
}
}
}