bim2sim-mcp
Related Servers
Alternatives to bim2sim-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for analyzing building sustainability metrics via Excel, PDF, and frameworks like ESG, LEED, BREEAM, DGNB with IFC integration.2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables one-click BIM audits by chaining IFC statistics, validation, and quantity takeoff workflows through natural language queries.MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that enables building energy analysis through tools for anomaly detection, flexible-load schedule optimization, and battery/solar outage-autonomy simulation using reproducible synthetic data.MIT
- AlicenseAqualityBmaintenanceMCP 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.6Apache 2.0
- AlicenseAqualityBmaintenanceAn 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.8MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI language models with the Bonsai Blender add-on to read, create, and edit IFC models through high-level tool calls.63MIT
TDQS
Scored across 11 tools
Tools are mostly distinct, with clear separation between test context management, cache admin operations, and health check. The only minor overlap is between admin_get_reference_info and get_cached_result, but the distinction (metadata vs. value) is clear.
Non-admin tools follow a verb_noun pattern (enable_test_context, set_test_context, get_cached_result), while admin tools consistently use an 'admin_' prefix. This is a predictable convention, though health_check is a slight deviation.
11 tools is well-scoped for a caching and tracing server, covering test context, cache retrieval, admin functions, and health monitoring without unnecessary bloat.
Cache operations cover retrieval, deletion, listing, info, stats, and namespace clearing, which is comprehensive. Test context has enable, set, reset, and get info. The only gap is no explicit cache creation tool, but that is likely automatic from other operations.