Vox vs Git
A side-by-side look at the Vox and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vox for text-to-speech work; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Vox when
- You need dedicated capabilities in the Text-to-Speech domain.
- You have the keys it needs:
ELEVENLABS_API_KEY. - You want tools like
listen, speak.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Text-to-Speech | Version Control |
| Quality signal | 40/100 · Fair | 81/100 · Excellent |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | ELEVENLABS_API_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 1 | 91,547 |
| Directory activity | 1 views 0 installs 0 upvotes | 52 views 0 installs 0 upvotes |
| Tools | 2 | 16 |
| Full listing | View Vox | View Git |
Tools & capabilities
Vox tools 2
listenActivates the mic, waits for you to speak, returns transcript + detected language when silence is detectedspeakSpeaks text aloud — ElevenLabs TTS with automatic fallback to macOS system voice
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
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.
Vox
No confirmed install command for Vox yet — follow the setup steps linked from its listing page rather than a guessed package name.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"mcp-server-git"
]
}
}
}
Frequently asked questions
Vox is categorized under Text-to-Speech and uses an install path we have not confirmed yet. Git belongs to Version Control and uses a local stdio subprocess. Pick Vox for text-to-speech work and Git for version control.
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. Vox has no confirmed install command yet — follow its own setup instructions.
Vox has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. 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 vox and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vox has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Git has 81/100 (Excellent) with 52 views, 0 installs and 91,547 GitHub stars.