Data Fortworth vs Git
A side-by-side look at the Data Fortworth 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 Data Fortworth 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 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.
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 | 57/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,540 |
| Directory activity | 2 views 0 installs 0 upvotes | 51 views 0 installs 0 upvotes |
| Tools | 3 | 16 |
| Full listing | View Data Fortworth | View Git |
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".
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.
Data Fortworth
{
"mcpServers": {
"data-fortworth": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-data-fortworth"
]
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Data Fortworth is categorized under Data Platforms and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Data Fortworth 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.
Data Fortworth 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 data-fortworth and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Data Fortworth has a quality signal of 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,540 GitHub stars.