EarScribe MCP vs Git
A side-by-side look at the EarScribe MCP 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 EarScribe MCP for speech-to-text 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 EarScribe MCP when
- You need dedicated capabilities in the Speech-to-Text domain.
- You want tools like
get_local_setup, get_official_links.
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 | Speech-to-Text | Version Control |
| Quality signal | 41/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 | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,540 |
| Directory activity | 0 views 0 installs 0 upvotes | 51 views 0 installs 0 upvotes |
| Tools | 2 | 16 |
| Full listing | View EarScribe MCP | View Git |
Tools & capabilities
EarScribe MCP tools 2
get_local_setupReturn canonical local-setup guidance for running the AI workflow on-device. (EarScribe)get_official_linksReturn the canonical list of official links for EarScribe (website, support, docs when available).
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.
EarScribe MCP
No confirmed install command for EarScribe MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
EarScribe MCP is categorized under Speech-to-Text and uses an install path we have not confirmed yet. Git belongs to Version Control and uses a local stdio subprocess. Pick EarScribe MCP for speech-to-text 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. EarScribe MCP has no confirmed install command yet — follow its own setup instructions.
EarScribe MCP 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 earscribe-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, EarScribe MCP has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,540 GitHub stars.