Skip to main content
Glama
cityjson-mcp

cityjson-mcp

by Yarroudh

Related Servers

Alternatives to cityjson-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for inspecting, analysing, and editing CityJSON and CityGML building datasets.
      19
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Provides MCP tools for CPACS-oriented TiGL workflows, enabling lifecycle management, inspection, export, and parameter manipulation of aircraft geometry models without native geometry runtimes.
      11
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      36
      48 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to create and edit parametric FreeCAD models, run Python inside FreeCAD, capture viewport screenshots, inspect documents, execute headless scripts, and run FEM analyses.
      17
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable LLM clients to generate CGA rule source from natural language, compile CGA rules into 3D GLB models, and access CityEngine official parsing and demo-library tools. It supports local installation or hosted streamable HTTP with per-service or unified API keys.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      Apache 2.0

    TDQS

    B3/5.0

    Scored across 42 tools

    Disambiguation3/5

    Most tools target a distinct operation, but two clusters overlap heavily: the upload/import family (cityjson_upload, cityjson_upload_start, cityjson_upload_chunk/finish/cancel, cityjson_import, cityjson_import_text, cityjson_open, cityjson_list_imports) and the validation family (cityjson_validate, cityjson_validate_schema, cityjson_validate_geometry). Descriptions do provide guidance on when to use each, but an agent must read carefully to avoid misselection.

    Naming Consistency4/5

    All tools use a consistent snake_case cityjson_-prefixed verb_noun pattern (cityjson_validate_geometry, cityjson_subset, cityjson_reproject, etc.), which is highly predictable. A few exceptions are noun-only (cityjson_info, cityjson_download, cityjson_backend_status) but these remain readable and consistent in style.

    Tool Count2/5

    42 tools is heavy for the stated scope and pushes well past the 15-tool guideline, especially since much of the surface is protocol plumbing (upload chunk/finish/cancel) and redundant validation entry points. The set feels over-expanded rather than tightly scoped.

    Completeness4/5

    Coverage of the CityJSON lifecycle is strong: ingestion, validation, spatial/CRS transforms, geometry cleanup, subsetting, format conversion, DB import/export, querying, and spec/schema lookups are all present. Minor gaps exist around mutating object data—no attribute-set/add or object creation/deletion tools—but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data