IDS MCP Server
Servidor MCP IDS
Creación de archivos IDS de buildingSMART impulsada por IA con un 100% de cumplimiento
Un servidor MCP (Model Context Protocol) que permite a los agentes de IA crear, validar y gestionar de forma determinista archivos de Especificación de Entrega de Información (IDS) que cumplen totalmente con el estándar IDS 1.0 de buildingSMART.
Características
✅ 100% compatible con IDS 1.0 - Todas las exportaciones se validan contra el esquema XSD oficial
✅ Integración con IfcTester - Utiliza la biblioteca oficial de IfcOpenShell
✅ Sesiones basadas en contexto FastMCP - Gestión automática de sesiones
✅ Desarrollo guiado por pruebas (TDD) - Más del 95% de cobertura de código con pruebas exhaustivas
✅ Salida determinista - La misma entrada siempre produce una salida idéntica
✅ Seguridad de tipos - Sugerencias de tipo completas con validación Pydantic
Related MCP server: ifc-mcp
Inicio rápido
Instalación
# Clone repository
git clone https://github.com/Quasar-Consulting-Group/ifc-ids-mcp.git
cd ifc-ids-mcp
# Install dependencies
pip install -r requirements.txt
# Install in development mode
pip install -e .Uso con Claude Desktop
Añadir a la configuración de Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"ids-mcp": {
"command": "python",
"args": ["-m", "ids_mcp_server"],
"env": {
"IDS_LOG_LEVEL": "INFO"
}
}
}
}Uso programático
from ifctester import ids
# The MCP server handles this automatically via tools
# But you can also use IfcTester directly:
# Create new IDS
my_ids = ids.Ids(title="Project Requirements")
# Add specification
spec = ids.Specification(name="Wall Requirements", ifcVersion=["IFC4"])
spec.applicability.append(ids.Entity(name="IFCWALL"))
requirement = ids.Property(
baseName="FireRating",
propertySet="Pset_WallCommon",
cardinality="required"
)
spec.requirements.append(requirement)
my_ids.specifications.append(spec)
# Export to XML
my_ids.to_xml("requirements.ids")Herramientas MCP disponibles
Gestión de documentos
create_ids - Crear nuevo documento IDS
load_ids - Cargar IDS existente desde un archivo o cadena XML
export_ids - Exportar IDS a XML con validación
get_ids_info - Obtener la estructura y metadatos del documento
Gestión de especificaciones
add_specification - Añadir especificación con versión IFC y cardinalidad
Gestión de facetas
Facetas básicas
add_entity_facet - Añadir filtro de tipo de entidad IFC (p. ej., IFCWALL)
add_property_facet - Añadir requisitos de propiedad
add_attribute_facet - Añadir requisitos de atributo IFC
Facetas avanzadas
add_classification_facet - Añadir requisitos de clasificación
add_material_facet - Añadir requisitos de material
add_partof_facet - Añadir requisitos de relación espacial
Gestión de restricciones
add_enumeration_restriction - Restringir a una lista de valores válidos
add_pattern_restriction - Restringir con patrón regex
add_bounds_restriction - Restringir rangos numéricos
add_length_restriction - Restringir la longitud de la cadena
Validación
validate_ids - Validar documento IDS contra el esquema XSD
validate_ifc_model - Validar modelo IFC contra IDS (función adicional)
Validación temprana y comprobación de restricciones
El servidor MCP incluye validación temprana para detectar violaciones del esquema IDS 1.0 inmediatamente cuando se llaman a las herramientas, en lugar de esperar hasta el momento de la exportación. Esto proporciona a los agentes de IA mensajes de error claros y procesables.
Restricciones del esquema IDS 1.0
1. Una sola faceta de entidad por aplicabilidad
Restricción: IDS 1.0 permite solo UNA faceta de entidad por sección de aplicabilidad de la especificación.
Validación temprana: La herramienta add_entity_facet valida esta restricción antes de añadir la faceta:
# ✅ CORRECT: First entity facet
add_entity_facet(spec_id="S1", location="applicability", entity_name="IFCWALL")
# ❌ INCORRECT: Second entity facet raises ToolError immediately
add_entity_facet(spec_id="S1", location="applicability", entity_name="IFCDOOR")
# Error: "IDS 1.0 XSD constraint violation: Only ONE entity facet is allowed..."Solución alternativa: Crear especificaciones separadas para cada tipo de entidad:
# Specification 1: Walls
add_specification(name="Wall Requirements", ifc_versions=["IFC4"], identifier="S1")
add_entity_facet(spec_id="S1", location="applicability", entity_name="IFCWALL")
# Specification 2: Doors
add_specification(name="Door Requirements", ifc_versions=["IFC4"], identifier="S2")
add_entity_facet(spec_id="S2", location="applicability", entity_name="IFCDOOR")2. Conjunto de propiedades requerido para facetas de propiedad
Restricción: IfcTester requiere el parámetro property_set para una exportación IDS válida.
Validación temprana: La herramienta add_property_facet valida este requisito antes de añadir la faceta:
# ❌ INCORRECT: Missing property_set raises ToolError immediately
add_property_facet(
spec_id="S1",
location="requirements",
property_name="FireRating"
)
# Error: "Property facet validation error: 'property_set' parameter is required..."
# ✅ CORRECT: Include property_set parameter
add_property_facet(
spec_id="S1",
location="requirements",
property_name="FireRating",
property_set="Pset_WallCommon"
)Conjuntos de propiedades comunes:
Pset_WallCommon- Propiedades de muroPset_DoorCommon- Propiedades de puertaPset_WindowCommon- Propiedades de ventanaPset_SpaceCommon- Propiedades de espacioPset_Common- Propiedades personalizadas/genéricas
Beneficios de la validación temprana
Retroalimentación inmediata - Los errores se detectan al invocar la herramienta, no al exportar
Mensajes de error claros - Incluye soluciones alternativas y ejemplos
Previene estados inválidos - Los documentos IDS permanecen válidos durante toda la creación
Mejor experiencia para el agente de IA - Los agentes reciben orientación procesable
Consulte CLAUDE.md para obtener documentación detallada sobre las restricciones de IDS 1.0.
Arquitectura
┌─────────────────────────────────────────────┐
│ AI Agent (Claude, GPT) │
└────────────────────┬────────────────────────┘
│ MCP Protocol
┌────────────────────▼────────────────────────┐
│ FastMCP Server │
│ ┌──────────────────────────────────────┐ │
│ │ MCP Tools (15+ tools) │ │
│ └───────────────┬──────────────────────┘ │
│ ┌───────────────▼──────────────────────┐ │
│ │ Session Manager (Context) │ │
│ └───────────────┬──────────────────────┘ │
│ ┌───────────────▼──────────────────────┐ │
│ │ IfcTester Integration (IDS Engine) │ │
│ └──────────────────────────────────────┘ │
└─────────────────────────────────────────────┘
│
▼
IDS XML File (100% XSD compliant)Desarrollo
Desarrollo guiado por pruebas (TDD)
Este proyecto sigue estrictamente la metodología TDD:
# Run all tests
pytest tests/ -v
# Run with coverage
pytest tests/ --cov=src/ids_mcp_server --cov-report=html
# Run specific test category
pytest tests/unit/ -v # Unit tests
pytest tests/integration/ -v # Integration tests
pytest tests/validation/ -v # XSD validation tests
# Must maintain 95%+ coverage
pytest tests/ --cov-fail-under=95Flujo de trabajo TDD (Red-Green-Refactor)
RED - Escribir una prueba que falle
GREEN - Implementar el código mínimo para pasarla
REFACTOR - Mejorar la calidad del código
Ejemplo:
# RED: Write failing test
def test_create_specification():
result = add_specification(name="Test", ifc_versions=["IFC4"])
assert result["status"] == "success"
# GREEN: Implement
def add_specification(name, ifc_versions):
return {"status": "success"}
# REFACTOR: Improve (keep tests passing)Calidad del código
# Format code
black src/ tests/
# Lint code
ruff check src/ tests/
# Type checking (optional)
mypy src/Estructura del proyecto
ifc-ids-mcp/
├── src/
│ └── ids_mcp_server/
│ ├── __init__.py
│ ├── __main__.py
│ ├── server.py # FastMCP server
│ ├── config.py # Configuration
│ ├── version.py # Version management
│ ├── session/ # Session management
│ │ ├── manager.py
│ │ ├── storage.py
│ │ ├── cleanup.py
│ │ └── models.py # Session data models
│ └── tools/ # MCP tools (17 total)
│ ├── document.py
│ ├── specification.py
│ ├── facets.py
│ ├── restrictions.py # Phase 007
│ ├── validation.py # Phase 008
│ └── validators.py # Early validation helpers
├── tests/ # 168 tests, 94% coverage
│ ├── unit/ # Unit tests
│ ├── component/ # Component tests
│ ├── integration/ # Integration tests
│ └── validation/ # XSD compliance tests
│ └── fixtures/ # Test fixtures
├── samples/ # Sample IDS/IFC files
│ ├── wall_fire_rating.ids
│ └── walls-fire-rating.ifc
├── specs/ # Implementation plans (PRDs)
├── .mcp.json # MCP server configuration
├── .coveragerc # Coverage configuration
├── constitution.md # Project principles
├── DESIGN_SPECIFICATION.md # Technical specification
├── CLAUDE.md # AI agent guide
├── pyproject.toml
├── pytest.ini
└── README.mdPrincipios de la constitución
Este proyecto sigue 6 principios innegociables:
100% cumplimiento del esquema IDS - Todas las exportaciones se validan contra XSD
Desarrollo guiado por pruebas - Más del 95% de cobertura, pruebas antes que código
Integración prioritaria con IfcTester - Sin generación de XML personalizada
Generación determinista - Entrada idéntica = salida idéntica
Sesiones basadas en contexto FastMCP - Gestión automática de sesiones
Buenas prácticas de Python - Sugerencias de tipo, PEP 8, Python moderno
Consulte constitution.md para obtener todos los detalles.
Documentación
Constitución - Principios innegociables
Especificación de diseño - Diseño técnico completo
Guía para agentes de IA - Guía para agentes de IA que trabajan en este proyecto
Planes de implementación - PRD fase por fase
Dependencias
Núcleo
fastmcp - Marco de trabajo del servidor MCP
ifctester - Creación y validación de IDS (de IfcOpenShell)
pydantic - Validación de datos
Desarrollo
pytest - Marco de trabajo de pruebas
pytest-asyncio - Soporte para pruebas asíncronas
pytest-cov - Informes de cobertura
black - Formato de código
ruff - Linting
Referencias
Estándar IDS: https://www.buildingsmart.org/standards/bsi-standards/information-delivery-specification-ids/
Esquema XSD de IDS: https://standards.buildingsmart.org/IDS/1.0/ids.xsd
Documentación de IfcTester: https://docs.ifcopenshell.org/ifctester.html
FastMCP: https://gofastmcp.com/
buildingSMART: https://www.buildingsmart.org/
Licencia
Licencia MIT - consulte el archivo LICENSE para obtener más detalles
Contribución
Lea constitution.md para conocer los principios del proyecto
Siga la metodología TDD (Red-Green-Refactor)
Asegure una cobertura de pruebas superior al 95%
Todas las exportaciones deben validarse contra el XSD de IDS 1.0
Utilice IfcTester para todas las operaciones IDS
Soporte
Problemas: https://github.com/Quasar-Consulting-Group/ifc-ids-mcp/issues
Debates: https://github.com/Quasar-Consulting-Group/ifc-ids-mcp/discussions
Estado: ✅ Implementación completa | 94% de cobertura de pruebas | 17 herramientas MCP | 168 pruebas | Validación temprana
Creado con ❤️ usando IfcOpenShell y FastMCP
Available Tools
17 toolsadd_attribute_facetC
Add an attribute facet to a specification.
Args: spec_id: Specification identifier location: "applicability" or "requirements" attribute_name: Attribute name (e.g., "Name", "Description") ctx: FastMCP Context (auto-injected) value: Required value or pattern cardinality: "required", "optional", or "prohibited"
Returns: {"status": "added", "facet_type": "attribute", "spec_id": "S1"}
Inputs: spec_id (required), location (required), attribute_name (required), value, +1 more. Returns: object
add_bounds_restrictionB
Add numeric bounds restriction.
Args: spec_id: Specification identifier or name facet_index: Index of facet in location (0-based) parameter_name: Which parameter to restrict (e.g., "value") base_type: XSD base type (e.g., "xs:double", "xs:integer") ctx: FastMCP Context (auto-injected) location: "applicability" or "requirements" (default: "requirements") min_inclusive: Minimum value (inclusive) max_inclusive: Maximum value (inclusive) min_exclusive: Minimum value (exclusive) max_exclusive: Maximum value (exclusive)
Returns: {"status": "added", "restriction_type": "bounds", "spec_id": "S1"}
Example: Add bounds to property value: Height must be between 2.4 and 3.0 meters
Inputs: spec_id (required), facet_index (required), parameter_name (required), base_type (required), +5 more. Returns: object
add_classification_facetA
Add a classification facet to a specification.
Args: spec_id: Specification identifier location: "applicability" or "requirements" classification_value: Classification code or pattern ctx: FastMCP Context (auto-injected) classification_system: Classification system name or URI cardinality: "required", "optional", or "prohibited"
Returns: {"status": "added", "facet_type": "classification", "spec_id": "S1"}
Inputs: spec_id (required), location (required), classification_value (required), classification_system, +1 more. Returns: object
add_entity_facetA
Add an entity facet to a specification.
IMPORTANT: IDS 1.0 allows only ONE entity facet per applicability section. If you need multiple entity types, create separate specifications.
Args: spec_id: Specification identifier location: "applicability" or "requirements" entity_name: IFC entity name (e.g., "IFCWALL") ctx: FastMCP Context (auto-injected) predefined_type: Optional predefined type cardinality: "required", "optional", or "prohibited" (requirements only)
Returns: {"status": "added", "facet_type": "entity", "spec_id": "S1"}
Raises: ToolError: If trying to add second entity to applicability section
Inputs: spec_id (required), location (required), entity_name (required), predefined_type, +1 more. Returns: object
add_enumeration_restrictionA
Add enumeration restriction (list of allowed values).
Args: spec_id: Specification identifier or name facet_index: Index of facet in location (0-based) parameter_name: Which parameter to restrict (e.g., "value", "propertySet") base_type: XSD base type (e.g., "xs:string", "xs:integer") values: List of allowed values ctx: FastMCP Context (auto-injected) location: "applicability" or "requirements" (default: "requirements")
Returns: {"status": "added", "restriction_type": "enumeration", "spec_id": "S1"}
Example: Add enumeration to property value: FireRating must be "REI30", "REI60", or "REI90"
Inputs: spec_id (required), facet_index (required), parameter_name (required), base_type (required), +2 more. Returns: object
add_length_restrictionB
Add string length restriction.
Args: spec_id: Specification identifier or name facet_index: Index of facet in location (0-based) parameter_name: Which parameter to restrict (e.g., "value") base_type: XSD base type (e.g., "xs:string") ctx: FastMCP Context (auto-injected) location: "applicability" or "requirements" (default: "requirements") length: Exact length min_length: Minimum length max_length: Maximum length
Returns: {"status": "added", "restriction_type": "length", "spec_id": "S1"}
Example: Add length restriction to attribute value: Tag must be between 5 and 50 characters
Inputs: spec_id (required), facet_index (required), parameter_name (required), base_type (required), +4 more. Returns: object
add_material_facetB
Add a material facet to a specification.
Args: spec_id: Specification identifier location: "applicability" or "requirements" material_value: Material name, category, or URI ctx: FastMCP Context (auto-injected) cardinality: "required", "optional", or "prohibited"
Returns: {"status": "added", "facet_type": "material", "spec_id": "S1"}
Inputs: spec_id (required), location (required), material_value (required), cardinality. Returns: object
add_partof_facetC
Add a partOf facet to a specification.
Args: spec_id: Specification identifier location: "applicability" or "requirements" relation: Relationship type (e.g., "IFCRELCONTAINEDINSPATIALSTRUCTURE") parent_entity: Parent entity name (e.g., "IFCSPACE") ctx: FastMCP Context (auto-injected) parent_predefined_type: Optional predefined type for parent cardinality: "required", "optional", or "prohibited"
Returns: {"status": "added", "facet_type": "partof", "spec_id": "S1"}
Inputs: spec_id (required), location (required), relation (required), parent_entity (required), +2 more. Returns: object
add_pattern_restrictionA
Add pattern restriction (regex matching).
Args: spec_id: Specification identifier or name facet_index: Index of facet in location (0-based) parameter_name: Which parameter to restrict (e.g., "value") base_type: XSD base type (e.g., "xs:string") pattern: Regular expression pattern ctx: FastMCP Context (auto-injected) location: "applicability" or "requirements" (default: "requirements")
Returns: {"status": "added", "restriction_type": "pattern", "spec_id": "S1"}
Example: Add pattern to attribute value: Name must match "EW-[0-9]{3}"
Inputs: spec_id (required), facet_index (required), parameter_name (required), base_type (required), +2 more. Returns: object
add_property_facetA
Add a property facet to a specification.
IMPORTANT: The property_set parameter is REQUIRED for valid IDS export.
Args: spec_id: Specification identifier location: "applicability" or "requirements" property_name: Property name (e.g., "FireRating") ctx: FastMCP Context (auto-injected) property_set: Property set name (e.g., "Pset_WallCommon") - REQUIRED data_type: IFC data type (e.g., "IFCLABEL") value: Required value or pattern cardinality: "required", "optional", or "prohibited"
Returns: {"status": "added", "facet_type": "property", "spec_id": "S1"}
Raises: ToolError: If property_set is None or empty
Inputs: spec_id (required), location (required), property_name (required), property_set, +3 more. Returns: object
add_specificationB
Add a specification to the current session's IDS document.
Args: name: Specification name ifc_versions: List of IFC versions (e.g., ["IFC4", "IFC4X3"]) ctx: FastMCP Context (auto-injected) identifier: Optional unique identifier description: Why this information is required instructions: How to fulfill requirements min_occurs: Minimum occurrences (0 = optional) max_occurs: Maximum occurrences (int or "unbounded")
Returns: { "status": "added", "spec_id": "S1", "ifc_versions": ["IFC4"] }
Inputs: name (required), ifc_versions (required), identifier, description, +3 more. Returns: object
create_idsA
Create a new IDS document for this session.
Session is automatically tracked by FastMCP - no session_id parameter needed!
Args: title: Document title (required) ctx: FastMCP Context (auto-injected) author: Author email or name version: Version string date: Date in YYYY-MM-DD format description: Document description copyright: Copyright notice milestone: Project milestone purpose: Purpose of this IDS
Returns: { "status": "created", "session_id": "auto-generated-by-fastmcp", "title": "..." }
Inputs: title (required), author, version, date, +4 more. Returns: object
export_idsA
Export IDS document to XML file using IfcTester.
Uses current session automatically - no session_id parameter needed!
Args: ctx: FastMCP Context (auto-injected) output_path: File path (optional, returns XML string if not provided) validate: Whether to validate against XSD (default: True)
Returns: { "status": "exported", "xml": "...", # If no output_path "file_path": "...", # If output_path provided "validation": {"valid": true, "errors": []} }
Inputs: output_path, validate. Returns: object
get_ids_infoA
Get current session's IDS document structure.
Uses current session automatically - no session_id parameter needed!
Args: ctx: FastMCP Context (auto-injected)
Returns: { "title": "...", "author": "...", "specification_count": 3, "specifications": [...] }
Inputs: no named parameters. Returns: object
load_idsA
Load an existing IDS file into the current session.
Replaces any existing IDS in this session.
Args: source: File path or XML string ctx: FastMCP Context (auto-injected) source_type: "file" or "string"
Returns: { "status": "loaded", "title": "...", "specification_count": 3, "specifications": [...] }
Inputs: source (required), source_type. Returns: object
validate_idsA
Validate current session's IDS document.
Validates:
Required fields present (title, specifications, etc.)
Each specification has applicability
IFC versions are valid
XSD schema compliance (via IfcTester)
Args: ctx: FastMCP Context (auto-injected)
Returns: { "valid": true, "errors": [], "warnings": [], "specifications_count": 3, "details": { "has_title": true, "has_specifications": true, "xsd_valid": true } }
Inputs: no named parameters. Returns: object
validate_ifc_modelA
Validate an IFC model against the current session's IDS specifications.
This bonus feature leverages IfcTester's IFC validation capabilities.
Args: ifc_file_path: Path to IFC file ctx: FastMCP Context (auto-injected) report_format: "console", "json", or "html"
Returns (json format): { "status": "validation_complete", "total_specifications": 3, "passed_specifications": 2, "failed_specifications": 1, "report": { "specifications": [ { "name": "Wall Fire Rating", "status": "passed", "applicable_entities": 25, "passed_entities": 25, "failed_entities": 0 }, ... ] } }
Inputs: ifc_file_path (required), report_format. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Each tool has a clearly distinct purpose with no overlap. The 'add_' tools create specific facet or restriction types (e.g., attribute, bounds, classification), while the management tools (create_ids, export_ids, etc.) handle document lifecycle operations. The descriptions clearly differentiate what each tool does, preventing agent confusion.
All tools follow a consistent verb_noun pattern with snake_case throughout. The 'add_' prefix is used uniformly for facet/restriction creation tools, while management tools use clear verbs like create, export, get, load, and validate. This predictable naming makes the tool set easy to navigate and understand.
With 17 tools, this server provides comprehensive coverage for IDS document creation and validation. The count is well-scoped for the domain, including core operations (create, export, validate), facet types (entity, property, material, etc.), and restriction types (bounds, enumeration, pattern). Each tool earns its place without redundancy.
The tool set provides complete coverage for IDS document lifecycle management. It includes document creation (create_ids), loading (load_ids), editing (add_* facets/restrictions), inspection (get_ids_info), validation (validate_ids), export (export_ids), and even model validation (validate_ifc_model). All essential CRUD operations are present with no apparent gaps.
Maintenance
Related MCP Connectors
15 deterministic validation tools for AI agents: tax IDs (15 countries), VAT, IBAN, LEI, HS codes.
Agent verification tools: CSV quality, citation checks, AI-readiness audits, requirement extraction
Edit IFC/BIM building models by language: quantities, checks, edits, new elements, undoable.
Create and manage test cases, test runs and results in Testiny from your AI assistant.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI assistants to create, edit, and export IFC5/IFCX building information models through natural language, handling spatial structure, elements, geometry, metadata, validation, and export.7326MIT
- AlicenseAqualityDmaintenanceEnables AI agents to load, query, and analyze IFC building model files, including spatial structures, elements, properties, materials, and geometry.201MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to query standardized building classifications, properties, and data dictionaries from buildingSMART for BIM model enrichment.93-
- AlicenseAqualityCmaintenanceEnables AI assistants to inspect, create, and report on IFC/BIM files locally, and to open models in a viewer with BCF viewpoint support.5155 npm13Apache 2.0