Anchorr MCP vs Git
A side-by-side look at the Anchorr 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 Anchorr MCP for customer data platforms work over a hosted endpoint; 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 Anchorr MCP when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
enrich_contact, enrich_company, bulk_enrich_contacts.
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 | Customer Data Platforms | Version Control |
| Quality signal | 47/100 · Fair | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 1 | 91,540 |
| Directory activity | 1 views 0 installs 0 upvotes | 51 views 0 installs 0 upvotes |
| Tools | 3 | 16 |
| Full listing | View Anchorr MCP | View Git |
Tools & capabilities
Anchorr MCP tools 3
enrich_contactsingle contact via email or `(first_name, last_name, domain)`enrich_companysingle company via domain or namebulk_enrich_contactsup to 200 contact IDs in one call, concurrency-capped, returns aggregate stats and per-contact outcomes
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.
Anchorr MCP
{
"mcpServers": {
"anchorr-mcp": {
"url": "https://anchorr-mcp.mgthompo.workers.dev/mcp"
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Anchorr MCP is categorized under Customer Data Platforms and uses a remote HTTP/SSE transport. Git belongs to Version Control and uses a local stdio subprocess. Pick Anchorr MCP for customer data platforms 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.
Anchorr 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 anchorr-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Anchorr MCP has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,540 GitHub stars.