Skip to main content
Glama
roynertr

COBie MCP

by roynertr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to COBie MCP

No user-submitted related servers found.

    Related Servers

    • Revit MCP Server

      DavidChin0
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Autodesk Revit 2024/2025/2026/2027 via pyRevit — 48 tools for building design, editing, analysis, clash detection, MEP, interop, documentation, and model persistence.
      MIT

    • pdf-reader-mcp

      iflow-mcp
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for extracting text from PDF files, supporting local files and URLs.
      -
    • pymupdf4llm-mcp by pymupdf

      pymupdf4llm-mcpofficial

      pymupdf
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for exporting PDF to markdown, optimized for LLM consumption.
      1,982 PyPI
      71
      AGPL 3.0

    • ifcopenshell-mcp

      Daviidro
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that lets users query, validate, convert, and compare IFC/BIM files using natural language. Runs fully locally and integrates with AI agents like Claude.
      8
      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

    C2.4/5.0

    Scored across 63 tools

    Disambiguation2/5

    Many tools are deprecated aliases duplicating identical functionality (e.g., graph_list_floors_tool vs graph_list_floors), and there is significant overlap between update_cobie, preview_update, capture_installation, and validate_draft_result. get_entity_details has an empty description, making its purpose ambiguous.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (list_floors, validate_cobie, add_document), but naming is inconsistent across families: some use graph_ prefixes, some use _tool suffixes for deprecated aliases, and verbs vary (lookup vs get vs find, load vs get). The pattern is recognizable but not consistently applied.

    Tool Count2/5

    63 tools is excessive for the apparent scope, largely because many are deprecated aliases and near-duplicates (e.g., 10+ graph_* aliases, multiple preview/validate/update combinations). The core functionality could be delivered with fewer, better-differentiated tools.

    Completeness4/5

    The tool set covers a broad COBie lifecycle: import/export, validation, updates, document attachment, graph queries, hierarchy, readiness assessment, and text/PDF extraction. However, get_entity_details and load_cobie_summary lack descriptions, and entity creation for spaces/floors/types is only indirectly supported through update_cobie.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources