@mcp-b/react-webmcp 4.1.0-beta.20260702224704 → 5.0.0

package/dist/index.d.ts

@@ -1,459 +1,177 @@
+import { InferOutput, InferToolInput, ToolExecutionState, WebMCPConfig, WebMCPReturn, WebMCPReturn as WebMCPReturn$1, useWebMCP } from "usewebmcp";
+import { ReactElement, ReactNode } from "react";
 import { ToolInputSchema, ToolInputSchema as ToolInputSchema$1 } from "@mcp-b/webmcp-polyfill/schema";
-import { DependencyList, ReactElement, ReactNode } from "react";
-import { BrowserMcpServer as ModelContextProtocol, Client, PromptDescriptor, PromptMessage, RequestOptions, Resource, ResourceContents, ResourceDescriptor, SamplingRequestParams, SamplingResult, ServerCapabilities, Tool, Transport } from "@mcp-b/webmcp-ts-sdk";
-import { CallToolResult, ElicitationParams, ElicitationResult, InferArgsFromInputSchema, InferJsonSchema, InputSchema, JsonSchemaForInference, ToolAnnotations, ToolDescriptor } from "@mcp-b/webmcp-types";
-import { z } from "zod";
+import { BrowserMcpServer as ModelContextProtocol, PromptDescriptor, PromptDescriptor as PromptDescriptor$1, ResourceDescriptor, ResourceDescriptor as ResourceDescriptor$1 } from "@mcp-b/webmcp-ts-sdk";
+import { Client, ConnectOptions, Resource, ServerCapabilities, Tool, Transport } from "@modelcontextprotocol/client";
+import { CallToolResult, MaybePromise, ToolAnnotations, ToolDescriptor } from "@mcp-b/webmcp-types";
 
-//#region src/zod-utils.d.ts
-type ZodSchemaObject = Record<string, z.ZodTypeAny>;
-type ZodSchema = ZodSchemaObject | z.ZodTypeAny;
-//#endregion
-//#region src/types.d.ts
-/**
- * Union of all input schema types supported by react-webmcp:
- * - `ToolInputSchema` (JSON Schema + Standard Schema v1)
- * - `ZodSchemaObject` (Zod v3 `Record<string, z.ZodTypeAny>`)
- */
-type ReactWebMCPInputSchema = ToolInputSchema$1 | ZodSchemaObject;
-/**
- * Union of all output schema types supported by react-webmcp:
- * - `JsonSchemaForInference` (MCP output schema)
- * - `ZodSchema` (converted to the inferable JSON Schema subset at runtime)
- */
-type ReactWebMCPOutputSchema = JsonSchemaForInference | ZodSchema;
-/**
- * Infers handler input type from a Standard Schema, Zod v3 schema, or JSON Schema.
- *
- * - **Standard Schema** (Zod v4, Valibot, ArkType): extracts `~standard.types.input`
- * - **Zod v3** (`Record<string, z.ZodTypeAny>`): uses `z.infer<z.ZodObject<T>>`
- * - **JSON Schema** (`as const`): uses `InferArgsFromInputSchema` for structural inference
- * - **Fallback**: `Record<string, unknown>`
- *
- * @template T - The input schema type
- * @internal
- */
-type InferToolInput<T> = T extends Record<string, z.ZodTypeAny> ? z.infer<z.ZodObject<T>> : T extends {
-  readonly '~standard': {
-    readonly types?: infer Types;
-  };
-} ? NonNullable<Types> extends {
-  readonly input: infer I;
-} ? I : Record<string, unknown> : T extends InputSchema ? InferArgsFromInputSchema<T> : Record<string, unknown>;
+//#region src/client/McpClientProvider.d.ts
 /**
- * Utility type to infer the output type from an output schema.
- *
- * - inferable JSON Schema resolves via `InferJsonSchema`
- * - `ZodSchemaObject` resolves via `z.infer<z.ZodObject<...>>`
- * - `undefined` falls back to `TFallback`
+ * Context value provided by McpClientProvider.
  *
- * @template TOutputSchema - Output schema for result inference
- * @template TFallback - Fallback type when no schema is provided
  * @internal
  */
-type InferOutput<TOutputSchema extends ReactWebMCPOutputSchema | undefined = undefined, TFallback = unknown> = TOutputSchema extends undefined ? TFallback : TOutputSchema extends z.ZodTypeAny ? z.infer<TOutputSchema> : TOutputSchema extends Record<string, z.ZodTypeAny> ? z.infer<z.ZodObject<TOutputSchema>> : TOutputSchema extends JsonSchemaForInference ? InferJsonSchema<TOutputSchema> : TFallback;
+interface McpClientContextValue {
+  client: Client;
+  tools: Tool[];
+  resources: Resource[];
+  isConnected: boolean;
+  isLoading: boolean;
+  error: Error | null;
+  capabilities: ServerCapabilities | null;
+  reconnect: (freshTransport?: Transport) => Promise<void>;
+}
 /**
- * Represents the current execution state of a tool, including loading status,
- * results, errors, and execution history.
+ * Props for the McpClientProvider component.
  *
- * @template TOutput - The type of data returned by the tool handler
  * @public
  */
-interface ToolExecutionState<TOutput = unknown> {
+interface McpClientProviderProps {
   /**
-   * Indicates whether the tool is currently executing.
-   * Use this to show loading states in your UI.
+   * React children to render within the provider.
    */
-  isExecuting: boolean;
+  children: ReactNode;
   /**
-   * The result from the most recent successful execution.
-   * Will be `null` if the tool hasn't been executed or last execution failed.
+   * MCP Client instance to use for communication.
    */
-  lastResult: TOutput | null;
+  client: Client;
   /**
-   * The error from the most recent failed execution.
-   * Will be `null` if the tool hasn't been executed or last execution succeeded.
+   * Transport instance for the client to connect through.
    */
-  error: Error | null;
+  transport: Transport;
   /**
-   * Total number of times this tool has been executed.
-   * Increments on successful executions only.
+   * Optional connection options.
    */
-  executionCount: number;
+  opts?: ConnectOptions;
 }
 /**
- * Configuration options for the `useWebMCP` hook.
+ * Provider component that manages an MCP client connection and exposes
+ * tools, resources, and connection state to child components.
  *
- * Defines a tool's metadata, schema, handler, and lifecycle callbacks.
+ * This provider handles:
+ * - Establishing and maintaining the MCP client connection
+ * - Fetching available tools and resources from the server
+ * - Listening for server notifications about tool/resource changes
+ * - Managing connection state and errors
+ * - Automatic cleanup on unmount
  *
- * @template TInputSchema - Schema defining input parameters
- * @template TOutputSchema - Output schema defining output structure
+ * @param props - Component props
+ * @returns Provider component wrapping children
  *
  * @public
  *
- * @example Basic tool without output schema:
- * ```typescript
- * const config: WebMCPConfig = {
- *   name: 'posts_like',
- *   description: 'Like a post by its ID',
- *   inputSchema: {
- *     type: 'object',
- *     properties: { postId: { type: 'string' } },
- *     required: ['postId'],
- *   } as const,
- *   handler: async ({ postId }) => {
- *     await api.likePost(postId);
- *     return { success: true };
- *   },
- * };
- * ```
- *
- * @example Tool with output schema (enables MCP structuredContent):
- * ```typescript
- * useWebMCP({
- *   name: 'posts_like',
- *   description: 'Like a post and return updated like count',
- *   inputSchema: {
- *     type: 'object',
- *     properties: { postId: { type: 'string' } },
- *     required: ['postId'],
- *   } as const,
- *   outputSchema: {
- *     type: 'object',
- *     properties: {
- *       likes: { type: 'number', description: 'Updated like count' },
- *       likedAt: { type: 'string', description: 'ISO timestamp of the like' },
- *     },
- *   } as const,
- *   handler: async ({ postId }) => {
- *     const result = await api.likePost(postId);
- *     return { likes: result.likes, likedAt: new Date().toISOString() };
- *   },
- * });
- * ```
- */
-interface WebMCPConfig<TInputSchema extends ReactWebMCPInputSchema = InputSchema, TOutputSchema extends ReactWebMCPOutputSchema | undefined = undefined> {
-  /**
-   * Unique identifier for the tool (e.g., 'posts_like', 'graph_navigate').
-   * Must follow naming conventions: lowercase with underscores.
-   */
-  name: string;
-  /**
-   * Human-readable description explaining what the tool does.
-   * This description is used by AI assistants to understand when to use the tool.
-   */
-  description: string;
-  /**
-   * Schema defining the input parameters for the tool.
-   * Use `as const` to enable type inference for the handler's input.
-   *
-   * @example
-   * ```typescript
-   * inputSchema: {
-   *   type: 'object',
-   *   properties: {
-   *     postId: { type: 'string', description: 'The ID of the post to like' },
-   *     userId: { type: 'string' },
-   *   },
-   *   required: ['postId'],
-   * } as const
-   * ```
-   */
-  inputSchema?: TInputSchema;
-  /**
-   * **Recommended:** Output schema defining the expected output structure.
-   * Accepts an inferable JSON Schema or a Zod schema that converts to one.
-   *
-   * When provided, this enables three key features:
-   * 1. **Type Safety**: The handler's return type is inferred from this schema
-   * 2. **MCP structuredContent**: The MCP response includes `structuredContent`
-   *    containing the typed output per the MCP specification
-   * 3. **AI Understanding**: AI models can better understand and use the tool's output
-   *
-   * @see {@link https://spec.modelcontextprotocol.io/specification/server/tools/#output-schemas}
-   *
-   * @example
-   * ```typescript
-   * outputSchema: {
-   *   type: 'object',
-   *   properties: {
-   *     counter: { type: 'number', description: 'The current counter value' },
-   *     timestamp: { type: 'string', description: 'ISO timestamp' },
-   *   },
-   * } as const
-   * ```
-   */
-  outputSchema?: TOutputSchema;
-  /**
-   * Optional metadata annotations providing hints about tool behavior.
-   * See {@link ToolAnnotations} for available options.
-   */
-  annotations?: ToolAnnotations;
-  /**
-   * The function that executes when the tool is called.
-   * Can be synchronous or asynchronous.
-   *
-   * When `outputSchema` is provided, the return type is inferred from the schema.
-   * Otherwise, any return type is allowed.
-   *
-   * @param input - Validated input parameters matching the inputSchema
-   * @returns The result data or a Promise resolving to the result
-   */
-  handler: (input: InferToolInput<TInputSchema>) => Promise<InferOutput<TOutputSchema>> | InferOutput<TOutputSchema>;
-  /**
-   * Custom formatter for the MCP text response.
-   *
-   * @deprecated Use `outputSchema` instead. The `outputSchema` provides type-safe
-   * structured output via MCP's `structuredContent`, which is the recommended
-   * approach for tool outputs. This property will be removed in a future version.
-   *
-   * @param output - The raw output from the handler
-   * @returns Formatted string for the MCP response content
-   */
-  formatOutput?: (output: InferOutput<TOutputSchema>) => string;
-  /**
-   * Optional callback invoked when the tool execution succeeds.
-   * Useful for triggering side effects like navigation or analytics.
-   *
-   * @param result - The successful result from the handler
-   * @param input - The input that was passed to the handler
-   */
-  onSuccess?: (result: InferOutput<TOutputSchema>, input: unknown) => void;
-  /**
-   * Optional callback invoked when the tool execution fails.
-   * Useful for error handling, logging, or showing user notifications.
-   *
-   * @param error - The error that occurred during execution
-   * @param input - The input that was passed to the handler
-   */
-  onError?: (error: Error, input: unknown) => void;
-}
-/**
- * Return value from the `useWebMCP` hook.
- * Provides access to execution state and methods for manual tool control.
+ * @example
+ * Connect to an MCP server via tab transport:
+ * ```tsx
+ * import { TabClientTransport } from '@mcp-b/transports';
+ * import { McpClientProvider } from '@mcp-b/react-webmcp';
+ * import { Client } from '@modelcontextprotocol/client';
  *
- * @template TOutputSchema - Output schema defining output structure
- * @public
- */
-interface WebMCPReturn<TOutputSchema extends ReactWebMCPOutputSchema | undefined = undefined, TInputSchema extends ReactWebMCPInputSchema = InputSchema> {
-  /**
-   * Current execution state including loading status, results, and errors.
-   * See {@link ToolExecutionState} for details.
-   */
-  state: ToolExecutionState<InferOutput<TOutputSchema>>;
-  /**
-   * Manually execute the tool with the provided input.
-   * Useful for testing, debugging, or triggering execution from your UI.
-   *
-   * @param input - The input parameters to pass to the tool
-   * @returns Promise resolving to the tool's output
-   * @throws Error if validation fails or handler throws
-   */
-  execute: (input: InferToolInput<TInputSchema>) => Promise<InferOutput<TOutputSchema>>;
-  /**
-   * Reset the execution state to its initial values.
-   * Clears results, errors, and resets the execution count.
-   */
-  reset: () => void;
-}
-/**
- * Configuration options for the `useWebMCPPrompt` hook.
- * Defines a prompt's metadata, argument schema, and message generator.
+ * const client = new Client(
+ *   { name: 'my-app', version: '1.0.0' },
+ *   { versionNegotiation: { mode: 'auto' } }
+ * );
  *
- * @template TArgsSchema - JSON Schema defining prompt arguments
- * @public
+ * const transport = new TabClientTransport({
+ *   channelId: 'mcp',
+ *   targetOrigin: window.location.origin,
+ * });
  *
- * @example
- * ```typescript
- * const config: WebMCPPromptConfig = {
- *   name: 'review_code',
- *   description: 'Review code for best practices',
- *   argsSchema: {
- *     type: 'object',
- *     properties: {
- *       code: { type: 'string', description: 'The code to review' },
- *       language: { type: 'string', description: 'Programming language' },
- *     },
- *     required: ['code'],
- *   } as const,
- *   get: async ({ code, language }) => ({
- *     messages: [{
- *       role: 'user',
- *       content: { type: 'text', text: `Review this ${language ?? ''} code:\n${code}` }
- *     }]
- *   }),
- * };
+ * function App() {
+ *   return (
+ *     <McpClientProvider client={client} transport={transport}>
+ *       <MyAppContent />
+ *     </McpClientProvider>
+ *   );
+ * }
  * ```
- */
-interface WebMCPPromptConfig<TArgsSchema extends ReactWebMCPInputSchema = InputSchema> {
-  /**
-   * Unique identifier for the prompt (e.g., 'review_code', 'summarize_text').
-   */
-  name: string;
-  /**
-   * Optional description explaining what the prompt does.
-   * This helps AI assistants understand when to use the prompt.
-   */
-  description?: string;
-  /**
-   * Optional JSON Schema defining the arguments for the prompt.
-   * Use `as const` to enable type inference for the `get` function's arguments.
-   */
-  argsSchema?: TArgsSchema;
-  /**
-   * Function that generates the prompt messages.
-   * Can be synchronous or asynchronous.
-   *
-   * @param args - Validated arguments matching the argsSchema
-   * @returns Object containing the prompt messages
-   */
-  get: (args: InferToolInput<TArgsSchema>) => Promise<{
-    messages: PromptMessage[];
-  }> | {
-    messages: PromptMessage[];
-  };
-}
-/**
- * Return value from the `useWebMCPPrompt` hook.
- * Indicates whether the prompt is registered.
  *
- * @public
- */
-interface WebMCPPromptReturn {
-  /**
-   * Whether the prompt is currently registered with the Model Context API.
-   */
-  isRegistered: boolean;
-}
-/**
- * Configuration options for the `useWebMCPResource` hook.
- * Defines a resource's metadata and read handler.
+ * @example
+ * Access tools from child components:
+ * ```tsx
+ * function MyAppContent() {
+ *   const { tools, isConnected, isLoading } = useMcpClient();
  *
- * @public
+ *   if (isLoading) {
+ *     return <div>Connecting to MCP server...</div>;
+ *   }
  *
- * @example Static resource
- * ```typescript
- * const config: WebMCPResourceConfig = {
- *   uri: 'config://app-settings',
- *   name: 'App Settings',
- *   description: 'Application configuration',
- *   mimeType: 'application/json',
- *   read: async (uri) => ({
- *     contents: [{ uri: uri.href, text: JSON.stringify(settings) }]
- *   }),
- * };
- * ```
+ *   if (!isConnected) {
+ *     return <div>Failed to connect to MCP server</div>;
+ *   }
  *
- * @example Dynamic resource with URI template
- * ```typescript
- * const config: WebMCPResourceConfig = {
- *   uri: 'user://{userId}/profile',
- *   name: 'User Profile',
- *   description: 'User profile data',
- *   read: async (uri, params) => ({
- *     contents: [{
- *       uri: uri.href,
- *       text: JSON.stringify(await fetchUser(params?.userId ?? ''))
- *     }]
- *   }),
- * };
+ *   return (
+ *     <div>
+ *       <h2>Available Tools:</h2>
+ *       <ul>
+ *         {tools.map(tool => (
+ *           <li key={tool.name}>{tool.description}</li>
+ *         ))}
+ *       </ul>
+ *     </div>
+ *   );
+ * }
  * ```
  */
-interface WebMCPResourceConfig {
-  /**
-   * The resource URI or URI template.
-   * - Static: "config://app-settings"
-   * - Template: "user://{userId}/profile" where {userId} becomes a parameter
-   */
-  uri: string;
-  /**
-   * Human-readable name for the resource.
-   */
-  name: string;
-  /**
-   * Optional description of what the resource provides.
-   */
-  description?: string;
-  /**
-   * Optional MIME type of the resource content.
-   */
-  mimeType?: string;
-  /**
-   * Function that reads and returns the resource content.
-   *
-   * @param uri - The resolved URI being requested
-   * @param params - Parameters extracted from URI template (if applicable)
-   * @returns Resource contents with the data
-   */
-  read: (uri: URL, params?: Record<string, string>) => Promise<{
-    contents: ResourceContents[];
-  }>;
-}
-/**
- * Return value from the `useWebMCPResource` hook.
- * Indicates whether the resource is registered.
- *
- * @public
- */
-interface WebMCPResourceReturn {
-  /**
-   * Whether the resource is currently registered with the Model Context API.
-   */
-  isRegistered: boolean;
-}
-//#endregion
-//#region src/useWebMCP.d.ts
+declare function McpClientProvider({
+  children,
+  client,
+  transport,
+  opts
+}: McpClientProviderProps): ReactElement;
 /**
- * React hook for registering and managing Model Context Protocol (MCP) tools.
- *
- * This hook handles the complete lifecycle of an MCP tool:
- * - Registers the tool with `window.document.modelContext`
- * - Manages execution state (loading, results, errors)
- * - Handles tool execution and lifecycle callbacks
- * - Automatically unregisters on component unmount
- * - Returns `structuredContent` when `outputSchema` is defined
+ * Hook to access the MCP client context.
+ * Must be used within an {@link McpClientProvider}.
  *
- * ## Output Schema (Recommended)
+ * @returns The MCP client context including client instance, tools, resources, and connection state
+ * @throws Error if used outside of McpClientProvider
  *
- * Always define an `outputSchema` for your tools. This provides:
- * - **Type Safety**: Handler return type is inferred from the schema
- * - **MCP structuredContent**: AI models receive structured, typed data
- * - **Better AI Understanding**: Models can reason about your tool's output format
+ * @public
  *
+ * @example
  * ```tsx
- * useWebMCP({
- *   name: 'get_user',
- *   description: 'Get user by ID',
- *   inputSchema: {
- *     type: 'object',
- *     properties: { userId: { type: 'string' } },
- *     required: ['userId'],
- *   } as const,
- *   outputSchema: {
- *     type: 'object',
- *     properties: {
- *       id: { type: 'string' },
- *       name: { type: 'string' },
- *       email: { type: 'string' },
- *     },
- *   } as const,
- *   handler: async ({ userId }) => {
- *     const user = await fetchUser(userId);
- *     return { id: user.id, name: user.name, email: user.email };
- *   },
- * });
- * ```
- *
- * @template TInputSchema - JSON Schema defining input parameter types (use `as const` for inference)
- * @template TOutputSchema - JSON Schema defining output structure
+ * function ToolsList() {
+ *   const { tools, isConnected, error, reconnect } = useMcpClient();
  *
- * @param config - Configuration object for the tool
- * @param deps - Optional dependency array that triggers tool re-registration when values change.
+ *   if (error) {
+ *     return (
+ *       <div>
+ *         Error: {error.message}
+ *         <button onClick={() => void reconnect()}>Retry</button>
+ *       </div>
+ *     );
+ *   }
  *
- * @returns Object containing execution state and control methods
+ *   if (!isConnected) {
+ *     return <div>Not connected</div>;
+ *   }
  *
- * @public
+ *   return (
+ *     <ul>
+ *       {tools.map(tool => (
+ *         <li key={tool.name}>{tool.description}</li>
+ *       ))}
+ *     </ul>
+ *   );
+ * }
+ * ```
  */
-declare function useWebMCP<TInputSchema extends ReactWebMCPInputSchema = InputSchema, TOutputSchema extends ReactWebMCPOutputSchema | undefined = undefined>(config: WebMCPConfig<TInputSchema, TOutputSchema>, deps?: DependencyList): WebMCPReturn<TOutputSchema, TInputSchema>;
+declare function useMcpClient(): McpClientContextValue;
+//#endregion
+//#region src/types.d.ts
+/** A single message returned by {@link WebMCPPromptConfig.get}. */
+type PromptMessage = Awaited<ReturnType<PromptDescriptor$1['get']>>['messages'][number];
+/** A single entry returned by {@link WebMCPResourceConfig.read}. */
+type ResourceContents = Awaited<ReturnType<ResourceDescriptor$1['read']>>['contents'][number];
+type WebMCPPromptConfig = Pick<PromptDescriptor$1, 'name' | 'description'> & {
+  argsSchema?: ToolInputSchema$1;
+  get: (args: Parameters<PromptDescriptor$1['get']>[0]) => MaybePromise<Awaited<ReturnType<PromptDescriptor$1['get']>>>;
+};
+interface WebMCPPromptReturn {
+  isRegistered: boolean;
+}
+type WebMCPResourceConfig = ResourceDescriptor$1;
+type WebMCPResourceReturn = WebMCPPromptReturn;
 //#endregion
 //#region src/useWebMCPContext.d.ts
 /**
@@ -464,9 +182,7 @@ declare function useWebMCP<TInputSchema extends ReactWebMCPInputSchema = InputSc
  * configures appropriate annotations (read-only, idempotent) and handles value
  * serialization.
  *
- * Note: This hook does not use an output schema, so the result will not include
- * `structuredContent` in the MCP response. Use {@link useWebMCP} directly with
- * `outputSchema` if you need structured output for MCP compliance.
+ * JSON-compatible values are normalized to text plus `structuredContent`.
  *
  * @template T - The type of context data to expose
  *
@@ -521,19 +237,16 @@ declare function useWebMCP<TInputSchema extends ReactWebMCPInputSchema = InputSc
  * }
  * ```
  */
-declare function useWebMCPContext<T>(name: string, description: string, getValue: () => T): WebMCPReturn;
+declare function useWebMCPContext<T>(name: string, description: string, getValue: () => T): WebMCPReturn$1;
 //#endregion
 //#region src/useWebMCPPrompt.d.ts
 /**
  * React hook for registering Model Context Protocol (MCP) prompts.
  *
  * This hook handles the complete lifecycle of an MCP prompt:
- * - Registers the prompt with `window.document.modelContext`
- * - Converts Zod schemas to JSON Schema for argument validation
+ * - Registers the prompt with the installed MCP-B `BrowserMcpServer`
  * - Automatically unregisters on component unmount
  *
- * @template TArgsSchema - Zod schema object defining argument types
- *
  * @param config - Configuration object for the prompt
  * @returns Object indicating registration status
  *
@@ -588,14 +301,14 @@ declare function useWebMCPContext<T>(name: string, description: string, getValue
  * }
  * ```
  */
-declare function useWebMCPPrompt<TArgsSchema extends ReactWebMCPInputSchema = InputSchema>(config: WebMCPPromptConfig<TArgsSchema>): WebMCPPromptReturn;
+declare function useWebMCPPrompt(config: WebMCPPromptConfig): WebMCPPromptReturn;
 //#endregion
 //#region src/useWebMCPResource.d.ts
 /**
  * React hook for registering Model Context Protocol (MCP) resources.
  *
  * This hook handles the complete lifecycle of an MCP resource:
- * - Registers the resource with `window.document.modelContext`
+ * - Registers the resource with the installed MCP-B `BrowserMcpServer`
  * - Supports both static URIs and URI templates with parameters
  * - Automatically unregisters on component unmount
  *
@@ -635,7 +348,7 @@ declare function useWebMCPPrompt<TArgsSchema extends ReactWebMCPInputSchema = In
  *     description: 'User profile data by ID',
  *     mimeType: 'application/json',
  *     read: async (uri, params) => {
- *       const userId = params?.userId ?? '';
+ *       const userId = typeof params?.userId === 'string' ? params.userId : '';
  *       const profile = await fetchUserProfile(userId);
  *       return {
  *         contents: [{
@@ -652,342 +365,27 @@ declare function useWebMCPPrompt<TArgsSchema extends ReactWebMCPInputSchema = In
  */
 declare function useWebMCPResource(config: WebMCPResourceConfig): WebMCPResourceReturn;
 //#endregion
-//#region src/useElicitationHandler.d.ts
-/**
- * State for elicitation requests, tracking the current request and results.
- */
-interface ElicitationState {
-  /** Whether an elicitation request is currently in progress */
-  isLoading: boolean;
-  /** The last elicitation result received */
-  result: ElicitationResult | null;
-  /** Any error that occurred during the last request */
-  error: Error | null;
-  /** Total number of requests made */
-  requestCount: number;
-}
-/**
- * Configuration options for the useElicitation hook.
- */
-interface UseElicitationConfig {
-  /**
-   * Optional callback invoked when an elicitation request completes successfully.
-   */
-  onSuccess?: (result: ElicitationResult) => void;
-  /**
-   * Optional callback invoked when an elicitation request fails.
-   */
-  onError?: (error: Error) => void;
-}
-/**
- * Return value from the useElicitation hook.
- */
-interface UseElicitationReturn {
-  /** Current state of elicitation */
-  state: ElicitationState;
-  /** Function to request user input from the connected client */
-  elicitInput: (params: ElicitationParams) => Promise<ElicitationResult>;
-  /** Reset the state */
-  reset: () => void;
-}
-/**
- * React hook for requesting user input from the connected MCP client.
- *
- * Elicitation allows the server (webpage) to request user input from the
- * connected client. This is useful when the page needs additional information
- * from the user, such as API keys, configuration options, or confirmations.
- *
- * There are two modes:
- * 1. **Form mode**: For non-sensitive data collection using a schema-driven form.
- * 2. **URL mode**: For sensitive data collection via a web URL (API keys, OAuth, etc.).
- *
- * @param config - Optional configuration including callbacks
- * @returns Object containing state and the elicitInput function
- *
- * @example Form elicitation:
- * ```tsx
- * function ConfigForm() {
- *   const { state, elicitInput } = useElicitation({
- *     onSuccess: (result) => console.log('Got input:', result),
- *     onError: (error) => console.error('Elicitation failed:', error),
- *   });
- *
- *   const handleConfigure = async () => {
- *     const result = await elicitInput({
- *       message: 'Please provide your configuration',
- *       requestedSchema: {
- *         type: 'object',
- *         properties: {
- *           apiKey: { type: 'string', title: 'API Key', description: 'Your API key' },
- *           model: { type: 'string', enum: ['gpt-4', 'gpt-3.5'], title: 'Model' }
- *         },
- *         required: ['apiKey']
- *       }
- *     });
- *
- *     if (result.action === 'accept') {
- *       console.log('Config:', result.content);
- *     }
- *   };
- *
- *   return (
- *     <button onClick={handleConfigure} disabled={state.isLoading}>
- *       Configure
- *     </button>
- *   );
- * }
- * ```
- *
- * @example URL elicitation (for sensitive data):
- * ```tsx
- * const { elicitInput } = useElicitation();
- *
- * const handleOAuth = async () => {
- *   const result = await elicitInput({
- *     mode: 'url',
- *     message: 'Please authenticate with GitHub',
- *     elicitationId: 'github-oauth-123',
- *     url: 'https://github.com/login/oauth/authorize?client_id=...'
- *   });
- *
- *   if (result.action === 'accept') {
- *     console.log('OAuth completed');
- *   }
- * };
- * ```
- */
-declare function useElicitation(config?: UseElicitationConfig): UseElicitationReturn;
-//#endregion
-//#region src/useSamplingHandler.d.ts
-/**
- * State for sampling requests, tracking the current request and results.
- */
-interface SamplingState {
-  /** Whether a sampling request is currently in progress */
-  isLoading: boolean;
-  /** The last sampling result received */
-  result: SamplingResult | null;
-  /** Any error that occurred during the last request */
-  error: Error | null;
-  /** Total number of requests made */
-  requestCount: number;
-}
-/**
- * Configuration options for the useSampling hook.
- */
-interface UseSamplingConfig {
-  /**
-   * Optional callback invoked when a sampling request completes successfully.
-   */
-  onSuccess?: (result: SamplingResult) => void;
-  /**
-   * Optional callback invoked when a sampling request fails.
-   */
-  onError?: (error: Error) => void;
-}
-/**
- * Return value from the useSampling hook.
- */
-interface UseSamplingReturn {
-  /** Current state of sampling */
-  state: SamplingState;
-  /** Function to request LLM completion from the connected client */
-  createMessage: (params: SamplingRequestParams) => Promise<SamplingResult>;
-  /** Reset the state */
-  reset: () => void;
-}
-/**
- * React hook for requesting LLM completions from the connected MCP client.
- *
- * Sampling allows the server (webpage) to request LLM completions from the
- * connected client. This is useful when the page needs AI capabilities like
- * summarization, generation, or analysis.
- *
- * @param config - Optional configuration including callbacks
- * @returns Object containing state and the createMessage function
- *
- * @example Basic usage:
- * ```tsx
- * function AIAssistant() {
- *   const { state, createMessage } = useSampling({
- *     onSuccess: (result) => console.log('Got response:', result),
- *     onError: (error) => console.error('Sampling failed:', error),
- *   });
- *
- *   const handleAsk = async () => {
- *     const result = await createMessage({
- *       messages: [
- *         { role: 'user', content: { type: 'text', text: 'What is 2+2?' } }
- *       ],
- *       maxTokens: 100,
- *     });
- *     console.log(result.content);
- *   };
- *
- *   return (
- *     <div>
- *       <button onClick={handleAsk} disabled={state.isLoading}>
- *         Ask AI
- *       </button>
- *       {state.result && <p>{JSON.stringify(state.result.content)}</p>}
- *     </div>
- *   );
- * }
- * ```
- */
-declare function useSampling(config?: UseSamplingConfig): UseSamplingReturn;
-//#endregion
-//#region src/client/McpClientProvider.d.ts
-/**
- * Context value provided by McpClientProvider.
- *
- * @internal
- */
-interface McpClientContextValue {
-  client: Client;
-  tools: Tool[];
-  resources: Resource[];
-  isConnected: boolean;
-  isLoading: boolean;
-  error: Error | null;
-  capabilities: ServerCapabilities | null;
-  reconnect: () => Promise<void>;
-}
-/**
- * Props for the McpClientProvider component.
- *
- * @public
- */
-interface McpClientProviderProps {
-  /**
-   * React children to render within the provider.
-   */
-  children: ReactNode;
-  /**
-   * MCP Client instance to use for communication.
-   */
-  client: Client;
-  /**
-   * Transport instance for the client to connect through.
-   */
-  transport: Transport;
-  /**
-   * Optional request options for the connection.
-   */
-  opts?: RequestOptions;
+//#region src/index.d.ts
+declare module 'react' {
+  interface FormHTMLAttributes<T> {
+    toolname?: string;
+    tooltitle?: string;
+    tooldescription?: string;
+    toolautosubmit?: '' | 'toolautosubmit';
+  }
+  interface FieldsetHTMLAttributes<T> {
+    toolparamdescription?: string;
+  }
+  interface InputHTMLAttributes<T> {
+    toolparamdescription?: string;
+  }
+  interface SelectHTMLAttributes<T> {
+    toolparamdescription?: string;
+  }
+  interface TextareaHTMLAttributes<T> {
+    toolparamdescription?: string;
+  }
 }
-/**
- * Provider component that manages an MCP client connection and exposes
- * tools, resources, and connection state to child components.
- *
- * This provider handles:
- * - Establishing and maintaining the MCP client connection
- * - Fetching available tools and resources from the server
- * - Listening for server notifications about tool/resource changes
- * - Managing connection state and errors
- * - Automatic cleanup on unmount
- *
- * @param props - Component props
- * @returns Provider component wrapping children
- *
- * @public
- *
- * @example
- * Connect to an MCP server via tab transport:
- * ```tsx
- * import { Client } from '@modelcontextprotocol/sdk/client/index.js';
- * import { TabClientTransport } from '@mcp-b/transports';
- * import { McpClientProvider } from '@mcp-b/react-webmcp';
- *
- * const client = new Client(
- *   { name: 'my-app', version: '1.0.0' },
- *   { capabilities: {} }
- * );
- *
- * const transport = new TabClientTransport('mcp', {
- *   clientInstanceId: 'my-app-instance',
- * });
- *
- * function App() {
- *   return (
- *     <McpClientProvider client={client} transport={transport}>
- *       <MyAppContent />
- *     </McpClientProvider>
- *   );
- * }
- * ```
- *
- * @example
- * Access tools from child components:
- * ```tsx
- * function MyAppContent() {
- *   const { tools, isConnected, isLoading } = useMcpClient();
- *
- *   if (isLoading) {
- *     return <div>Connecting to MCP server...</div>;
- *   }
- *
- *   if (!isConnected) {
- *     return <div>Failed to connect to MCP server</div>;
- *   }
- *
- *   return (
- *     <div>
- *       <h2>Available Tools:</h2>
- *       <ul>
- *         {tools.map(tool => (
- *           <li key={tool.name}>{tool.description}</li>
- *         ))}
- *       </ul>
- *     </div>
- *   );
- * }
- * ```
- */
-declare function McpClientProvider({
-  children,
-  client,
-  transport,
-  opts
-}: McpClientProviderProps): ReactElement;
-/**
- * Hook to access the MCP client context.
- * Must be used within an {@link McpClientProvider}.
- *
- * @returns The MCP client context including client instance, tools, resources, and connection state
- * @throws Error if used outside of McpClientProvider
- *
- * @public
- *
- * @example
- * ```tsx
- * function ToolsList() {
- *   const { tools, isConnected, error, reconnect } = useMcpClient();
- *
- *   if (error) {
- *     return (
- *       <div>
- *         Error: {error.message}
- *         <button onClick={reconnect}>Retry</button>
- *       </div>
- *     );
- *   }
- *
- *   if (!isConnected) {
- *     return <div>Not connected</div>;
- *   }
- *
- *   return (
- *     <ul>
- *       {tools.map(tool => (
- *         <li key={tool.name}>{tool.description}</li>
- *       ))}
- *     </ul>
- *   );
- * }
- * ```
- */
-declare function useMcpClient(): McpClientContextValue;
 //#endregion
-export { type CallToolResult, type ElicitationState as ElicitationHandlerState, type ElicitationState, type InferOutput, type InferToolInput, McpClientProvider, type McpClientProviderProps, type ModelContextProtocol, type PromptDescriptor, type PromptMessage, type ReactWebMCPInputSchema, type ResourceContents, type ResourceDescriptor, type SamplingState as SamplingHandlerState, type SamplingState, type ToolAnnotations, type ToolDescriptor, type ToolExecutionState, type ToolInputSchema, type UseElicitationConfig, type UseElicitationConfig as UseElicitationHandlerConfig, type UseElicitationReturn as UseElicitationHandlerReturn, type UseElicitationReturn, type UseSamplingConfig, type UseSamplingConfig as UseSamplingHandlerConfig, type UseSamplingReturn as UseSamplingHandlerReturn, type UseSamplingReturn, type WebMCPConfig, type WebMCPPromptConfig, type WebMCPPromptReturn, type WebMCPResourceConfig, type WebMCPResourceReturn, type WebMCPReturn, type ZodSchema, type ZodSchemaObject, useElicitation, useElicitation as useElicitationHandler, useMcpClient, useSampling, useSampling as useSamplingHandler, useWebMCP, useWebMCPContext, useWebMCPPrompt, useWebMCPResource };
+export { type CallToolResult, type InferOutput, type InferToolInput, McpClientProvider, type McpClientProviderProps, type ModelContextProtocol, type PromptDescriptor, type PromptMessage, type ResourceContents, type ResourceDescriptor, type ToolAnnotations, type ToolDescriptor, type ToolExecutionState, type ToolInputSchema, type WebMCPConfig, type WebMCPPromptConfig, type WebMCPPromptReturn, type WebMCPResourceConfig, type WebMCPResourceReturn, type WebMCPReturn, useMcpClient, useWebMCP, useWebMCPContext, useWebMCPPrompt, useWebMCPResource };
 //# sourceMappingURL=index.d.ts.map