Differences

This shows you the differences between two versions of the page.

--- 261:releasenotes [2026/04/13 11:07] – [Unified configuration metamodel changes*] Meier, Erich
+++ 261:releasenotes [2026/04/16 11:41] (current) – [MCP Server available as beta version] Iseler, Marc
@@ Line 25: / Line 25: @@
 ===== MCP Server available as beta version =====
-MCP (Model Context Protocol) has established itself as the universal way to connect LLMs (Large Language Models) and other AI systems with data sources.
+MCP (Model Context Protocol) has established itself as the universal way to connect LLMs (Large Language Models) and other AI systems with data sources. It's a common way to integrate Stages into your **enterprise chatbots**, so that your development processes are taken into consideration in those systems.
-Through our new MCP Server, AI systems can access process data managed in Stages for various purposes and use cases.
+Through our new MCP Server, AI systems can access process data managed in Stages for various purposes and use cases. You can therefore adjust the MCP configuration to control the amount of information revealed via the MCP interface.
-**//TBD//**
 [[mcpServer|See here for more info]] on MCP with Stages.
@@ Line 128: / Line 126: @@
 Unlike //Topic//, a //Process Area// contains automatic visualization of the workflows it contains, improving transparency and overview for complex process landscapes.
-=== Pre-Release of new Unified Configuration variants ===
+=== Announcing our Future Standard Metamodel Strategy ===
+With this release, we share adjustments to our standard metamodel strategy. We strive to support new modeling requirements more quickly while minimizing the number of delivered standard metamodel variants.
-//TBD: "strict" vs "backward compatible"//
+[[261:metamodelStrategy|Read here for details]] of the new strategy.