Data Fortworth vs Jitsu
A side-by-side look at the Data Fortworth 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 Data Fortworth 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 Data Fortworth when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
datasets, query, metadata.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 57/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 | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Data Fortworth | View Jitsu |
Tools & capabilities
Data Fortworth tools 3
datasetsSearch the Fort Worth Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.queryRun a Socrata SoQL query against a Fort Worth Open Data dataset by resource_id (e.g. "eax3-qev8"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.metadataGet a Fort Worth Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "eax3-qev8".
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.
Data Fortworth
{
"mcpServers": {
"data-fortworth": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-data-fortworth"
]
}
}
}
Jitsu
No confirmed install command for Jitsu yet — follow the setup steps linked from its listing page rather than a guessed package name.