QueensEstate
Related Servers
Alternatives to QueensEstate
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables LLMs to answer everyday questions about Charlotte and Mecklenburg County using official open data, covering area crime and crashes, 311 service requests, trash and recycling schedules, zoning and rezonings, code enforcement, capital projects, nearby places and bus routes, plus city budget and salary statistics. It also exposes generic tools for searching, describing, querying, and summarizing any of the portal's roughly 380 ArcGIS datasets by keyword, SQL filter, or location.19-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and query City of Charlotte GIS datasets (parcels, zoning, public works) via ArcGIS Feature Services.3 npm1MIT
- FlicenseAqualityBmaintenanceAn MCP server that exposes Charlotte, NC and Mecklenburg County open data as tools for an LLM agent, enabling queries about trash pickup, parcels, zoning, crime, and more by geocoding addresses and querying live ArcGIS layers.21-
- AlicenseNot gradedqualityCmaintenanceProvides access to Cincinnati open data via the Socrata SODA API, allowing users to query datasets using natural language or direct tool calls.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
TDQS
Scored across 19 tools
Each tool targets a distinct civic data domain: crashes, crime, 311, code enforcement, closures, rezonings, budget, salaries, and open data. Even the three crime-related tools are cleanly separated by location vs. citywide aggregation.
Most tools follow a clear verb_noun pattern like get_crime_near, summarize_crime, and describe_dataset. Minor deviations like lookup_address, find_nearby_places, and search_datasets break the strict 'get_' pattern, but the naming is still predictable and readable.
Nineteen tools is slightly above the typical sweet spot, but the server covers a broad municipal data platform spanning many domains. Each tool has a clear role, and the dataset meta-tools justify the extra count by enabling open-ended queries beyond the purpose-built tools.
The tool surface is unusually complete: address lookup, property/government profiles, safety, traffic, 311, code enforcement, planning, transportation, budget, and salary data are all covered. The generic dataset search/describe/query/summarize tools eliminate dead ends by allowing access to the full open data catalog.