From d4faef9758a64122f5488c4091b4d43e4f9f40b0 Mon Sep 17 00:00:00 2001 From: Peter Alexander Date: Fri, 1 May 2026 20:15:53 +0100 Subject: [PATCH] Add nextCursor to events/list and _meta to event types and occurrences events/list response now shows nextCursor for consistency with base MCP list pagination. Event-type definitions and EventOccurrence both gain optional _meta, matching Tool/Resource/Prompt. --- docs/design-sketch-proposal.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/design-sketch-proposal.md b/docs/design-sketch-proposal.md index d3d7543..ade7ab1 100644 --- a/docs/design-sketch-proposal.md +++ b/docs/design-sketch-proposal.md @@ -77,9 +77,11 @@ Servers advertise event support in their capabilities: "deduplicate_window_seconds": { "type": "integer", "default": 0, "description": "Suppress duplicate alerts within this window" } } }, - "payloadSchema": { "..." : "..." } + "payloadSchema": { "..." : "..." }, + "_meta": { "..." : "..." } // optional; same semantics as on Tool/Resource/Prompt } - ] + ], + "nextCursor": "..." // present when more pages are available; same semantics as tools/list etc. } ``` @@ -184,6 +186,7 @@ Each entry in `events[]`, the params of `notifications/events/event` (plus `requ | `timestamp` | string (ISO 8601) | yes | When the event occurred | | `data` | object | yes | Payload conforming to the event type's `payloadSchema` | | `cursor` | string \| null | no | Subscription position after this event (push/webhook only; poll carries cursor at the response level). `null` when the event type does not support replay — see *Cursor Lifecycle*. | +| `_meta` | object | no | Reserved for protocol/extension metadata, consistent with `_meta` on other MCP types. Not governed by `payloadSchema`. | **Notes:**