
Koe TTS Studio
space.kennedyazeruPublished by kennedyazeru.spaceOfficial publisherv1.3.0Updated Nov 21, 2026
Free text-to-speech for any MCP client: one hosted endpoint, four engines, no API bill.
Overview
Hosted text-to-speech MCP endpoint that lets an assistant generate voiceovers from text using four TTS engines and return audio or a download link.
- What you can do
- Check studio health, engines, queue, limits and your own usage
- List available voices per engine (edge, piper, kokoro, kitten) with an optional language filter
- Generate a voiceover from text, then poll the job and return a signed download URL plus inline audio for short clips
- Look up the status of a voiceover job by id
- List your last ten voiceover jobs
- Check requests and words used this hour and today against limits
- When to use it
- Useful when an agent needs spoken audio, narration or voiceovers without paying for a commercial TTS API, and when a hosted, install-free endpoint is preferred over running a local studio.
- Requirements
- A remote streamable-HTTP endpoint; no local install or Node.js needed. A free key is required, sent as an Authorization bearer header; the key is created on the setup page, which solves a proof-of-work challenge. Network access to the hosted service.
Installation
In SourceWeft
- Open Koe TTS Studio in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/space.kennedyazeru%2Fkoe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"koe-tts-studio": {
"type": "http",
"url": "https://koe.kennedyazeru.space/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
Koe TTS Studio + MCP
A self-hosted text-to-speech studio (Microsoft neural voices via edge-tts, optional offline Piper, Kokoro and Kitten) and an MCP server so agents can generate voiceovers on demand — free, no ElevenLabs.
It is built to be a free public product:
- Multi-tenant — every MCP install and every browser gets its own free key (issued server-side) with independent hourly/daily quotas.
- Rate-limited — per-key and per-IP limits, a bounded global queue, a global daily word budget, and a circuit breaker for upstream (Microsoft) failures.
- Ephemeral audio — generated zips are deleted after 15 minutes; job metadata after 1 hour; a restart wipes all audio. Nothing depends on permanent storage.
- One small SQLite file — issued keys and every counter live in
KOE_DB_PATH(./koe.dbby default), so limits survive restarts and a key is revocable by deleting its row. Keys are persisted as SHA-256 hashes, never plaintext, so a dumped database cannot be replayed as live keys.KOE_SECRETstill signs download links and hashed subjects.
Use it from any agent (hosted MCP)
The public instance runs at https://koe.kennedyazeru.space. The hosted MCP server is at https://koe.kennedyazeru.space/mcp. Agents connect by URL — no install, no local Node, no config file. The same URL serves a human setup page in a browser.
- Open https://koe.kennedyazeru.space/mcp and click Create key (the page solves the proof-of-work challenge for you).
- Point your client at
https://koe.kennedyazeru.space/mcpwithAuthorization: Bearer <key>(orx-api-key: <key>). - Ask the agent to call
studio_status, thengenerate_voiceover.
Works with Claude custom connectors (static request header, currently beta), Claude Code (--transport http), Cursor, or any streamable-HTTP MCP client. The endpoint is stateless and returns JSON (no SSE required), which keeps it compatible with a reverse proxy and ephemeral container disk.
Because the audio lives on the server rather than the caller's disk, hosted generate_voiceover returns a short-lived signed download URL (/audio/:id?dl=…, no API key needed) plus inline audio for short clips. The local stdio server below is still available for developers and saves files directly.
Building an agent? AGENTS.md is the full agent-facing reference: exact MCP tool schemas, response shapes, recipes, error handling and the raw HTTP API. DESIGN.md records the visual system and the analytics measurement language.
Free tier
Global safety rail: 6 concurrent jobs, a 20-job queue, and 30,000 words/day across the whole instance.
Scaling out
Synthesis is a queue, and the queue lives in SQLite, so capacity is a matter of running more workers — not of running a bigger server process:
- The global concurrency limit (
KOE_GLOBAL_CONCURRENCY) is enforced inside the claim transaction, so every process shares one budget. Two processes cannot both admit job number seven. - Jobs are claimed atomically (
queued→starting), so no job runs twice, and a worker that dies mid-job is reaped and refunded after the job deadline. - Workers share the database file, so they must be on the same host or volume.
The audio directory must be shared too, since
GET /download/:idmay be served by a process that did not synthesise the job. - Parts of one job synthesise in parallel (
KOE_PART_CONCURRENCY, default 2), and identical(text, voice, rate, pitch, engine)requests are served fromoutput/cache/instead of a fresh upstream call. That cache has a byte budget (KOE_CACHE_MAX_MB, default 256 MB) and is pruned oldest-first on every write, and again on every periodic sweep, so lowering the limit or inheriting files from an older run still converges on the budget. - A job's script is not stored in the database:
POST /ttswrites it tooutput/work/<jobId>.parts.jsonand the worker reads it from there. The row keeps counts and status only. If a worker is killed mid-job, the next boot re-queues the job from that file (with a fresh deadline) instead of failing it; only jobs whose script is missing are failed and refunded. The file is deleted on every terminal outcome — success, failure, deadline overrun, a reaped worker, orDELETE /job/:id— so only jobs that are still waiting or running hold one.
Measured on the reference box (108-word jobs, edge engine): 2 workers ≈ 6 jobs/min,
6 workers ≈ 10–15 jobs/min. The upstream endpoint, not the CPU, is the ceiling —
raise KOE_GLOBAL_CONCURRENCY carefully and watch for 403/429s. One job may be at most 2,000 words / 40,000 characters — and 900 words on kitten, which cannot finish more than that inside the 300 s job deadline, so a longer kitten script is a 400 before anything is charged. Free keys are capped at 3 per IP per day. Previews are metered too and limited to 600 characters.
All of these are environment variables (see below).
How keys work
Keys are issued server-side: POST /keys writes an opaque koe_sk_<32 hex> record into SQLite, and every request validates against that table. Nothing client-side can be counted.
POST /api/registeris a thin alias ofPOST /keys— same gate, same201 {key}body, so older callers keep working instead of getting a 404.- Challenges are single-use and expire after 5 minutes; a wrong or replayed one is
403 pow_challenge_invalid/pow_failed. - With
TURNSTILE_SITEKEY+TURNSTILE_SECRETset, the gate becomes Cloudflare Turnstile instead of proof-of-work (headless clients then needTTS_API_KEY). - Keys are rows, so they are revocable: delete the row (or wipe
KOE_DB_PATH) and the key stops working on the next request. The studio UI and the MCP client re-mint automatically when a stored key starts returning401— see MIGRATION-v3-keys.md. - Rows hold
sha256(key), never the key itself. A database from a build that stored raw keys is upgraded on open: each plaintext row is rewritten as its digest in place, so existing keys keep working and no plaintext secret is left on disk. KOE_REQUIRE_KEY=truerejects anonymous calls. The bundled MCP server and studio UI register a key automatically, so end users never see this step.API_KEYis an operator/admin key. It bypasses all limits and can see every tenant's jobs. Keep it private.
Kill switch
KOE_KILL_SWITCH=true answers 503 {"error":"temporarily_disabled"} on POST /tts, POST /tts-preview* and POST /mcp before auth, quota, queueing or any upstream work. Flip it in the environment and restart to stop all generation instantly; everything else (health, key issuance, usage, dashboards) keeps answering.
Ephemeral audio
- Audio zips live in
output/audio/and are deleted afterKOE_AUDIO_TTL_SEC(default 900 s). - Job metadata lives in the SQLite
jobstable (KOE_DB_PATH) and is pruned afterKOE_JOB_TTL_SEC(default 1 hour). A legacyoutput/jobs.jsonis imported once on boot and then ignored. - Previews are written to
output/previews/and swept afterKOE_PREVIEW_TTL_SEC(default 10 min). - On boot all audio/preview/work files are deleted; jobs that were mid-flight are marked failed.
GET /download/:idreturns410once audio expires. - Script text is never stored on disk — only counts, voice, engine, status and timings.
TTS Studio server (server.js)
Local usage: npm install && node server.js → http://localhost:3000. / redirects to the MCP setup page at /mcp; the studio UI is served at /studio. It talks to the same origin (or http://localhost:3000 when opened as a file).
Endpoints
Auth accepts x-api-key: <key>, Authorization: Bearer <key>, or ?key=<key>. POST /mcp always needs a live key row (or the admin key). Status codes: 400 validation or a job over KOE_MAX_JOB_WORDS, 401 {"error":"invalid_key"} missing/unknown key, 403 another tenant's job or a failed issuance gate, 404 unknown, 409 not ready, 410 audio expired, 413 script over the 40,000-char cap, 429 {"reason":…} rate/queue/global limit, 503 {"error":"temporarily_disabled"} kill switch, engine unavailable or upstream cool-down.
Rejections carry a reason (hourly_requests, hourly_words, daily_words, global_daily_words, job_too_long, kill_switch, queue_full, invalid_key, mint_cap) and, for limits, a retryAfterSeconds reset window.
Two backends
TTS_BACKEND=native— runs theedge-tts/piperCLIs directly (the production Docker image). Default when Docker is unavailable.TTS_BACKEND=docker— shells out to theedge-tts/piper-ttsDocker images (local dev). Auto-selected when thedockerCLI exists.
Docker invocations use execFile (no shell), so script text and voice ids are never interpreted as shell commands.
Three engines
All three sit behind one registry (engines/index.js) and one interface — synthesize() -> { bytes, contentType }, listVoices(), healthy().
edge is the default and behaves exactly as it always has; KOE_DEFAULT_ENGINE can override the default but is intentionally left unset.
The Kokoro sidecar is optional. Start it with:
The app works fine without it — edge and piper are untouched, and only engine: "kokoro" requests are rejected with 503 {"error":"tts_unavailable","engine":"kokoro"} (returned within 10s, before any quota is charged). GET /healthz stays 200 either way and reports engines.kokoro: false while it is down.
Point the studio at a sidecar on another host with KOKORO_BASE_URL (default http://127.0.0.1:8880).
Note the sidecar ignores pitch entirely, and rates below 1.0 are clamped up to 1.0 (it accepts speed only in 1.0–2.0) — a warning is logged once if either happens.
Kitten sidecar (tiny, WAV)
Kitten TTS is the cheap local engine: the int8 nano checkpoint is ~25 MB, the measured sidecar RSS after a synthesis is ~155 MB, and the image is ~300 MB — so it runs comfortably where Kokoro does not. It is roughly 6× faster than realtime for short text (measured: 18 words → 8.8 s of audio in 1.4 s).
Same rules as Kokoro: the app works without it, and only engine: "kitten"
requests answer 503 {"error":"tts_unavailable","engine":"kitten"} while it is
down (before any quota is charged). GET /healthz reports engines.kitten.
- Base URL:
KITTEN_BASE_URL(defaulthttp://127.0.0.1:8881). - Output is WAV, so jobs zip and merge exactly like piper's.
rateis passed to the sidecar asspeedand clamped to 0.5–2.0; pitch is ignored (warned once).- One synthesis at a time inside the container, which is what keeps it inside its memory limit.
- The image installs
kittenmlwithout its torch/CUDA tree: the int8 ONNX path never imports torch (verified), so the stock dependency set is 6.5 GB for nothing. Seeops/kitten/Dockerfile.
Kitten voices — the eight speakers every checkpoint ships. The sidecar is
authoritative (GET /voices); this is the fallback list:
bella jasper luna bruno rosie hugo kiki leo
Ids are lowercase and never shared with edge, piper or Kokoro — passing a Kokoro
id to engine: "kitten" is a 400 with the valid ids in the body.
Kokoro voices
Kokoro voice ids are not shared with edge/piper: passing an edge voice to engine: "kokoro" is a 400 listing the first 20 valid kokoro ids (and the reverse). The live list comes from the sidecar (GET /v1/audio/voices); if it is unreachable the built-in catalog below is served instead.
- en-US (20):
af_heartaf_alloyaf_aoedeaf_bellaaf_jessicaaf_koreaf_nicoleaf_novaaf_riveraf_sarahaf_skyam_adamam_echoam_ericam_fenriram_liamam_michaelam_onyxam_puckam_santa - en-GB (8):
bf_alicebf_emmabf_isabellabf_lilybm_danielbm_fablebm_georgebm_lewis - ja-JP (5):
jf_alphajf_gongitsunejf_nezumijf_tebukurojm_kumo - zh-CN (8):
zf_xiaobeizf_xiaonizf_xiaoxiaozf_xiaoyizm_yunjianzm_yunxizm_yunxiazm_yunyang - es-ES (3):
ef_doraem_alexem_santa - fr-FR (1):
ff_siwis - hi-IN (4):
hf_alphahf_betahm_omegahm_psi - it-IT (2):
if_saraim_nicola - pt-BR (3):
pf_dorapm_alexpm_santa
The id prefix is locale + gender (a=American, b=British, f/m=female/male), so bm_george is a British male voice.
Deploy on AWS (EC2 + Docker + Caddy)
Production is a single EC2 instance running the koe container behind Caddy, with a Let's Encrypt certificate and two systemd timers (watchdog and disk guard). The complete runbook is in DEPLOY.md; the reusable scripts and unit files are in ops/. Pushes to main can also deploy automatically once CI passes, and a deploy can be started by hand from the Actions tab — both go through Systems Manager, so the instance needs no open SSH port and GitHub stores no AWS key. The opt-in setup (OIDC role, instance profile, repository variables) is in DEPLOY.md §6.
Short version
rebuild.sh clones/pulls the repo, builds the image, recreates koe on 127.0.0.1:8080, and starts Caddy. KOE_SECRET must stay stable — it signs download links and every hashed subject id. API_KEY is the operator key used by /stats, /stats.json, and the analytics dashboard.
The Docker image installs Node 20 + edge-tts and best-effort Piper. It keeps runtime data (state.json, stats.json, and koe.db — which now also holds the job queue) on a mounted volume so a container recreate does not wipe issued keys, usage counters or job metadata — set KOE_DB_PATH=/data/koe.db alongside KOE_STATE_FILE/KOE_JOBS_FILE/KOE_STATS_FILE.
The container runs as the unprivileged node user (uid 1000). rebuild.sh hands the data directory to that uid before starting. If you launch the image by hand with a bind mount, make it writable first (sudo chown -R 1000:1000 ./data), or the app cannot open its database.
Back up /data/koe.db. It holds every issued key, mint cap and counter; audio and jobs are disposable. ops/backup.sh takes a verified, retention-limited snapshot with SQLite's online backup API — see DEPLOY.md §8.
render.yamlremains in the repo as a legacy blueprint. It is not the production target.
MCP server
Hosted (recommended)
Already running at POST /mcp on your deployment — see Use it from any agent above. There is nothing to install and no environment variables to set; the caller's free key scopes every tool call. GET /mcp is the human setup page.
Local stdio (mcp/)
Runs the same tools as a local process. It talks to a studio (local or hosted) and saves generated audio to a local file path, which is handy for video pipelines.
Register it
Claude Desktop (claude_desktop_config.json):
Claude Code:
No key is required in the config. On first use the MCP asks GET /keys/challenge, answers the proof-of-work, mints the key with POST /keys, saves it in ~/.koe/credentials.json (keyed by studio URL), and reuses it. Each user/install therefore gets an independent quota. If the studio starts answering 401 (for example after an upgrade that invalidates old keys), the client clears the stored key and mints a fresh one automatically. Set TTS_API_KEY only if you want to force a specific key (for example the operator's admin key).
Tools
MCP environment variables
Smoke-test the wiring without an agent:
Server environment variables
Operator analytics
/stats.html is a public shell; its numbers come from the admin-only /stats.json. Open the page, paste API_KEY, and it reads:
- Traffic — all HTTP hits, voiceover jobs, MCP calls, previews, downloads, and new keys, all-time and today.
- Product users — unique subjects with a real product action (voiceover, MCP call, preview, download, or registration) in the last 5 minutes / hour / 24 hours.
- Visitors — all unique subjects, including crawlers and page loads. The dashboard shows these separately so bot traffic cannot inflate the user count.
- Request sources — top subjects by HTTP requests; Voiceover users — top subjects by words generated.
- Daily ledger — 14 days of counters.
Counters persist to KOE_STATS_FILE (default .koe-stats.json; /data/stats.json in the production container). Anonymous visitor ids are keyed HMACs from guard.anonSubject(), never raw IPs. Older raw-IP records are migrated on load. Job and audio data remain ephemeral.
Notes
- edge-tts is free but unofficial (Microsoft's consumer endpoint); occasional throttling is expected. The circuit breaker pauses new work briefly instead of hammering it.
- Very long scripts are split into ~3000-char parts by the studio; the MCP merges them back into a single file (MP3s concatenated, WAVs re-muxed properly).
- Tests:
npm test(115 tests: guard limits, key auth and hashing, tenant isolation, validation, ephemeral cleanup, analytics privacy/accounting, engine adapters, Kokoro sidecar behaviour, hosted MCP handshake and signed audio links). CI runs them on push and on the Docker build.
Agent skill
skills/koe-voiceover/SKILL.md packages this
server as a portable SKILL.md: when to reach for a voiceover, how to get a free
key, the tool table, script-formatting rules and the error table. Zip the folder
to publish it to a skill marketplace.
Support
Koe is free and has no accounts, cards or paid APIs. Running it costs one small box and a domain, paid by one person. If it has been useful, you can buy me a malt — naira checkout, which Buy Me a Coffee can't do for a Nigerian account.
Licence
Koe is free software under the GNU Affero General Public License v3.0 (AGPL-3.0). © 2026 Azeru548. See LICENSE for the full text.
You can use it, change it and run it — for your own videos, inside your company, or as part of a paid product. Two obligations are what make that safe for everyone:
- Share changes when you host it. If you modify Koe and let other people use that modified version over a network — a public instance, a SaaS, an internal portal that other teams reach over HTTP — you must offer those users the complete corresponding source of your version, under the AGPL (§13). Running it privately for yourself or your own business requires no disclosure.
- Keep the notices. Don't strip the copyright or the license, and mark a fork as changed (AGPL §5) — "based on Koe" is the fair way to say it.
There is no warranty and no support contract. If the public instance is down or rate-limited, the license is what lets you run your own.
What the license does not cover
The AGPL covers this source code. It grants nothing for the Koe name, the
logo, or the domain koe.kennedyazeru.space, and it does not permit presenting
a fork as the official project or implying endorsement by it. If you run a
public instance of your own, give it its own name — "based on Koe" is welcome,
"Koe" as your brand is not. The hosted instance itself (its keys, its quota, its
uptime) is not part of what this repository licenses.
Contributing
Issues and pull requests are welcome. For anything larger than a bug fix, open an issue first so the scope is agreed before you write code. Contributions are accepted under the project's AGPL-3.0 license — no CLA and no copyright assignment. Please keep keys, secrets and other people's audio out of issues and pull requests.
Source: README.md at commit ad51f00
Tools
0Version history
1- v1.3.0LatestNov 21, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts