Skip to main content
Glama
tookta91

Aedifion MCP Server

by tookta91

Related Servers

Alternatives to Aedifion MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to Tacit building digital twins to query buildings, equipment, sensors, and zones using natural language. It provides tools for exploring Brick-compliant knowledge graphs, fetching historical sensor data, and accessing site documents.
      4
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Connects AI assistants to SkySpark and Haxall building automation systems by dynamically exposing SkySpark Axon functions as MCP tools. Enables natural language interaction with building data, equipment, and automation functions through real-time tool discovery.
      5
      MIT
    • 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
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with SkyFoundry SkySpark building automation data via the Model Context Protocol. It allows users to evaluate Axon expressions, perform CRUD operations on records, and manage project functions through a comprehensive suite of 21 tools.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with Autodesk Revit for building design, editing, analysis, clash detection, MEP, interop, documentation, and model persistence via 48 tools.
      MIT

    TDQS

    B3.1/5.0

    Scored across 123 tools

    Disambiguation4/5

    Most tools are clearly distinct, targeting specific resources and actions like projects, datapoints, analytics, tasks, and AI. However, some overlap exists, such as multiple 'get_' tools for different aspects of analytics or controls, which could cause confusion if an agent doesn't carefully read descriptions. Overall, the naming and domain separation are strong enough to minimize misselection.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. Verbs like 'create_', 'delete_', 'get_', 'update_', 'enable_', 'disable_' are applied predictably across resources, making the set easy to navigate and understand. There are no deviations in style or convention.

    Tool Count2/5

    With 123 tools, the count is excessive for a single server, making it overwhelming and difficult for an agent to manage. While the domain (building management and analytics) is broad, this many tools suggests poor scoping, likely leading to cognitive overload and inefficiency in tool selection, even if the coverage is comprehensive.

    Completeness5/5

    The tool set provides comprehensive CRUD and lifecycle coverage across all major domains: projects, datapoints, analytics, controls, tasks, AI, users, and more. There are no obvious gaps; for example, each resource has create, read, update, and delete operations, and workflows are fully supported with enabling, disabling, triggering, and status checks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues