Skip to main content
HyperWhisper ships with an in-app HTTP server you can opt into from Settings → Local API. When on, it listens on 127.0.0.1 only — never the LAN — and writes the bound port plus a bearer token to a discovery file on disk so MCP wrappers, benchmark scripts, and shell automation can find it without configuration.

Discovery file

chmod 600, JSON shape:

Authentication

Every endpoint except /health requires:
The token is generated on first server start (32 random bytes, base64-url-encoded) and stored in the macOS Keychain. You can regenerate it from Settings → Local API; the previous token is invalidated immediately.

Response envelope

Both shapes are returned with HTTP 200:
HTTP 4xx is reserved for protocol failures: 400 for malformed JSON, 401 for missing or invalid bearer token. Everything else (including “transcription engine errored”, “API key missing”, “file not found”) arrives as ok:false with a machine-readable code.

Endpoints

Full schema is in openapi.yaml.

Next: MCP

To plug HyperWhisper into Cursor, Claude Desktop, or Claude Code as a tool an agent can call, follow the MCP setup guide.