CLI and MCP

The same local service, with a different door.

Command line

local-transcribe is a client of the shared service. Every command prints JSON, and the service is started on demand if it is not running.

Check the service and list models

local-transcribe status
local-transcribe models list

Submit a job to run locally

local-transcribe jobs add ./interview.m4a --root ~/recordings

Pin a LAN node and never fall back

local-transcribe jobs add ./interview.m4a --node Gaming-PC --lan-model <model id>

List jobs and export

local-transcribe jobs list
local-transcribe export <job id> --format txt --output ./transcript.txt

voice-to-text-mcp speaks MCP over local stdio and is another client of the shared service. No model is ever loaded inside the MCP process.

Submit a transcription and get a job id back immediately, then poll status and result.
List jobs and models, cancel, retry, and export results as TXT or JSON.
File access is fail-closed: inputs and export destinations must live under explicitly allowed roots, and a request without roots is denied.
No network listener, no unrestricted filesystem access, no shell execution.

The tool list changes between versions. docs/mcp.md in the repository is the authority.

The GUI, the CLI and the MCP server all connect to the same service instance backed by the same files. A job started in one is visible in the others.