@datadive-tools/mcp 0.14.0 → 0.16.0

package/dist/lib.d.ts

@@ -205,4 +205,37 @@ declare class ApiError extends Error {
  */
 declare const PKG_VERSION: string;
 
-export { type AnyTool, ApiError, type Config, type Credentials, PKG_VERSION, SCOPE_READ, SCOPE_WRITE, type ToolDefinition, allTools, buildServer, loadConfig, requiredScope };
+/**
+ * "What's new" for connected assistants and users (RS-11631).
+ *
+ * MCP has no message for "a new version with new features is out": `tools/list_changed` only
+ * reaches a live session, and the hosted server is stateless, so no session survives a deploy.
+ * Two protocol features carry the news instead, both built from the list below:
+ *
+ *   - `SERVER_INSTRUCTIONS`, sent to the client in the `initialize` result on every connection,
+ *     so the assistant knows the latest additions without the user asking.
+ *   - The `whats_new` prompt, which the user picks by hand (e.g. `/mcp__datadive__whats_new` in
+ *     Claude Code), for the full recent list.
+ *
+ * Both the stdio server (`buildServer`) and the hosted server register them from these exports,
+ * so there is one copy. Add an entry here with every release that changes what a user can do;
+ * keep the wording for users, not developers. Newest first.
+ */
+interface WhatsNewEntry {
+    /** Package version that shipped the change. */
+    version: string;
+    /** yyyy-mm-dd the change reached the hosted server. */
+    released: string;
+    items: string[];
+}
+declare const WHATS_NEW: ReadonlyArray<WhatsNewEntry>;
+declare const SERVER_INSTRUCTIONS: string;
+declare const WHATS_NEW_PROMPT: {
+    name: string;
+    title: string;
+    description: string;
+};
+/** The prompt's single user message: the list plus a request to explain it briefly. */
+declare function whatsNewPromptText(): string;
+
+export { type AnyTool, ApiError, type Config, type Credentials, PKG_VERSION, SCOPE_READ, SCOPE_WRITE, SERVER_INSTRUCTIONS, type ToolDefinition, WHATS_NEW, WHATS_NEW_PROMPT, type WhatsNewEntry, allTools, buildServer, loadConfig, requiredScope, whatsNewPromptText };