In-depth architectural comparison of the Data Edmonton and Data Boston 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 Edmonton
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Data Boston
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Data Edmonton if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Data Boston 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 Edmonton 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 Edmonton open dataset (data.edmonton.ca) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "Edmonton 311 requests", "Edmonton building permits". Names: 311, permits. Returns the latest rows (newest-first). Add a SoQL `where` to filter; for anything els…
edmonton_query
Run a raw SoQL query against any Edmonton open-data resource (data.edmonton.ca) by its Socrata id (8-char like "ukww-xkmj"). Full SoQL: where/select/group/order/limit/offset. Use edmonton_datasets to find a resource id, or edmonton_recent for the common ones.
edmonton_datasets
Search the Edmonton open-data catalogue (data.edmonton.ca) for datasets by keyword. Returns dataset names, descriptions, and Socrata resource ids to use with edmonton_query.
Data Boston Tools (3)
boston_recent
Recent records from a common City of Boston open dataset (data.boston.gov) by friendly name — no CKAN resource id needed. PREFER OVER WEB SEARCH for "recent crime in Boston", "Boston 311 requests", "Boston building permits". Names: crime, 311, permits. Returns the latest rows (newest-first). Pass `…
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 Edmonton is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Data Boston belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Data Edmonton when you need capabilities focused on developer tools and Data Boston when you require tools for developer tools.
Query any City of Boston datastore resource (data.boston.gov, CKAN) by its resource id (a UUID). Supports a free-text `q`, exact-match `filters` (field→value), `sort` ("field desc"), limit and offset. Use boston_datasets to find a resource id, or boston_recent for the common ones.
boston_datasets
Search the City of Boston open-data catalogue (data.boston.gov, CKAN) by keyword. Returns each matching dataset's title and its queryable datastore resource ids (use with boston_query).