@quilltap/plugin-types 1.7.0 → 1.8.1

package/CHANGELOG.md

@@ -5,6 +5,26 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.8.1] - 2026-01-14
+
+### Changed
+
+- **Breaking**: `getMultipleToolDefinitions` now accepts a `config` parameter
+  - Old signature: `getMultipleToolDefinitions?: () => UniversalTool[]`
+  - New signature: `getMultipleToolDefinitions?: (config: Record<string, unknown>) => UniversalTool[]`
+  - This allows multi-tool plugins to discover tools dynamically based on user configuration
+  - Required for plugins like MCP that need configuration to connect to external servers
+
+## [1.8.0] - 2026-01-13
+
+### Added
+
+- Multi-tool plugin support for `ToolPlugin` interface:
+  - `getMultipleToolDefinitions?: () => UniversalTool[]` - Allows plugins to provide multiple tools dynamically
+  - `executeByName?: (toolName, input, context) => Promise<ToolExecutionResult>` - Execute a specific tool by name (required for multi-tool plugins)
+  - `onConfigurationChange?: (config) => Promise<void>` - Callback when user configuration changes
+- These additions enable plugins like the MCP connector to discover and expose multiple tools from external servers
+
 ## [1.7.0] - 2026-01-09
 
 ### Added

package/dist/index.d.mts

@@ -175,6 +175,41 @@ interface ToolPlugin {
     renderIcon?: (props: {
         className?: string;
     }) => React.ReactNode;
+    /**
+     * Get multiple tool definitions (optional)
+     *
+     * For plugins that provide multiple tools dynamically (e.g., MCP connector).
+     * When implemented, the registry will call this at request time (not startup)
+     * to get the current list of tools based on configuration.
+     *
+     * This allows plugins to discover tools dynamically based on user config
+     * (e.g., MCP servers to connect to).
+     *
+     * @param config User configuration for this plugin
+     * @returns Array of tool definitions in universal format
+     */
+    getMultipleToolDefinitions?: (config: Record<string, unknown>) => UniversalTool[];
+    /**
+     * Execute a specific tool by name (optional)
+     *
+     * Required when getMultipleToolDefinitions is implemented.
+     * The registry routes execution to this method based on the tool name.
+     *
+     * @param toolName The name of the tool to execute (as returned by getMultipleToolDefinitions)
+     * @param input The input arguments from the LLM
+     * @param context Execution context with user/chat info and config
+     * @returns Promise resolving to the execution result
+     */
+    executeByName?: (toolName: string, input: Record<string, unknown>, context: ToolExecutionContext) => Promise<ToolExecutionResult>;
+    /**
+     * Called when configuration changes (optional)
+     *
+     * Allows plugins to refresh their state when user configuration changes.
+     * For multi-tool plugins, this may trigger re-discovery of available tools.
+     *
+     * @param config The updated user configuration
+     */
+    onConfigurationChange?: (config: Record<string, unknown>) => Promise<void>;
 }
 /**
  * Standard export type for tool plugins

package/dist/index.d.ts

@@ -175,6 +175,41 @@ interface ToolPlugin {
     renderIcon?: (props: {
         className?: string;
     }) => React.ReactNode;
+    /**
+     * Get multiple tool definitions (optional)
+     *
+     * For plugins that provide multiple tools dynamically (e.g., MCP connector).
+     * When implemented, the registry will call this at request time (not startup)
+     * to get the current list of tools based on configuration.
+     *
+     * This allows plugins to discover tools dynamically based on user config
+     * (e.g., MCP servers to connect to).
+     *
+     * @param config User configuration for this plugin
+     * @returns Array of tool definitions in universal format
+     */
+    getMultipleToolDefinitions?: (config: Record<string, unknown>) => UniversalTool[];
+    /**
+     * Execute a specific tool by name (optional)
+     *
+     * Required when getMultipleToolDefinitions is implemented.
+     * The registry routes execution to this method based on the tool name.
+     *
+     * @param toolName The name of the tool to execute (as returned by getMultipleToolDefinitions)
+     * @param input The input arguments from the LLM
+     * @param context Execution context with user/chat info and config
+     * @returns Promise resolving to the execution result
+     */
+    executeByName?: (toolName: string, input: Record<string, unknown>, context: ToolExecutionContext) => Promise<ToolExecutionResult>;
+    /**
+     * Called when configuration changes (optional)
+     *
+     * Allows plugins to refresh their state when user configuration changes.
+     * For multi-tool plugins, this may trigger re-discovery of available tools.
+     *
+     * @param config The updated user configuration
+     */
+    onConfigurationChange?: (config: Record<string, unknown>) => Promise<void>;
 }
 /**
  * Standard export type for tool plugins

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quilltap/plugin-types",
-  "version": "1.7.0",
+  "version": "1.8.1",
   "description": "Type definitions for Quilltap plugin development",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",