Moxie Docs MCP vs Voice Bridge
A side-by-side look at the Moxie Docs MCP and Voice Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Moxie Docs MCP for knowledge & memory work as a local process; choose Voice Bridge for text-to-speech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Choose Voice Bridge when
- You need dedicated capabilities in the Text-to-Speech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VOICE_BRIDGE_HOME, ELEVENLABS_API_KEY, VOICE_BRIDGE_MODE, VOICE_BRIDGE_ENGINE, VOICE_BRIDGE_EDGE_VOICE, VOICE_BRIDGE_EDGE_RATE, VOICE_BRIDGE_ELEVENLABS_SPEED, VOICE_BRIDGE_KOKORO_VOICE. - You want tools like
speak, set_engine, get_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Text-to-Speech |
| Quality signal | 80/100 · Excellent | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | VOICE_BRIDGE_HOMEELEVENLABS_API_KEYVOICE_BRIDGE_MODEVOICE_BRIDGE_ENGINEVOICE_BRIDGE_EDGE_VOICEVOICE_BRIDGE_EDGE_RATEVOICE_BRIDGE_ELEVENLABS_SPEEDVOICE_BRIDGE_KOKORO_VOICE |
| Verified owner | Verified | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 36 views 25 installs 4 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 12 | 4 |
| Full listing | View Moxie Docs MCP | View Voice Bridge |
Tools & capabilities
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.
Voice Bridge tools 4
speakSpeak text aloud. Optionally override engine for this call.set_engineSwitch the default TTS engine (`auto`, `edge-tts`, `elevenlabs`, `kokoro`, `say`, `espeak`)get_statusShow current mode, engine, and available engineslist_voicesList available voices. Defaults to current engine if omitted.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
Voice Bridge
{
"mcpServers": {
"voice-bridge": {
"command": "npx",
"args": [
"-y",
"ai-voice-bridge"
],
"env": {
"VOICE_BRIDGE_HOME": "YOUR_VOICE_BRIDGE_HOME_HERE",
"ELEVENLABS_API_KEY": "YOUR_ELEVENLABS_API_KEY_HERE",
"VOICE_BRIDGE_MODE": "YOUR_VOICE_BRIDGE_MODE_HERE",
"VOICE_BRIDGE_ENGINE": "YOUR_VOICE_BRIDGE_ENGINE_HERE",
"VOICE_BRIDGE_EDGE_VOICE": "YOUR_VOICE_BRIDGE_EDGE_VOICE_HERE",
"VOICE_BRIDGE_EDGE_RATE": "YOUR_VOICE_BRIDGE_EDGE_RATE_HERE",
"VOICE_BRIDGE_ELEVENLABS_SPEED": "YOUR_VOICE_BRIDGE_ELEVENLABS_SPEED_HERE",
"VOICE_BRIDGE_KOKORO_VOICE": "YOUR_VOICE_BRIDGE_KOKORO_VOICE_HERE"
}
}
}
}
Frequently asked questions
Moxie Docs MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Voice Bridge belongs to Text-to-Speech and uses a local stdio subprocess. Pick Moxie Docs MCP for knowledge & memory work and Voice Bridge for text-to-speech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Voice Bridge has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add moxie-docs-mcp and voice-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Moxie Docs MCP has a quality signal of 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars. Voice Bridge has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.