@jeffjassky/telemetry 0.1.0 → 0.2.0

package/README.md

@@ -110,7 +110,7 @@ the full suite in CI. `react` and `vue` are optional peers for their client
 entries.
 
 Entry points: `.` (server), `/core`, `/web`, `/react`, `/vue`, `/electron`,
-`/cli`.
+`/cli`, `/mcp` (agent tools), `/mcp/sdk` (official-SDK seam).
 
 ## Try it
 

package/dist/mcp-sdk.cjs

@@ -0,0 +1,19 @@
+'use strict';
+
+// src/server/mcp-sdk.ts
+function registerTelemetryTools(server, tools) {
+  for (const t of tools) {
+    server.registerTool(
+      t.name,
+      { title: t.title, description: t.description, inputSchema: t.inputSchema.shape },
+      async (args, extra) => {
+        const data = await t.handler(args, extra);
+        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
+      }
+    );
+  }
+}
+
+exports.registerTelemetryTools = registerTelemetryTools;
+//# sourceMappingURL=mcp-sdk.cjs.map
+//# sourceMappingURL=mcp-sdk.cjs.map

package/dist/mcp-sdk.cjs.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/server/mcp-sdk.ts"],"names":[],"mappings":";;;AAgCO,SAAS,sBAAA,CAAuB,QAAuB,KAAA,EAA+B;AAC3F,EAAA,KAAA,MAAW,KAAK,KAAA,EAAO;AACrB,IAAA,MAAA,CAAO,YAAA;AAAA,MACL,CAAA,CAAE,IAAA;AAAA,MACF,EAAE,KAAA,EAAO,CAAA,CAAE,KAAA,EAAO,WAAA,EAAa,EAAE,WAAA,EAAa,WAAA,EAAa,CAAA,CAAE,WAAA,CAAY,KAAA,EAAM;AAAA,MAC/E,OAAO,MAAe,KAAA,KAAmB;AACvC,QAAA,MAAM,IAAA,GAAO,MAAM,CAAA,CAAE,OAAA,CAAQ,MAAM,KAAK,CAAA;AACxC,QAAA,OAAO,EAAE,OAAA,EAAS,CAAC,EAAE,MAAM,MAAA,EAAQ,IAAA,EAAM,IAAA,CAAK,SAAA,CAAU,IAAA,EAAM,IAAA,EAAM,CAAC,CAAA,EAAG,CAAA,EAAE;AAAA,MAC5E;AAAA,KACF;AAAA,EACF;AACF","file":"mcp-sdk.cjs","sourcesContent":["import type { ToolDescriptor } from './mcp.js';\n\n/**\n * The one seam to the official MCP SDK — isolated here so the core `./mcp`\n * entry stays runtime-free. The SDK is NOT imported: `McpServerLike` is a\n * structural type, so a real `McpServer` from `@modelcontextprotocol/sdk`\n * satisfies it without this package taking a dependency on it. Any server that\n * exposes a compatible `registerTool` works identically.\n *\n *   import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js'\n *   import { createTelemetryMcp } from '@jeffjassky/telemetry/mcp'\n *   import { registerTelemetryTools } from '@jeffjassky/telemetry/mcp/sdk'\n *\n *   const server = new McpServer({ name: 'my-app', version: '1.0.0' })\n *   registerTelemetryTools(server, createTelemetryMcp({ telemetry, viewerAdapter }))\n */\n\nexport interface McpServerLike {\n  registerTool(\n    name: string,\n    config: { title?: string; description?: string; inputSchema?: Record<string, unknown> },\n    handler: (args: any, extra: unknown) => unknown | Promise<unknown>,\n  ): unknown;\n}\n\n/**\n * Register every descriptor on an MCP server. The SDK takes a zod raw shape as\n * `inputSchema`, which is exactly `descriptor.inputSchema.shape`. Each handler's\n * JSON result is wrapped as a single text content block — the MCP wire shape —\n * and `extra` (the SDK's per-request context) is forwarded verbatim to the\n * descriptor, which is what its viewerAdapter resolves the scope from.\n */\nexport function registerTelemetryTools(server: McpServerLike, tools: ToolDescriptor[]): void {\n  for (const t of tools) {\n    server.registerTool(\n      t.name,\n      { title: t.title, description: t.description, inputSchema: t.inputSchema.shape },\n      async (args: unknown, extra: unknown) => {\n        const data = await t.handler(args, extra);\n        return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };\n      },\n    );\n  }\n}\n"]}

package/dist/mcp-sdk.js

@@ -0,0 +1,17 @@
+// src/server/mcp-sdk.ts
+function registerTelemetryTools(server, tools) {
+  for (const t of tools) {
+    server.registerTool(
+      t.name,
+      { title: t.title, description: t.description, inputSchema: t.inputSchema.shape },
+      async (args, extra) => {
+        const data = await t.handler(args, extra);
+        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
+      }
+    );
+  }
+}
+
+export { registerTelemetryTools };
+//# sourceMappingURL=mcp-sdk.js.map
+//# sourceMappingURL=mcp-sdk.js.map

package/dist/mcp-sdk.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/server/mcp-sdk.ts"],"names":[],"mappings":";AAgCO,SAAS,sBAAA,CAAuB,QAAuB,KAAA,EAA+B;AAC3F,EAAA,KAAA,MAAW,KAAK,KAAA,EAAO;AACrB,IAAA,MAAA,CAAO,YAAA;AAAA,MACL,CAAA,CAAE,IAAA;AAAA,MACF,EAAE,KAAA,EAAO,CAAA,CAAE,KAAA,EAAO,WAAA,EAAa,EAAE,WAAA,EAAa,WAAA,EAAa,CAAA,CAAE,WAAA,CAAY,KAAA,EAAM;AAAA,MAC/E,OAAO,MAAe,KAAA,KAAmB;AACvC,QAAA,MAAM,IAAA,GAAO,MAAM,CAAA,CAAE,OAAA,CAAQ,MAAM,KAAK,CAAA;AACxC,QAAA,OAAO,EAAE,OAAA,EAAS,CAAC,EAAE,MAAM,MAAA,EAAQ,IAAA,EAAM,IAAA,CAAK,SAAA,CAAU,IAAA,EAAM,IAAA,EAAM,CAAC,CAAA,EAAG,CAAA,EAAE;AAAA,MAC5E;AAAA,KACF;AAAA,EACF;AACF","file":"mcp-sdk.js","sourcesContent":["import type { ToolDescriptor } from './mcp.js';\n\n/**\n * The one seam to the official MCP SDK — isolated here so the core `./mcp`\n * entry stays runtime-free. The SDK is NOT imported: `McpServerLike` is a\n * structural type, so a real `McpServer` from `@modelcontextprotocol/sdk`\n * satisfies it without this package taking a dependency on it. Any server that\n * exposes a compatible `registerTool` works identically.\n *\n *   import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js'\n *   import { createTelemetryMcp } from '@jeffjassky/telemetry/mcp'\n *   import { registerTelemetryTools } from '@jeffjassky/telemetry/mcp/sdk'\n *\n *   const server = new McpServer({ name: 'my-app', version: '1.0.0' })\n *   registerTelemetryTools(server, createTelemetryMcp({ telemetry, viewerAdapter }))\n */\n\nexport interface McpServerLike {\n  registerTool(\n    name: string,\n    config: { title?: string; description?: string; inputSchema?: Record<string, unknown> },\n    handler: (args: any, extra: unknown) => unknown | Promise<unknown>,\n  ): unknown;\n}\n\n/**\n * Register every descriptor on an MCP server. The SDK takes a zod raw shape as\n * `inputSchema`, which is exactly `descriptor.inputSchema.shape`. Each handler's\n * JSON result is wrapped as a single text content block — the MCP wire shape —\n * and `extra` (the SDK's per-request context) is forwarded verbatim to the\n * descriptor, which is what its viewerAdapter resolves the scope from.\n */\nexport function registerTelemetryTools(server: McpServerLike, tools: ToolDescriptor[]): void {\n  for (const t of tools) {\n    server.registerTool(\n      t.name,\n      { title: t.title, description: t.description, inputSchema: t.inputSchema.shape },\n      async (args: unknown, extra: unknown) => {\n        const data = await t.handler(args, extra);\n        return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };\n      },\n    );\n  }\n}\n"]}