Skip to main content
Glama
HamerCode

CityDPC-MCP

by HamerCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CityDPC-MCP

No user-submitted related servers found.

    Related Servers

    • cityjson-mcp

      Yarroudh
      A
      license
      B
      quality
      A
      maintenance
      Enables MCP clients to inspect, validate, transform, and query CityJSON models, with support for conversion, persistence, and 3D geometry validation.
      37
      3
      MIT

    • bonsai-mcp

      nhantruong96
      A
      license
      B
      quality
      B
      maintenance
      MCP server for reading, viewing, and editing IFC models using IfcOpenShell and Bonsai. Enables querying model data, viewing via Blender's viewport, and making IFC-semantic edits without raw mesh operations.
      28
      MIT

    • lunar

      polydera
      A
      license
      Not graded
      quality
      D
      maintenance
      Browser-based geometry processing server that enables AI agents to create geometry, run analysis and operators, inspect results, and take screenshots via MCP.
      93 npm
      6
      MIT

    • ifc-geometry-mcp

      Slimouzi
      A
      license
      A
      quality
      B
      maintenance
      MCP server for IFC geometric audit, providing tools to detect space clashes, extract space inventories, compute surface losses, check boundaries, and verify opening correspondences in BIM models.
      6
      Apache 2.0

    • COBie MCP

      roynertr
      A
      license
      C
      quality
      C
      maintenance
      MCP server for COBie Excel validation, updates, and PDF extraction.
      63
      1
      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.5/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have distinct resource/action boundaries: dataset lifecycle, building CRUD, semantic enrichment, spatial analysis, and snapshot history are clearly separated. However, number_of_buildings and analyse_dataset overlap somewhat, and get_all_buildings/get_buiding_Id_list/get_building_by_id require reading descriptions to distinguish intent.

    Naming Consistency4/5

    Tool names mostly follow a snake_case, verb-oriented pattern (list_datasets, load_dataset, create_building, remove_building_attributes). Minor deviations include the noun-only number_of_buildings and the typo/camelCase segment in get_buiding_Id_list.

    Tool Count3/5

    At 19 tools, the set is borderline heavy for the domain. Most tools earn their place, but there is some redundancy around dataset/building summaries that could be consolidated.

    Completeness4/5

    The surface covers dataset loading, creation, filtering, saving, history, and building CRUD, enrichment, removal, and analysis. Minor gaps remain, such as no explicit delete/update dataset operation and no general building geometry update tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources