Next Devtools MCP vs Voice Bridge
A side-by-side look at the Next Devtools 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 Next Devtools MCP for developer tools 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 Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
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 | Developer Tools | Text-to-Speech |
| Quality signal | 86/100 · Excellent | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | 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 | 832 | 0 |
| Directory activity | 9 views 0 installs 1 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 4 | 4 |
| Full listing | View Next Devtools MCP | View Voice Bridge |
Tools & capabilities
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
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.
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
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
Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. Voice Bridge belongs to Text-to-Speech and uses a local stdio subprocess. Pick Next Devtools MCP for developer tools 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.
Next Devtools MCP is listed as free. Auth: no auth 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 vercel-next-devtools-mcp and voice-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Next Devtools MCP has a quality signal of 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars. Voice Bridge has 49/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.