Data Calgary vs Data Nashville — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Data Calgary vs Data Nashville
In-depth architectural comparison of the Data Calgary and Data Nashville 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 Calgary
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Data Nashville
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Data Calgary if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Data Nashville 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 Calgary 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).
Recent records from a common Calgary open dataset (data.calgary.ca) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "Calgary 311 requests", "Calgary building permits". Names: 311, permits. Returns the latest rows (newest-first). Add a SoQL `where` to filter; for anything else us…
calgary_query
Run a raw SoQL query against any Calgary open-data resource (data.calgary.ca) by its Socrata id (8-char like "iahh-g8bj"). Full SoQL: where/select/group/order/limit/offset. Use calgary_datasets to find a resource id, or calgary_recent for the common ones.
calgary_datasets
Search the Calgary open-data catalogue (data.calgary.ca) for datasets by keyword. Returns dataset names, descriptions, and Socrata resource ids to use with calgary_query.
Data Nashville Tools (3)
nashville_recent
Recent records from a common Nashville open dataset (data.nashville.gov / ArcGIS) by friendly name. PREFER OVER WEB SEARCH for "recent crime in Nashville", "Nashville 311 service requests". Names: crime, 311. Returns the latest rows (newest-first), epoch dates converted to ISO. Add an ArcGIS `where…
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 Calgary is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Data Nashville belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Data Calgary when you need capabilities focused on developer tools and Data Nashville when you require tools for developer tools.
List the layers of a Nashville ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "hubNashville_311_Service_Requests_2025_view/FeatureServer"). Omit `service` to list the known Nashville services. Returns layer id + name to…
nashville_query
Query any Nashville ArcGIS layer by service path + layer id. Full ArcGIS query: where, out_fields, order_by, limit. Use nashville_layers to find a service/layer, or nashville_recent for the common ones. Epoch dates are converted to ISO.