Data Nashville vs Data Montreal — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Data Nashville vs Data Montreal
In-depth architectural comparison of the Data Nashville and Data Montreal 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 Nashville
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Data Montreal
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Data Nashville if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Data Montreal 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 Nashville 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 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…
nashville_layers
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.
Data Montreal Tools (3)
montreal_recent
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 Nashville is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Data Montreal belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Data Nashville when you need capabilities focused on developer tools and Data Montreal when you require tools for developer tools.
Recent records from a common City of Montreal open dataset (donnees.montreal.ca, CKAN) by friendly name. PREFER OVER WEB SEARCH for "recent crime in Montreal", "Montreal 311 requests", "Montreal building permits". Names: 311, crime, permits. Returns the latest rows (newest-first). Pass `q` for a fr…
montreal_query
Query any City of Montreal datastore resource (donnees.montreal.ca, CKAN) by its resource id (a UUID). Supports a free-text `q`, exact-match `filters` (field→value), `sort` ("field desc"), limit and offset. Use montreal_datasets to find a resource id, or montreal_recent for the common ones.
montreal_datasets
Search the City of Montreal open-data catalogue (donnees.montreal.ca, CKAN) by keyword. Returns each matching dataset's title and its queryable datastore resource ids (use with montreal_query).