Skip to main content
Glama
ajwann

Charlotte Open Data MCP Server

by ajwann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Charlotte Open Data MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-arcgis-cary

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Town of Cary GIS open geospatial data (parcels, zoning, parks, etc.) through natural language or direct tool calls, allowing dataset search, feature querying, and schema inspection.
      3 npm
      MIT

    • mcp-arcgis-durham

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and querying Durham, North Carolina open geospatial data from ArcGIS Feature/Map Services, including parcels, zoning, and public safety datasets via natural language or direct tool calls.
      3 npm
      MIT

    • mcp-data-cincinnati

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to Cincinnati open data via the Socrata SODA API, allowing users to query datasets using 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.7/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools map to distinct data domains (311, crime, crashes, budget, etc.), but get_address_profile duplicates several specialized capabilities—especially trash/recycling schedule—and the generic query_dataset/summarize_dataset can answer questions also covered by purpose-built tools. Descriptions provide guidance (e.g., search_datasets says to use purpose-built tools first), so misselection risk is moderate but present.

    Naming Consistency5/5

    All 19 tools use snake_case with a verb-first pattern (get_, lookup_, summarize_, find_, search_, describe_, query_), and resource names are clear and predictable. Minor verb variety (get vs lookup vs find) is semantically appropriate and does not break consistency.

    Tool Count4/5

    19 tools is on the higher side but justified by the breadth of Charlotte open data (address, transit, safety, budget, etc.) plus a generic dataset access layer. Each tool targets a distinct data type, though the composite address profile and generic trio create some redundancy.

    Completeness4/5

    The surface covers major city data domains and the generic search/describe/query/summarize tools allow access to any of ~380 portal datasets, so agents can answer most questions without dead ends. Minor gaps include real-time transit arrivals and a dedicated bus stop tool (handled indirectly via find_nearby_places), but overall coverage is strong.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources