Datos Co vs Git
A side-by-side look at the Datos Co 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 Datos Co for data platforms work as a local process; 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 Datos Co when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_datasets, dataset_columns, query_dataset.
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 | Data Platforms | Version Control |
| Quality signal | 53/100 · Good | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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,547 |
| Directory activity | 1 views 0 installs 0 upvotes | 53 views 0 installs 0 upvotes |
| Tools | 3 | 16 |
| Full listing | View Datos Co | View Git |
Tools & capabilities
Datos Co tools 3
search_datasetsSearch datasets published on Colombia's open-data portal datos.gov.co. Returns each dataset's Socrata 4x4 id (e.g. "gt2j-8ykr"), name, and description (Spanish). Use the id with dataset_columns and query_dataset. Query terms can be Spanish or English (e.g. "covid", "presupuesto", "contratos").dataset_columnsList the columns of a datos.gov.co dataset: field name (used in SoQL $select/$where), human label, and data type. Call this before query_dataset so you know which fields exist. datasetId is the Socrata 4x4 code from search_datasets.query_datasetQuery rows from a datos.gov.co dataset using SoQL. datasetId is the Socrata 4x4 code from search_datasets. SoQL clauses: $select (columns / aggregates like "count(*)"), $where (SQL-like filter, e.g. "departamento_nom='BOGOTA' AND edad > 60"), $order ("count desc"), $group, $q (full-text across the…
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.
Datos Co
{
"mcpServers": {
"datos-co": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-datos-co"
]
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"mcp-server-git"
]
}
}
}
Frequently asked questions
Datos Co is categorized under Data Platforms and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Datos Co for 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.
Datos Co 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 datos-co and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Datos Co has a quality signal of 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 53 views, 0 installs and 91,547 GitHub stars.