inworld (the CLI) and inworld-mcp (the standalone MCP server, equivalent to inworld mcp).
Authentication
Workspaces and API keys
Text-to-Speech
synthesize supports audio markups directly in the text: emotions ([happy], [sad]), delivery styles ([whispering]), vocalizations ([laugh], [sigh]), SSML breaks, and IPA pronunciation.
Audiobooks
Turn a whole book into a single MP3 with chapter markers:.txt, the spine in .epub) and synthesized in parallel, each on its own TTS session so voice delivery stays consistent within a chapter. Long runs are resumable: pass --work-dir <dir> and a re-run skips chapters that already finished.
Speech-to-Text
LLM Router
MCP server
The CLI ships with the full Inworld MCP server — your AI assistant gets real operational tools, not just documentation search: TTS previews, voice design and publishing, STT transcription, LLM chat, workspace search and limits, billing summary, and router + BYOK credential management.Many agents don’t need the MCP server at all — they can call
inworld commands directly from the shell.Telemetry
The CLI collects anonymous usage analytics. To opt out:Inworld CLI vs. Runtime CLI
The Inworld CLI (inworld) covers platform APIs: auth, API keys, TTS, STT, and LLM Router. For Agent Runtime graph development and deployment (inworld-runtime init/run/deploy), see the Runtime CLI.