Datos Co vs Jitsu
A side-by-side look at the Datos Co and Jitsu 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 Jitsu for data platforms. 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 53/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,113 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Datos Co | View Jitsu |
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…
Jitsu tools
No tool names declared yet. Check the project README from 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"
]
}
}
}
Jitsu
No confirmed install command for Jitsu yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Datos Co is categorized under Data Platforms and uses a local stdio subprocess. Jitsu belongs to Data Platforms and uses an install path we have not confirmed yet. Pick Datos Co for data platforms work and Jitsu for data platforms.
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. Jitsu has no confirmed install command yet — follow its own setup instructions.
Datos Co has no declared pricing — check the project's own site. Jitsu 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 datos-co and jitsu 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. Jitsu has 41/100 (Fair) with 1 views, 0 installs and 5,113 GitHub stars.