Meta extension type

Generic metadata passed with most requests.

Metadata reserved by MCP to allow clients and servers to attach additional metadata to their interactions.

Certain key names are reserved by MCP for protocol-level metadata, as specified below; implementations MUST NOT make assumptions about values at these keys.

Additionally, definitions in the schema may reserve particular names for purpose-specific metadata, as declared in those definitions.

Key name format: valid _meta key names have two segments: an optional prefix, and a name.

  • Prefix: If specified, MUST be a series of labels separated by dots (.), followed by a slash (/). Labels MUST start with a letter and end with a letter or digit; interior characters can be letters, digits, or hyphens (-). From the 2025-11-25 revision, implementations SHOULD use reverse DNS notation (e.g., com.example/ rather than example.com/), and any prefix whose second label is modelcontextprotocol or mcp is reserved for MCP use. For example: io.modelcontextprotocol/, dev.mcp/, org.modelcontextprotocol.api/, and com.mcp.tools/ are all reserved, while com.example.mcp/ is not, because its second label is example. The 2025-06-18 revision reserved any prefix carrying modelcontextprotocol or mcp in a label other than the last.
  • Name: Unless empty, MUST begin and end with an alphanumeric character ([a-z0-9A-Z]). MAY contain hyphens (-), underscores (_), dots (.), and alphanumerics in between.

From the 2026-07-28 revision, traceparent, tracestate, and baggage are reserved for OpenTelemetry trace context, as an exception to the prefix rule. When present, their values MUST follow the W3C Trace Context and W3C Baggage formats respectively.

on
Implementers

Constructors

Meta.fromMap(Map<String, Object?> _value)

Operators

operator [](String key) → Object?