AI Agent Hub
Back to plugins
🧰

dsh-kokoro

Web Tools Updated 2026.09.01

Run the following command in DeepSeek Harness:

dsh plugin install jwilson411/dsh-kokoro

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install jwilson411/dsh-kokoro in your terminal to install this plugin; the full source repository is https://github.com/jwilson411/dsh-kokoro .

About this plugin

If you are already running a Kokoro TTS server locally and wish the DeepSeek Harness model could actually speak instead of only printing text, dsh-kokoro is the thin function plugin that closes that gap. It ships no model weights, needs no API key, and has zero runtime dependencies.

It registers a single model-facing tool, kokoro_tts, which accepts text, voice, and speed, POSTs once to the /tts endpoint of your local Kokoro server, writes the returned WAV into a plugin-owned subdirectory under the system temp folder (directory 0700, files 0600), and hands the path back to the caller. Nineteen allowlisted voices, a 0.5 to 2.0 speed range, a 30-second abort deadline, a 10 MiB response cap, and a RIFF/WAVE header check all happen on the plugin side so a bad argument fails locally without burning a network round trip. The output path is fixed by the plugin; the caller cannot choose it, preventing text-to-speech from becoming an arbitrary file-write primitive.

It suits engineers who are already serving kokoro-tts-api on 127.0.0.1, want Harness conversations to produce audio with one tool call, and prefer a minimal attack surface with a fully offline test suite. It is not an audio toolkit: no playback, no conversion, no mixing. It answers one question, what would this text sound like, and returns a file path.

Use Cases

  • Have the Harness model read its reply aloud as a WAV file within a conversation
  • Synthesize specified text with an allowlisted voice and return the saved file path
  • Generate speech inside an air-gapped network by hitting a local Kokoro server without any public API key

Best For

  • Developers who already run a kokoro-tts-api server locally
  • Security-conscious users who prefer zero runtime dependencies and a minimal attack surface
  • Engineers needing TTS in offline or intranet environments without external API dependencies