BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.cfgmgmtcamp.org//VM78AU
BEGIN:VTIMEZONE
TZID:Europe/Brussels
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-ghent2026-VM78AU@cfp.cfgmgmtcamp.org
DTSTART;TZID=Europe/Brussels:20260203T165000
DTEND;TZID=Europe/Brussels:20260203T171500
DESCRIPTION:Infrastructure as Code (IaC) describes standardized infrastruct
 ure using code - versionable\, reproducible\, and automated. But as enviro
 nments become larger and more diverse\, teams must develop and maintain mo
 re different API integrations to connect tools\, platforms\, and processes
 .\nThe result: a complex interface landscape of (proprietary) interfaces\,
  small-scale workarounds\, and selective bridges that are not only prone t
 o errors but also difficult to scale.\nThe Model Context Protocol (MCP) of
 fers a different approach here: instead of building a separate API solutio
 n for each tool connection\, MCP creates a uniform\, standardized format f
 or context information. The extension by MCP Server represents the next lo
 gical step\, in which they become the linchpin for keeping models\, metada
 ta\, and infrastructure knowledge accessible independently of specific too
 ls. They store the required context centrally\, version it\, and make it a
 vailable organization-wide - as a “single source of truth” for infrast
 ructure knowledge. \n\nThis talk will present the concept and possibilitie
 s and discuss the advantages and disadvantages of MCP. It will also touch 
 on the cultural and technical implications of such a new standard.
DTSTAMP:20260913T140318Z
LOCATION:B.Con
SUMMARY:From Code to Context: Infrastructure as Code and the Model Context 
 Protocol - Mar
URL:https://cfp.cfgmgmtcamp.org/ghent2026/talk/VM78AU/
END:VEVENT
END:VCALENDAR