cambridge-open-data-ma-mcp
Related Servers
Alternatives to cambridge-open-data-ma-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying City of Boston open data through the CKAN API, providing access to datasets from data.boston.gov via natural language.489 npmMIT
- AlicenseAqualityAmaintenanceLets AI assistants discover public Socrata open-data portals, search their datasets, inspect schemas, and run bounded read-only SoQL queries to answer questions with live government data. All access is strictly read-only and results come straight from the publisher's portal.5128 PyPIMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to search, explore, and query any CKAN open data portal through natural language, making public datasets accessible without requiring knowledge of the portal's API.201,857 npm60MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search, explore, and query San Francisco's open data portal through a standardized interface for public datasets. It supports SQL-like querying via the Socrata platform and includes features like fuzzy column matching and schema caching.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying and exploring the City of Worcester's open data portal (ArcGIS Hub) through natural language, including dataset search, type filtering, schema inspection, spatial point-in-polygon queries, and geocoding.MIT
- AlicenseAqualityCmaintenanceEnables an AI assistant to search and browse the City of Houston Open Data portal (CKAN) — finding datasets, listing departments and topic groups, inspecting table columns, and reading rows with filters, sorting, and paging. It is read-only and requires no key or sign-in.6MIT
TDQS
Scored across 8 tools
Most tools have clearly distinct pipeline roles: refresh_catalog (metadata cache), fetch_dataset (row cache), search/describe (metadata lookup), query (SQL). The only real overlap is field_coverage vs coverage_audit (one field vs all fields), but the descriptions explicitly frame the audit as the batch alternative to the manual check.
Six of eight names follow a clear verb_noun pattern (refresh_catalog, search_datasets, describe_dataset, fetch_dataset, list_cached_datasets), plus the short query. field_coverage and coverage_audit break the pattern as noun phrases, a minor but noticeable deviation.
Eight tools is well-scoped for a dataset-portal pipeline: discovery, schema, fetch, cache listing, coverage checks, and SQL querying, with no redundant entries. Each tool earns its place in a coherent workflow.
The surface covers the full lifecycle from catalog refresh through schema inspection, fetching, coverage auditing, and cross-dataset SQL. Minor gaps exist: no way to delete/evict cached data, no export or pagination of query results, and no catalog filtering by category or update date beyond keyword search.