Skip to main content
Glama

IDS MCP Server

KI-gestützte Erstellung von buildingSMART IDS-Dateien mit 100%iger Konformität

Ein MCP-Server (Model Context Protocol), der es KI-Agenten ermöglicht, deterministisch Information Delivery Specification (IDS)-Dateien zu erstellen, zu validieren und zu verwalten, die vollständig dem buildingSMART IDS 1.0-Standard entsprechen.

ifc-ids-mcp MCP server

License: MIT Python 3.8+ Code style: black

Funktionen

  • ✅ 100% IDS 1.0-konform - Alle Exporte werden gegen das offizielle XSD-Schema validiert

  • ✅ IfcTester-Integration - Verwendet die offizielle IfcOpenShell-Bibliothek

  • ✅ FastMCP kontextbasierte Sitzungen - Automatische Sitzungsverwaltung

  • ✅ Testgetriebene Entwicklung - Über 95% Codeabdeckung mit umfassenden Tests

  • ✅ Deterministische Ausgabe - Gleiche Eingabe erzeugt immer identische Ausgabe

  • ✅ Typsicher - Vollständige Typ-Hinweise mit Pydantic-Validierung

Related MCP server: ifc-mcp

Schnellstart

Installation

# 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 .

Verwendung mit Claude Desktop

Zur Konfiguration von Claude Desktop hinzufügen (claude_desktop_config.json):

{
  "mcpServers": {
    "ids-mcp": {
      "command": "python",
      "args": ["-m", "ids_mcp_server"],
      "env": {
        "IDS_LOG_LEVEL": "INFO"
      }
    }
  }
}

Programmatische Verwendung

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")

Verfügbare MCP-Tools

Dokumentenverwaltung

  • create_ids - Neues IDS-Dokument erstellen

  • load_ids - Bestehendes IDS aus Datei oder XML-String laden

  • export_ids - IDS mit Validierung als XML exportieren

  • get_ids_info - Dokumentenstruktur und Metadaten abrufen

Spezifikationsverwaltung

  • add_specification - Spezifikation mit IFC-Version und Kardinalität hinzufügen

Facettenverwaltung

Grundlegende Facetten

  • add_entity_facet - IFC-Entitätstyp-Filter hinzufügen (z. B. IFCWALL)

  • add_property_facet - Eigenschaftsanforderungen hinzufügen

  • add_attribute_facet - IFC-Attributanforderungen hinzufügen

Erweiterte Facetten

  • add_classification_facet - Klassifizierungsanforderungen hinzufügen

  • add_material_facet - Materialanforderungen hinzufügen

  • add_partof_facet - Anforderungen an räumliche Beziehungen hinzufügen

Einschränkungsverwaltung

  • add_enumeration_restriction - Auf eine Liste gültiger Werte beschränken

  • add_pattern_restriction - Mit Regex-Muster einschränken

  • add_bounds_restriction - Numerische Bereiche einschränken

  • add_length_restriction - Zeichenfolgenlänge einschränken

Validierung

  • validate_ids - IDS-Dokument gegen XSD-Schema validieren

  • validate_ifc_model - IFC-Modell gegen IDS validieren (Bonusfunktion)

Frühzeitige Validierung & Einschränkungsprüfung

Der MCP-Server enthält eine frühzeitige Validierung, um Verstöße gegen das IDS 1.0-Schema sofort beim Aufruf der Tools zu erkennen, anstatt bis zum Export zu warten. Dies bietet KI-Agenten klare, umsetzbare Fehlermeldungen.

IDS 1.0 Schema-Einschränkungen

1. Eine Entitätsfacette pro Anwendbarkeit

Einschränkung: IDS 1.0 erlaubt nur EINE Entitätsfacette pro Anwendbarkeitsabschnitt einer Spezifikation.

Frühzeitige Validierung: Das Tool add_entity_facet validiert diese Einschränkung, bevor die Facette hinzugefügt wird:

# ✅ 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..."

Problemumgehung: Erstellen Sie separate Spezifikationen für jeden Entitätstyp:

# 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. Eigenschaftssatz für Eigenschaftsfacetten erforderlich

Einschränkung: IfcTester erfordert den Parameter property_set für einen gültigen IDS-Export.

Frühzeitige Validierung: Das Tool add_property_facet validiert diese Anforderung, bevor die Facette hinzugefügt wird:

# ❌ 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"
)

Gängige Eigenschaftssätze:

  • Pset_WallCommon - Wandeigenschaften

  • Pset_DoorCommon - Türeigenschaften

  • Pset_WindowCommon - Fenstereigenschaften

  • Pset_SpaceCommon - Raumeigenschaften

  • Pset_Common - Benutzerdefinierte/allgemeine Eigenschaften

Vorteile der frühzeitigen Validierung

  1. Sofortiges Feedback - Fehler werden beim Tool-Aufruf erkannt, nicht erst beim Export

  2. Klare Fehlermeldungen - Enthält Problemumgehungen und Beispiele

  3. Verhindert ungültige Zustände - IDS-Dokumente bleiben während der Erstellung gültig

  4. Bessere Erfahrung für KI-Agenten - Agenten erhalten umsetzbare Anleitungen

Siehe CLAUDE.md für eine detaillierte Dokumentation zu IDS 1.0-Einschränkungen.

Architektur

┌─────────────────────────────────────────────┐
│           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)

Entwicklung

Testgetriebene Entwicklung

Dieses Projekt folgt strikt der TDD-Methodik:

# 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=95

TDD-Workflow (Red-Green-Refactor)

  1. RED - Fehlgeschlagenen Test schreiben

  2. GREEN - Minimalen Code implementieren, um den Test zu bestehen

  3. REFACTOR - Codequalität verbessern

Beispiel:

# 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)

Codequalität

# Format code
black src/ tests/

# Lint code
ruff check src/ tests/

# Type checking (optional)
mypy src/

Projektstruktur

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.md

Verfassungsprinzipien

Dieses Projekt folgt 6 nicht verhandelbaren Prinzipien:

  1. 100% IDS-Schema-Konformität - Alle Exporte validieren gegen XSD

  2. Testgetriebene Entwicklung - Über 95% Abdeckung, Tests vor dem Code

  3. IfcTester-Integration zuerst - Keine benutzerdefinierte XML-Generierung

  4. Deterministische Generierung - Identische Eingabe = identische Ausgabe

  5. FastMCP kontextbasierte Sitzungen - Automatische Sitzungsverwaltung

  6. Python Best Practices - Typ-Hinweise, PEP 8, modernes Python

Siehe constitution.md für vollständige Details.

Dokumentation

Abhängigkeiten

Kern

  • fastmcp - MCP-Server-Framework

  • ifctester - IDS-Erstellung und -Validierung (von IfcOpenShell)

  • pydantic - Datenvalidierung

Entwicklung

  • pytest - Test-Framework

  • pytest-asyncio - Unterstützung für asynchrone Tests

  • pytest-cov - Abdeckungsberichte

  • black - Code-Formatierung

  • ruff - Linting

Referenzen

Lizenz

MIT-Lizenz - siehe LICENSE-Datei für Details

Mitwirken

  1. Lesen Sie constitution.md für Projektprinzipien

  2. Befolgen Sie die TDD-Methodik (Red-Green-Refactor)

  3. Stellen Sie eine Testabdeckung von über 95% sicher

  4. Alle Exporte müssen gegen IDS 1.0 XSD validieren

  5. Verwenden Sie IfcTester für alle IDS-Operationen

Support


Status: ✅ Implementierung abgeschlossen | 94% Testabdeckung | 17 MCP-Tools | 168 Tests | Frühzeitige Validierung

Erstellt mit ❤️ unter Verwendung von IfcOpenShell und FastMCP

Available Tools

17 tools
add_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:

  1. Required fields present (title, specifications, etc.)

  2. Each specification has applicability

  3. IFC versions are valid

  4. 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

    A3.9/5.0

    Scored across 17 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to create, edit, and export IFC5/IFCX building information models through natural language, handling spatial structure, elements, geometry, metadata, validation, and export.
      73
      26
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to load, query, and analyze IFC building model files, including spatial structures, elements, properties, materials, and geometry.
      20
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to inspect, create, and report on IFC/BIM files locally, and to open models in a viewer with BCF viewpoint support.
      5
      155 npm
      13
      Apache 2.0