Side-by-Side Model Context Protocol Comparison
Data Fortworth vs Data Mesa
In-depth architectural comparison of the Data Fortworth and Data Mesa MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Data Fortworth
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Data Mesa
Developer Tools · Remote HTTP/SSE
Quality: 33/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Data Fortworth if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Data Mesa if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
D
Choose Data Fortworth when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: datasets, query, metadata.
Choose Data Mesa when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
Feature & Specification Comparison
Tools & Capabilities Breakdown
Data Fortworth Tools (3)
datasets
Search 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.
query
Run 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.
metadata
Get a Fort Worth Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "eax3-qev8".
Data Mesa Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Data Fortworth Configuration
Data Mesa Configuration