@quilltap/plugin-types 1.8.0 → 1.8.1

package/CHANGELOG.md

@@ -5,6 +5,16 @@ 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

package/dist/index.d.mts

@@ -179,12 +179,16 @@ interface ToolPlugin {
      * Get multiple tool definitions (optional)
      *
      * For plugins that provide multiple tools dynamically (e.g., MCP connector).
-     * When implemented, the registry will call this instead of getToolDefinition()
-     * and register each returned tool separately.
+     * 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?: () => UniversalTool[];
+    getMultipleToolDefinitions?: (config: Record<string, unknown>) => UniversalTool[];
     /**
      * Execute a specific tool by name (optional)
      *

package/dist/index.d.ts

@@ -179,12 +179,16 @@ interface ToolPlugin {
      * Get multiple tool definitions (optional)
      *
      * For plugins that provide multiple tools dynamically (e.g., MCP connector).
-     * When implemented, the registry will call this instead of getToolDefinition()
-     * and register each returned tool separately.
+     * 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?: () => UniversalTool[];
+    getMultipleToolDefinitions?: (config: Record<string, unknown>) => UniversalTool[];
     /**
      * Execute a specific tool by name (optional)
      *

package/package.json

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