VoxFabric
# 声络 VoxFabric
**Weave Every AI Voice**
MCP speech I/O for any agent host — local mic/speakers, Edge TTS speak, optional local ASR listen.
VoxFabric is a **stdio MCP server**: any MCP-capable host can call tools to speak and listen on the machine that runs this process. Speak uses **Edge TTS** (network to Microsoft/Bing). Listen is optional and can use **local ASR** (e.g. Whisper) with models you place yourself. There is **no web UI** — MCP only. The project is **source-available**; personal/non-commercial evaluation is fine, but **commercial use and 二开 require paid written authorization** (see [LICENSE](LICENSE)).
---
## Tools
| Tool | Role |
|---|---|
| `speak` | TTS playback (Edge) |
| `listen` | Mic → text |
| `listen_start` / `get_speech` / `listen_stop` | Persistent listen |
| `set_engine` / `catalog` / `health` | Engines & health |
Optional engines include local Whisper / SenseVoice / Aliyun ASR, energy or Silero VAD, and Edge TTS.
---
## Install & connect
All prerequisites, Windows / Kali steps, MCP JSON, proxy, and troubleshooting: **[DEPLOY.md](DEPLOY.md)**.
---
## License
**Source-available** — not OSI “Open Source” with free commercial rights.
- Personal / non-commercial evaluation: OK.
- Commercial use, SaaS, redistribution, or commercial 二开: **paid written authorization** required.
- Full terms: **[LICENSE](LICENSE)**.
TDQS
Scored across 8 tools
Each tool targets a distinct function: speak for TTS, listen for one-shot STT, listen_start/get_speech/listen_stop for streaming sessions, set_engine/catalog for configuration, and health for status. No two tools have overlapping responsibilities.
Most names follow an imperative verb style with snake_case for compound actions (listen_start, get_speech). A few single-word names like catalog and health deviate from a strict verb_noun pattern, but the overall style is consistent and readable.
8 tools is well within the ideal range. Each tool serves a clear purpose in the voice lifecycle (speech, recognition, session control, engine management, health) without redundancy.
The core voice workflows are covered: one-shot and continuous recognition, TTS, engine switching, and status. Minor gaps exist such as no explicit pause/resume or volume control for speech, but these can be worked around using engine settings.