cityjson-mcp
Related Servers
Alternatives to cityjson-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for inspecting, analysing, and editing CityJSON and CityGML building datasets.-
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for CPACS-oriented TiGL workflows, enabling lifecycle management, inspection, export, and parameter manipulation of aircraft geometry models without native geometry runtimes.3MIT
- AlicenseAqualityCmaintenanceEnables AI agents and MCP clients to perform 3D asset creation and verification: exact b-rep CAD, GLB validation with embedded certificates, mesh inspection, and physics scenes, with most tools running without Blender.360MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and software to create, edit, inspect, validate, and export CAD geometry through MCP using backend-neutral typed operations, with FreeCAD/OpenCascade as the authoritative B-rep backend and JSCAD preview.1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceBrowser-based geometry processing server that enables AI agents to create geometry, run analysis and operators, inspect results, and take screenshots via MCP.41 npm6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to perform geospatial analysis, spatial data processing, vector and raster operations, coordinate transformations, spatial statistics, mapping, and access to climate, satellite, and other geospatial data through MCP-compatible clients.MIT
TDQS
Scored across 37 tools
Most tools map cleanly to distinct operations (validate vs validate_schema vs validate_geometry; import vs open vs import_text). A few boundaries rely on careful reading, such as open vs import and export vs db_export, but the descriptions generally make the intended use clear.
All tools consistently use the cityjson_ prefix followed by lowercase snake_case verb phrases such as list_imports, validate_geometry, assign_crs, and db_export. No camelCase, no arbitrary verb mixing, and the pattern is predictable across the entire set.
At 37 tools, the server is well past the 25-tool threshold for a heavy surface. While the domain is broad, many tools are thin wrappers around the same underlying cjio engine, and the count adds cognitive load without clearly earning every slot.
The surface covers import/open, query, validation, transformation, export, conversion, database round-tripping, and spec/schema access, which is strong for CityJSON processing. Minor gaps remain, such as no obvious way to list open dataset handles or delete objects, but these are workable limitations rather than dead ends.