Skip to main content
Glama
rosserbusinessarchitecture

Dallas Civic MCP

by rosserbusinessarchitecture
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Dallas Civic MCP

No user-submitted related servers found.

    Related Servers

    • Local Dallas MCP

      mindwear-capitian
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that provides AI assistants with plain-English access to official Dallas-area public data (weather alerts, school ratings, and 311 service requests) without requiring API keys or logins.
      4
      1
      Apache 2.0

    • local-dfw-mcp

      LizzleChen
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to answer DFW civic and property questions using official data sources without API keys.
      9
      87 npm
      2
      Apache 2.0

    • local-houston-mcp

      mindwear-capitian
      A
      license
      A
      quality
      C
      maintenance
      Provides AI assistants with plain-English access to official Houston-area public data including weather alerts and school ratings, no API keys required.
      3
      1
      Apache 2.0

    • DataDallas MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Dallas open data via the Socrata SODA API, allowing access to municipal datasets through natural language.
      2 npm
      MIT

    • Local San Antonio MCP

      mindwear-capitian
      A
      license
      A
      quality
      C
      maintenance
      Provides Claude and any MCP client with plain-English access to official San Antonio-area public data including weather alerts, school ratings, and 311 service calls, with no API keys required.
      4
      1
      Apache 2.0
    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.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct civic dataset: weather alerts, school data, 311 service requests, permits, crime, and property. There is no functional overlap between the domain tools, and the 'about' meta-tool is clearly separated. An agent would have little trouble selecting the right tool for a query.

    Naming Consistency4/5

    Domain tools consistently use a 'dallas_' prefix followed by a clear noun (e.g., dallas_crime, dallas_property). The exception is 'about', which lacks the prefix but is a common server metadata tool. Overall naming is coherent and readable with only a minor deviation.

    Tool Count5/5

    Seven tools (six data tools plus one meta tool) are well within the ideal range for a focused civic data MCP server. Each tool adds a distinct data source and the set feels appropriately scoped—neither sparse nor bloated.

    Completeness4/5

    The server covers the main civic data areas expected for the City of Dallas: alerts, schools, 311, permits, crime, and property records. Some adjacent areas (e.g., traffic, transit, city budgets) are missing, and the property tool deliberately excludes appraised values, so completeness is strong but not exhaustive.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources