@jini-ai/mcp 0.4.1 → 0.4.2

package/dist/server/resources/active-resource.d.ts

@@ -3,8 +3,7 @@ import type { McpResourceDef } from '../resource-protocol.js';
  * `jini://active` -> `GET /api/active`. Returns the raw daemon payload as formatted JSON text,
  * unchanged — unlike `getActiveContextTool`, this does not add a conversational hint when
  * `active:false`; a resource is meant to be raw structured data a client attaches to context, not
- * a model-facing tool result, matching the OD origin's own `od://focus/active` handler (which also
- * returned the raw `/api/active` body with no special-casing).
+ * a model-facing tool result.
  */
 export declare const activeContextResource: McpResourceDef;
 /** The full set of kernel resource defs this package ships, ready to pass as `createMcpToolServer`'s `resources` option. */

package/dist/server/resources/active-resource.js

@@ -1,27 +1,8 @@
 /**
  * @module @jini-ai/mcp/server/resources/active-resource
- *
- * The one MCP *resource* this package ships: a read-only pointer to
- * `GET /api/active` (`packages/http/src/active-context.ts`'s `getActiveRoute`)
- * — the same underlying data `../tools/run-tools.js`'s `getActiveContextTool`
- * already proxies as a *tool*. This is not redundant: OD's origin
- * (`apps/daemon/src/mcp.ts`) exposed the identical `/api/active` payload
- * both ways — as the `get_active_context` tool (already ported, see
- * `../tools/run-tools.js`) AND as the `od://focus/active` resource (its
- * `ListResourcesRequestSchema`/`ReadResourceRequestSchema` handlers) —
- * because tools and resources serve different MCP client affordances: a
- * tool is invoked by the model mid-conversation, while a resource can be
- * listed and attached to context by the user/client without any tool call.
- * This module is that second affordance for the same primitive. See
- * `archived provenance ledger`'s 2026-07-21 addition for why the rest of OD's resource
- * surface (`od://skills/...`, `od://design-systems/...`) was NOT ported the
- * same way (both require a Skill/DesignSystem noun this kernel doesn't have).
- *
- * Security posture matches every other tool/resource in this package: no
- * separate authorization mechanism here — whatever `@jini-ai/http-kit`'s
- * same-origin guard / bearer-auth middleware already enforces on
- * `GET /api/active` is the only gate a read of this resource passes
- * through.
+ * Read-only active-context resource over GET /api/active. Tools let the model request data during
+ * a conversation; resources let clients list and attach that data without invoking a tool.
+ * Target-route same-origin and bearer-auth gates remain authoritative, as for the proxy tools.
  */
 import { getDaemonJson } from '../daemon-client.js';
 import { daemonCallOptions } from '../tool-protocol.js';
@@ -29,8 +10,7 @@ import { daemonCallOptions } from '../tool-protocol.js';
  * `jini://active` -> `GET /api/active`. Returns the raw daemon payload as formatted JSON text,
  * unchanged — unlike `getActiveContextTool`, this does not add a conversational hint when
  * `active:false`; a resource is meant to be raw structured data a client attaches to context, not
- * a model-facing tool result, matching the OD origin's own `od://focus/active` handler (which also
- * returned the raw `/api/active` body with no special-casing).
+ * a model-facing tool result.
  */
 export const activeContextResource = {
     uri: 'jini://active',

package/dist/server/tool-server.d.ts

@@ -1,28 +1,10 @@
 /**
  * @module @jini-ai/mcp/server/tool-server
- *
- * `createMcpToolServer` — the generic stdio MCP server hosting mechanism.
- * Ported from the *mechanism* of OD's `apps/daemon/src/mcp.ts` `runMcpStdio`
- * (idle-exit lifecycle, `Server` + `StdioServerTransport` wiring, holding the
- * process open until stdin closes) with the OD-specific parts — the
- * hardcoded 18-tool `TOOL_DEFS`, the `od://` resource scheme, the
- * project/skill/plugin `instructions` prose — replaced by a caller-supplied,
- * bounded, explicit `tools: readonly McpToolDef[]` list. A caller is the
- * *first* user of this mechanism, not the only one it will ever support (see
- * `archived provenance ledger`'s 2026-07-21 addition for the full design-decision note).
- *
- * `tools` capability is always advertised (`capabilities: {tools: {}}`).
- * `resources` capability (`ListResourcesRequestSchema`/
- * `ReadResourceRequestSchema`, mirroring the tools wiring one section down)
- * is advertised only when the caller supplies at least one entry in the
- * optional `resources` option — a 2026-07-21 addition once this package
- * shipped its first genuinely portable resource (`../resources/
- * active-resource.js`'s `jini://active`, see that file's module doc and
- * `archived provenance ledger`'s 2026-07-21 addition for why the *rest* of OD's resource
- * surface — `od://skills/...`, `od://design-systems/...` — still has no
- * kernel equivalent and stays unported). A caller passing no `resources`
- * gets the exact same `capabilities: {tools: {}}`-only server this module
- * always produced.
+ * Generic stdio hosting for an explicit caller-supplied tool list. Construction validates unique
+ * names synchronously without I/O; run resolves the daemon URL, connects and serves until closure.
+ * Tools capability is always advertised; resources only when nonempty resources are supplied.
+ * Narrow object-shaped server/transport ports permit DI fakes without requiring SDK class instances
+ * with nominal private fields; default adapters translate those contracts to the real SDK.
  */
 import type { Readable, Writable } from 'node:stream';
 import type { McpTransportLike } from './ports.js';

package/dist/server/tool-server.js

@@ -5,7 +5,7 @@ import { CallToolRequestSchema, ListResourcesRequestSchema, ListToolsRequestSche
 import { createMcpIdleExitController } from '../client/client.js';
 import { buildResourceIndex, handleResourceRead, resourcesToList } from './resource-protocol.js';
 import { buildToolIndex, handleToolCall, toolsToList } from './tool-protocol.js';
-/** Auto-exit an idle server after this long with no tool activity — same ceiling the OD origin used for its own stdio MCP server. */
+/** Auto-exit an idle server after this long without tool activity. */
 const DEFAULT_IDLE_MS = 30 * 60 * 1000;
 // SDK objects remain behind these adapters; hosts implement the object-shaped ports above.
 function defaultCreateServer({ info, options }) {

package/dist/server/tools/run-tools.js

@@ -1,17 +1,8 @@
 /**
  * @module @jini-ai/mcp/server/tools/run-tools
- *
- * The first real, concrete `McpToolDef`s hosted by `createMcpToolServer`
- * (`../tool-server.js`) — a proxy over `@jini-ai/http-kit`'s already-gated `Run`
- * transport (`packages/http/src/runs.ts`) plus the generic active-resource
- * channel (`packages/http/src/active-context.ts`) and the agent-def listing
- * (`packages/http/src/agents.ts`). Each tool's `handler` does nothing but
- * validate its own arguments and proxy a single HTTP call via
- * `../daemon-client.js` — no separate authorization mechanism, no caching,
- * no state: whatever `@jini-ai/http-kit`'s same-origin guard / bearer-auth
- * middleware already enforces on the target route is the only gate a call
- * here passes through (see `archived provenance ledger`'s 2026-07-21 addition for the
- * full origin-mapping and what was deliberately not ported).
+ * Proxy tools for runs, active context and agent definitions. Each validates its arguments and
+ * delegates a single request to daemon-client; target-route same-origin and bearer-auth gates
+ * remain authoritative. See daemonCallOptions for shared auth and cancellation propagation.
  */
 import { getDaemonJson, postDaemonJson } from '../daemon-client.js';
 import { daemonCallOptions, requireString } from '../tool-protocol.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jini-ai/mcp",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "Model Context Protocol adapters: server config schema and IO, an MCP client, and agent-side MCP server installation.",
   "license": "Apache-2.0",
   "repository": {
@@ -83,10 +83,29 @@
     "registry": "https://registry.npmjs.org"
   },
   "dependencies": {
+    "@jini-ai/core": "^0.4.2"
+  },
+  "peerDependencies": {
     "@cfworker/json-schema": "^4.1.1",
-    "@modelcontextprotocol/sdk": "^1.29.0",
     "@jini-ai/platform": "^0.5.1",
-    "@jini-ai/core": "^0.4.1"
+    "@modelcontextprotocol/sdk": "^1.29.0"
+  },
+  "peerDependenciesMeta": {
+    "@cfworker/json-schema": {
+      "optional": true
+    },
+    "@jini-ai/platform": {
+      "optional": true
+    },
+    "@modelcontextprotocol/sdk": {
+      "optional": true
+    }
+  },
+  "devDependencies": {
+    "@cfworker/json-schema": "^4.1.1",
+    "@modelcontextprotocol/sdk": "^1.29.0",
+    "@jini-ai/core": "^0.4.2",
+    "@jini-ai/platform": "^0.5.2"
   },
   "scripts": {
     "build": "tsc -p tsconfig.json && chmod +x dist/bin/serve.js",