@stone-js/mcp-dev 0.8.8 → 0.8.10

package/dist/browser/options/McpDevBlueprint.d.ts

@@ -1,18 +0,0 @@
-import { McpDevOptions } from '../../declarations';
-import { McpDevBlueprint } from '../../options/McpDevBlueprint';
-/**
- * Browser stub of the MCP dev blueprint.
- *
- * It carries the config bucket but wires **no** blueprint middleware, so importing it into a browser
- * bundle never pulls the Node-only `stone mcp` command, its server (`@modelcontextprotocol/sdk`,
- * stdio) or the filesystem. The `stone mcp` command is a development, Node-only concern; in the
- * browser this keeps the app compiling and inert.
- */
-export declare const mcpDevBlueprint: McpDevBlueprint;
-/**
- * Browser stub of `defineMcpDev`: returns the config bucket with no Node wiring.
- *
- * @param options - The MCP dev options.
- * @returns The (inert) blueprint.
- */
-export declare function defineMcpDev(options?: McpDevOptions): McpDevBlueprint;

package/dist/browser.js

@@ -1,37 +0,0 @@
-import { classDecoratorLegacyWrapper } from '@stone-js/core';
-
-/**
- * Browser stub of `@McpDev()`: a no-op.
- *
- * The dev MCP server (`stone mcp`) is a Node-only, development concern. Stubbing the decorator for
- * the browser keeps an isomorphic app compiling and inert there, without dragging the CLI command,
- * the MCP SDK server, or `node:fs` into the browser bundle (which would break a SPA). The real
- * decorator lives in the Node build.
- *
- * @param _options - Ignored in the browser.
- * @returns A no-op class decorator.
- */
-const McpDev = (_options = {}) => {
-    return classDecoratorLegacyWrapper((_target, _context) => { });
-};
-
-/**
- * Browser stub of the MCP dev blueprint.
- *
- * It carries the config bucket but wires **no** blueprint middleware, so importing it into a browser
- * bundle never pulls the Node-only `stone mcp` command, its server (`@modelcontextprotocol/sdk`,
- * stdio) or the filesystem. The `stone mcp` command is a development, Node-only concern; in the
- * browser this keeps the app compiling and inert.
- */
-const mcpDevBlueprint = { stone: { mcpDev: {} } };
-/**
- * Browser stub of `defineMcpDev`: returns the config bucket with no Node wiring.
- *
- * @param options - The MCP dev options.
- * @returns The (inert) blueprint.
- */
-function defineMcpDev(options = {}) {
-    return { stone: { mcpDev: options } };
-}
-
-export { McpDev, defineMcpDev, mcpDevBlueprint };

package/dist/decorators/McpDev.d.ts

@@ -1,24 +0,0 @@
-import { McpDevOptions } from '../declarations';
-import { ClassType } from '@stone-js/core';
-/**
- * Options for the `McpDev` decorator.
- */
-export interface McpDevDecoratorOptions extends McpDevOptions {
-}
-/**
- * A class decorator that adds the `stone mcp` command to your app.
- *
- * Declarative counterpart of registering {@link mcpDevBlueprint}: apply it to your app class to
- * expose the framework-knowledge tools (plus any you declare) to a coding agent over MCP.
- *
- * @param options - The MCP dev options (server name, instructions, your tools).
- * @returns A class decorator.
- *
- * @example
- * ```typescript
- * @McpDev({ tools: [myTool] })
- * @StoneApp({ name: 'my-app' })
- * export class Application {}
- * ```
- */
-export declare const McpDev: <T extends ClassType = ClassType>(options?: McpDevDecoratorOptions) => ClassDecorator;

package/dist/middleware/BlueprintMiddleware.d.ts

@@ -1,17 +0,0 @@
-import { BlueprintContext, IBlueprint, ClassType, MetaMiddleware, NextMiddleware } from '@stone-js/core';
-/**
- * Middleware that registers the `mcp` command when the app runs on the Node CLI adapter.
- *
- * It mirrors the router's command registration: contribute a `MetaCommandHandler` to
- * `stone.adapter.commands` so the CLI (itself a Stone.js app on the Node CLI adapter) discovers
- * `stone mcp` by introspection, no hard-coding.
- *
- * @param context - The blueprint context.
- * @param next - The next pipeline function.
- * @returns The updated blueprint.
- */
-export declare const SetMcpCommandsMiddleware: (context: BlueprintContext<IBlueprint, ClassType>, next: NextMiddleware<BlueprintContext<IBlueprint, ClassType>, IBlueprint>) => Promise<IBlueprint>;
-/**
- * The blueprint middleware contributed by the MCP dev module.
- */
-export declare const metaMcpDevBlueprintMiddleware: Array<MetaMiddleware<BlueprintContext<IBlueprint, ClassType>, IBlueprint>>;

package/dist/options/McpDevBlueprint.d.ts

@@ -1,34 +0,0 @@
-import { McpDevOptions } from '../declarations';
-import { AppConfig, StoneBlueprint } from '@stone-js/core';
-/**
- * MCP dev configuration bucket (`stone.mcpDev`).
- */
-export interface McpDevConfig extends McpDevOptions {
-}
-/**
- * Application config augmented with the MCP dev bucket.
- */
-export interface McpDevAppConfig extends Partial<AppConfig> {
-    mcpDev: Partial<McpDevConfig>;
-}
-/**
- * Blueprint for the MCP dev module.
- */
-export interface McpDevBlueprint extends StoneBlueprint {
-    stone: McpDevAppConfig;
-}
-/**
- * Opt-in blueprint: import and register it to add the `stone mcp` command.
- *
- * It contributes a blueprint middleware that registers the command on the Node CLI adapter. Add
- * your own tools and the server name/instructions under `stone.mcpDev` (or via `@McpDev()` /
- * `defineMcpDev()`).
- */
-export declare const mcpDevBlueprint: McpDevBlueprint;
-/**
- * Imperative helper: build an MCP dev blueprint with the given options.
- *
- * @param options - The MCP dev options (server name, instructions, your tools, report tools).
- * @returns The blueprint to register in your app.
- */
-export declare function defineMcpDev(options?: McpDevOptions): McpDevBlueprint;