Skip to main content
Glama
helenkwok

Fragment MCP Server

by helenkwok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Fragment MCP Server

No user-submitted related servers found.

    Related Servers

    • FS-MCP Server

      boleyn
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that provides intelligent file reading and semantic search capabilities across multiple document formats with security-first access controls.
      7
      MIT

    • Autodesk Build MCP Server

      SamuraiBuddha
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server implementation for Autodesk Construction Cloud Build that enables AI assistants to manage construction issues, RFIs, submittals, photos, forms, and costs through natural language.
      -

    • 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

    B3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: converting IFC to FRAG, fetching elements by category, and loading FRAG files. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool for each task.

    Naming Consistency4/5

    The tools follow a consistent verb-object naming pattern (e.g., convert-ifc-to-frag, fetch-elements-of-category, load-frag), with all names using kebab-case. There is a minor deviation in 'load-frag' being slightly simpler, but overall the naming is predictable and readable.

    Tool Count3/5

    With only 3 tools, the server feels thin for a domain involving IFC/FRAG file processing and element fetching. While the tools cover basic operations, the scope suggests more comprehensive functionality might be expected, such as querying or manipulating loaded data.

    Completeness2/5

    The toolset has significant gaps for a fragment processing domain. It lacks operations for updating, deleting, or querying beyond category fetching, and there are no tools for saving or exporting modified fragments, leaving agents with dead ends in workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources