2026-02-03, 16:50–17:15, B.Con
Infrastructure as Code (IaC) describes standardized infrastructure using code - versionable, reproducible, and automated. But as environments become larger and more diverse, teams must develop and maintain more different API integrations to connect tools, platforms, and processes.
The result: a complex interface landscape of (proprietary) interfaces, small-scale workarounds, and selective bridges that are not only prone to errors but also difficult to scale.
The Model Context Protocol (MCP) offers a different approach here: instead of building a separate API solution for each tool connection, MCP creates a uniform, standardized format for context information. The extension by MCP Server represents the next logical step, in which they become the linchpin for keeping models, metadata, and infrastructure knowledge accessible independently of specific tools. They store the required context centrally, version it, and make it available organization-wide - as a “single source of truth” for infrastructure knowledge.
This talk will present the concept and possibilities and discuss the advantages and disadvantages of MCP. It will also touch on the cultural and technical implications of such a new standard.
Working as a System Engineer in Infrastructure Automation at System Vertrieb Alexander GmbH
Ansible, Terraform, Git, GitLab CI/CD, and the synergy of it all
Learning, always learning
CALMAS-Mindset
Hobbies (currently)
Pen and Paper (Dungeon Master)
Birding (started and it's fun!)
Watching Arte (there is always a perl to find!)
Quotes
I have no special talent. I am only passionately curious. - A. Einstein (1952)
Nihili est vir qui mundum non reddat meliorem. (R. Scott's "Kingdom of Heaven")
It is the small everyday deeds of ordinary folk that keep the darkness at bay. Small acts of kindness and love. - Gandalf (P. Jackson's "The Hobbit")