Skip to main content
Glama
Sign In
seattle-open-data

seattle-open-data

by briandconnelly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to seattle-open-data

No user-submitted related servers found.

    Related Servers

    • opendata-atlas

      briandconnelly
      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

    • DataSF MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and retrieve San Francisco open data from data.sfgov.org via the Socrata SODA API.
      38 npm
      MIT

    • mcp-data-orlando

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and querying Orlando Open Data datasets via Socrata SoQL, providing access to metadata and data rows through natural language or direct tool calls.
      659 npm
      MIT

    • CDC MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query U.S. public-health datasets such as disease surveillance, mortality, behavioral risk factors, and flu activity through the Socrata API, using natural language or direct tool calls.
      415 npm
      MIT

    • mcp-data-cincinnati

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to Cincinnati open data via the Socrata SODA API, allowing users to query datasets using natural language or direct tool calls.
      693 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search for datasets, describe a specific dataset's metadata, access server-wide reference documentation, and query a dataset. The descriptions clearly delineate when to use each, with no overlapping functionality.

    Naming Consistency5/5

    All tools follow the consistent pattern seattle_data_<verb>_<noun> (search_datasets, describe_dataset, get_reference, query_dataset). The verbs are distinct but appropriate, and the naming is predictable and readable.

    Tool Count5/5

    Four tools are well-scoped for a read-only open data query service, covering discovery, metadata inspection, reference, and query execution without redundancy. Each tool earns its place.

    Completeness4/5

    The toolset covers the core workflow: search datasets, describe schema, query data, and access reference help. A minor gap is the lack of a tool to list all datasets without a topic query, but this is a minor limitation in an otherwise complete surface for the domain.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources