Skip to main content
Glama
shuji-bonji

@shuji-bonji/ifc-core-mcp

by shuji-bonji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @shuji-bonji/ifc-core-mcp

No user-submitted related servers found.

    Related Servers

    • w3c-mcp

      shuji-bonji
      A
      license
      A
      quality
      B
      maintenance
      MCP Server for accessing W3C/WHATWG/IETF web specifications. Provides AI assistants with access to official web standards data including specifications, WebIDL definitions, CSS properties, and HTML elements.
      11
      29 npm
      4
      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

    • rdf-mcp

      gtfierro
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP servers for querying Brick and 223P ontologies, enabling abbreviation expansion, term/property lookup, and definition retrieval.
      5
      BSD 3-Clause

    • Shiranui

      i-akiya
      A
      license
      C
      quality
      C
      maintenance
      MCP server for retrieving clinical standard content from the CDISC Library, supporting controlled terminology, ADaM, SDTM, CDASH, SEND metadata, and search.
      31
      7
      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
    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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: entity definition lookup, inheritance hierarchy, propertyset retrieval/search, and entity search. No functional overlap, clear boundaries.

    Naming Consistency4/5

    All tools follow the pattern 'ifc_<verb>_<noun>', but verbs are not perfectly uniform ('get' for three, 'search' for one). Consistent prefix and noun naming, minor verb inconsistency.

    Tool Count4/5

    Four tools is reasonable for a core IFC schema server. Covers essential lookups without being too sparse or bloated. Could include a few more (e.g., types, quantities) but current count is appropriate.

    Completeness4/5

    Covers key aspects of IFC schema: entity definitions, inheritance, propertysets, and search. Missing metadata like types list or quantity sets, but core read operations are well-covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources