idfkit-mcp
OfficialRelated Servers
Alternatives to idfkit-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables natural language interaction with OpenStudio building energy simulation, allowing creation, querying, and modification of models, running EnergyPlus simulations, and analyzing results.57-
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with OpenStudio building energy models through natural language, allowing users to load, inspect, and manipulate OSM files including building geometry, HVAC systems, materials, schedules, and internal loads.11MIT
- FlicenseNot gradedqualityDmaintenanceExposes EnergyPlus simulation control (run, parse metrics, edit schedules) as LLM tools for autonomous building energy optimization.-
- FlicenseNot gradedqualityDmaintenanceExposes EnergyPlus building simulation tools as MCP endpoints, enabling LLMs to run closed-loop energy optimization while maintaining occupant comfort.-
- AlicenseAqualityAmaintenanceEnables natural-language interaction with Ladybug Tools for building performance simulation, 3D modeling, and data visualization, allowing agents to perform complex environmental analysis tasks without CAD software.335 PyPI12GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to understand, query, and manipulate Honeybee building energy models through natural language via the Model Context Protocol.17GPL 3.0
TDQS
Scored across 39 tools
Most tools target a clearly distinct action (add vs batch_add, remove vs remove_objects, validate_model vs check_model_integrity are well-differentiated). A few pairs sit close together — query_timeseries vs export_timeseries, and query_simulation_table vs view_simulation_report — but their descriptions clarify the query/export and data/viewer split.
Nearly all names follow a consistent snake_case verb_noun pattern (add_object, list_objects, run_simulation, view_geometry, download_weather_file). The one outlier is file_manager, a noun-phrase tool with no verb, plus minor verb variety (new_ vs clear_ vs load_), but the convention is largely predictable.
At 39 tools this is well over the comfortable range and could likely be consolidated (e.g. timeseries query/export, report query/view). However the domain genuinely spans model CRUD, schema, docs, validation, simulation, results analysis, weather, and visualization, so the density per functional area (~3-4 tools) is justified.
The surface covers the full EnergyPlus modeling lifecycle: create/load/save/migrate, complete object CRUD plus rename/duplicate, schema and doc introspection, schema and domain-level validation, simulation execution, extensive results analysis, weather retrieval, file management, and visualization. No obvious dead ends for the stated purpose.