ExperimentalMcpApi

Annotation marking an API as experimental and subject to changes or removal in the future.

This annotation is used to signal that a particular element, such as a class, function, or property, is part of an experimental API. Such APIs may not be stable, and their usage requires opting in explicitly.

Users of the annotated API must explicitly accept the opt-in requirement to ensure they are aware of the potential instability or unfinished nature of the API.

Targets that can be annotated include:

  • Classes

  • Annotation classes

  • Properties

  • Fields

  • Local variables

  • Value parameters

  • Constructors

  • Functions

  • Property getters

  • Property setters

  • Type aliases