Skip to main content
Glama
fwextensions

DataSF MCP Server

by fwextensions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to DataSF MCP Server

No user-submitted related servers found.

    Related Servers

    • DataSF MCP

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

    • SF Permits MCP Server

      tbrennem-source
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides access to San Francisco public permitting, business, and property data through the Socrata SODA API. Users can search permit details, aggregate statistics, and look up property assessments using natural language.
      MIT

    • CKAN MCP Server

      ondata
      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
      606 npm
      59
      MIT

    • mcp-data-orlando

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      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.
      3 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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_schema retrieves metadata for a dataset, list_datasf browses datasets with filters, query_datasf executes queries, and search_datasf searches by keywords. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'datasf' as a common suffix (e.g., get_schema, list_datasf, query_datasf, search_datasf). This predictability enhances readability and usability across the tool set.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of interacting with San Francisco's open data portal. Each tool serves a distinct and necessary function, covering browsing, searching, querying, and schema retrieval without being overly sparse or bloated.

    Completeness5/5

    The tool set provides complete coverage for the domain of data exploration and querying: list_datasf and search_datasf enable dataset discovery, get_schema provides metadata for query preparation, and query_datasf allows data retrieval. There are no obvious gaps in the workflow.

    Resources