Skip to main content
Glama
cambridge-open-data-ma-mcp

cambridge-open-data-ma-mcp

by ali5ter

Related Servers

Alternatives to cambridge-open-data-ma-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying City of Boston open data through the CKAN API, providing access to datasets from data.boston.gov via natural language.
      489 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Lets 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.
      5
      128 PyPI
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      20
      1,857 npm
      60
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      6
      MIT

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues