Skip to main content
Glama
louistrue

IFCX MCP

by louistrue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to IFCX MCP

No user-submitted related servers found.

    Related Servers

    • ifc-mcp

      flinker-app
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to inspect, create, and report on IFC/BIM files locally, and to open models in a viewer with BCF viewpoint support.
      5
      85 npm
      11
      Apache 2.0

    • ifc-mcp

      WolfzTech
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to load, query, and analyze IFC building model files, including spatial structures, elements, properties, materials, and geometry.
      20
      MIT

    • 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

    • NavisworksMCP

      shuotao
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI platforms to control Autodesk Navisworks via natural language, supporting model analysis, selection, data extraction, and visual management.
      7
      -
    • idfkit-mcp by idfkit

      idfkit-mcpofficial

      idfkit
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to create, edit, and simulate EnergyPlus building energy models via natural language. Supports schema exploration, model editing, simulation execution, and documentation search.
      39
      3
      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.5/5.0

    Scored across 73 tools

    Disambiguation3/5

    Many tools have clear distinct purposes, but the presence of numerous aliases (e.g., ifcx_add_mesh_geometry for ifcx_create_geometry_mesh) and similar tool names (ifcx_create_model, ifcx_plan_model, ifcx_preview_created_model) may still cause confusion for an agent.

    Naming Consistency4/5

    All tools follow the ifcx_verb_noun pattern with consistent verbs like create, list, export, validate. However, aliases (add vs create, write vs export) break the pattern, and the mixing of 'write' and 'export' for similar actions reduces consistency.

    Tool Count2/5

    With 73 tools, the server is very large. While it covers a broad domain, the number is excessive and likely to overwhelm an agent, making selection difficult. A more focused set or consolidation of related tools would improve coherence.

    Completeness5/5

    The tool surface is extremely comprehensive, covering creation, geometry, spatial structure, changesets, composition, validation, export, query, conflict detection, and more. There are no obvious gaps for the IFCX modeling and collaboration workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources