@assistant-ui/mcp-docs-server 0.1.34 → 0.1.36

package/.docs/raw/docs/(docs)/cli.mdx

@@ -56,8 +56,9 @@ This command scaffolds a project from assistant-ui starter templates or examples
 | `minimal` | Bare-bones starting point | `npx assistant-ui create -t minimal` |
 | `cloud` | Cloud-backed persistence starter | `npx assistant-ui create -t cloud` |
 | `cloud-clerk` | Cloud-backed starter with Clerk auth | `npx assistant-ui create -t cloud-clerk` |
-| `langgraph` | LangGraph starter template | `npx assistant-ui create -t langgraph` |
+| `langchain` | LangGraph starter with the react-langchain adapter | `npx assistant-ui create -t langchain` |
 | `mcp` | MCP starter template | `npx assistant-ui create -t mcp` |
+| `eve` | Eve agent + Next.js starter | `npx assistant-ui create -t eve` |
 
 **Available Examples**
 
@@ -66,6 +67,7 @@ Use `--example` to create a project from one of the monorepo examples with full
 | Example | Description | Command |
 |---------|-------------|---------|
 | `with-ai-sdk-v6` | Vercel AI SDK v6 integration | `npx assistant-ui create my-app -e with-ai-sdk-v6` |
+| `with-eve` | Eve agent integration | `npx assistant-ui create my-app -e with-eve` |
 | `with-artifacts` | HTML artifact rendering with live preview | `npx assistant-ui create my-app -e with-artifacts` |
 | `with-langgraph` | LangGraph agent with custom tools | `npx assistant-ui create my-app -e with-langgraph` |
 | `with-cloud` | Assistant Cloud persistence | `npx assistant-ui create my-app -e with-cloud` |
@@ -116,7 +118,7 @@ Arguments:
   project-directory         name of the project directory
 
 Options:
-  -t, --template <template>      template to use (default, minimal, cloud, cloud-clerk, langgraph, mcp)
+  -t, --template <template>      template to use (default, minimal, cloud, cloud-clerk, langchain, mcp, eve)
   -e, --example <example>        create from an example (e.g., with-langgraph)
   -p, --preset <name-or-url>     preset name or URL (e.g., chatgpt)
   --native                       create an Expo / React Native project

package/.docs/raw/docs/(docs)/devtools.mdx

@@ -43,9 +43,32 @@ export function AssistantApp() {
 
 ### Verify the DevTools overlay
 
-That's it! In development builds you should now see the DevTools in the lower-right corner of your site.
+That's it! In development builds you should now see the DevTools launcher in the lower-right corner of your site. The panel renders inline in an isolated shadow root, and the whole component is stripped from production builds.
 
-![DevTools floating modal anchored in the lower-right corner of a page](../../../../../.github/assets/devtoolsmodal.png)
+![DevTools floating launcher anchored in the lower-right corner of a page](../../../../../.github/assets/devtoolsmodal.png)
 
   </Step>
 </Steps>
+
+## Custom tabs
+
+The panel is extensible. Pass extra inspector tabs to `DevToolsModal` with `plugins`; each plugin renders from the inspected instance's projected data (`state`, `logs`, `modelContext`, `scopes`).
+
+```tsx
+import { createDevToolsPlugin, DevToolsModal } from "@assistant-ui/react-devtools";
+
+const stateTab = createDevToolsPlugin({
+  id: "my-state",
+  label: "My state",
+  Component: ({ data }) => <pre>{JSON.stringify(data.state, null, 2)}</pre>,
+});
+
+export function AssistantApp() {
+  return (
+    <AssistantRuntimeProvider runtime={runtime}>
+      <DevToolsModal plugins={[stateTab]} />
+      {/* ...your assistant-ui... */}
+    </AssistantRuntimeProvider>
+  );
+}
+```

package/.docs/raw/docs/(docs)/index.mdx

@@ -52,11 +52,14 @@ npx assistant-ui@latest create -t cloud
 # Assistant Cloud + Clerk authentication
 npx assistant-ui@latest create -t cloud-clerk
 
-# LangGraph starter template
-npx assistant-ui@latest create -t langgraph
+# LangGraph starter (react-langchain adapter)
+npx assistant-ui@latest create -t langchain
 
 # MCP starter template
 npx assistant-ui@latest create -t mcp
+
+# Eve agent starter template
+npx assistant-ui@latest create -t eve
 ```
 
 ## What's Next?

package/.docs/raw/docs/(docs)/installation.mdx

@@ -34,11 +34,14 @@ npx assistant-ui@latest create -t cloud
 # Assistant Cloud + Clerk authentication
 npx assistant-ui@latest create -t cloud-clerk
 
-# LangGraph starter template
-npx assistant-ui@latest create -t langgraph
+# LangGraph starter (react-langchain adapter)
+npx assistant-ui@latest create -t langchain
 
 # MCP starter template
 npx assistant-ui@latest create -t mcp
+
+# Eve agent starter template
+npx assistant-ui@latest create -t eve
 ```
 
 **Add to an existing project:**

package/.docs/raw/docs/(reference)/api-reference/external-store/message-conversion.mdx

@@ -14,39 +14,39 @@ import { useExternalMessageConverter } from "@/generated/typeDocs";
 
 ## API Reference
 
-### bindExternalStoreMessage
+### getExternalStoreMessages
 
-<Callout type="warn">
-<strong>Deprecated.</strong> This API is experimental and may change without notice.
-</Callout>
+```ts
+const getExternalStoreMessages: <T>(input: { messages: readonly ThreadMessage[]; } | ThreadMessage | ThreadMessage["content"][number]) => T[];
+```
 
-Attach the original external store message(s) to a ThreadMessage or message part.
-This is a no-op if the target already has a bound message.
-Use `getExternalStoreMessages` to retrieve the bound messages later.
+### unstable_convertExternalMessages
 
 ```ts
-const bindExternalStoreMessage: <T>(target: object, message: T | T[]) => void;
+const unstable_convertExternalMessages: <T extends WeakKey>(messages: T[], callback: useExternalMessageConverter.Callback<T>, isRunning: boolean, metadata: useExternalMessageConverter.Metadata) => ThreadMessage[];
 ```
 
-### getExternalStoreMessages
+### unstable_createMessageConverter
 
 ```ts
-const getExternalStoreMessages: <T>(input: { messages: readonly ThreadMessage[]; } | ThreadMessage | ThreadMessage["content"][number]) => T[];
+const unstable_createMessageConverter: <T extends object>(callback: useExternalMessageConverter.Callback<T>) => { useThreadMessages: ({ messages, isRunning, joinStrategy, metadata, }: { messages: T[]; isRunning: boolean; joinStrategy?: JoinStrategy | undefined; metadata?: useExternalMessageConverter.Metadata; }) => ThreadMessage[]; toThreadMessages: (messages: T[], isRunning?: boolean, metadata?: useExternalMessageConverter.Metadata) => ThreadMessage[]; toOriginalMessages: (input: ThreadState | ThreadMessage | ThreadMessage["content"][number]) => unknown[]; toOriginalMessage: (input: ThreadState | ThreadMessage | ThreadMessage["content"][number]) => {}; useOriginalMessage: () => {}; useOriginalMessages: () => unknown[]; };
 ```
 
 ### useExternalMessageConverter
 
 <ParametersTable {...useExternalMessageConverter} />
 
-### unstable_convertExternalMessages
+### bindExternalStoreMessage
 
-```ts
-const unstable_convertExternalMessages: <T extends WeakKey>(messages: T[], callback: useExternalMessageConverter.Callback<T>, isRunning: boolean, metadata: useExternalMessageConverter.Metadata) => ThreadMessage[];
-```
+<Callout type="tip">
+<strong>Experimental.</strong> This API is experimental and may change without notice.
+</Callout>
 
-### unstable_createMessageConverter
+Attach the original external store message(s) to a ThreadMessage or message part.
+This is a no-op if the target already has a bound message.
+Use `getExternalStoreMessages` to retrieve the bound messages later.
 
 ```ts
-const unstable_createMessageConverter: <T extends object>(callback: useExternalMessageConverter.Callback<T>) => { useThreadMessages: ({ messages, isRunning, joinStrategy, metadata, }: { messages: T[]; isRunning: boolean; joinStrategy?: JoinStrategy | undefined; metadata?: useExternalMessageConverter.Metadata; }) => ThreadMessage[]; toThreadMessages: (messages: T[], isRunning?: boolean, metadata?: useExternalMessageConverter.Metadata) => ThreadMessage[]; toOriginalMessages: (input: ThreadState | ThreadMessage | ThreadMessage["content"][number]) => unknown[]; toOriginalMessage: (input: ThreadState | ThreadMessage | ThreadMessage["content"][number]) => {}; useOriginalMessage: () => {}; useOriginalMessages: () => unknown[]; };
+const bindExternalStoreMessage: <T>(target: object, message: T | T[]) => void;
 ```
 {/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/hooks/composer-triggers.mdx

@@ -3,7 +3,7 @@ title: Composer Trigger Hooks
 description: Unstable assistant-ui hooks for mention menus, slash commands, and custom composer trigger popovers.
 ---
 
-import { unstable_useMentionAdapter, unstable_useSlashCommandAdapter } from "@/generated/typeDocs";
+import { unstable_useLiveCompletionAdapter, unstable_useMentionAdapter, unstable_useSlashCommandAdapter } from "@/generated/typeDocs";
 
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
@@ -14,47 +14,6 @@ import { unstable_useMentionAdapter, unstable_useSlashCommandAdapter } from "@/g
 
 ## API Reference
 
-### unstable_useMentionAdapter
-
-<Callout type="warn">
-<strong>Deprecated.</strong> Under active development and might change without notice.
-</Callout>
-
-Creates a spreadable `{ adapter, directive }` bundle for `@` mentions.
-Supports tools registered in model context, explicit items, or both —
-flat or categorized.
-
-```tsx
-const mention = unstable_useMentionAdapter();
-<ComposerTriggerPopover char="@" {...mention} />
-```
-
-<ParametersTable {...unstable_useMentionAdapter} />
-
-### unstable_useSlashCommandAdapter
-
-<Callout type="warn">
-<strong>Deprecated.</strong> Under active development and may change without notice.
-</Callout>
-
-Bundles slash command definitions (with inline `execute` callbacks) into
-`{adapter, action}` that plug directly into `ComposerTriggerPopover`.
-`execute` stays in the hook closure and is never attached to the returned
-`TriggerItem`, keeping items serializable.
-
-```tsx
-const slash = unstable_useSlashCommandAdapter({
-  commands: [
-    { id: "summarize", execute: () => runSummarize(), icon: "FileText" },
-    { id: "translate", execute: () => runTranslate(), icon: "Languages" },
-  ],
-});
-
-<ComposerTriggerPopover char="/" {...slash} />
-```
-
-<ParametersTable {...unstable_useSlashCommandAdapter} />
-
 ### unstable_useTriggerPopoverRootContext
 
 ```ts
@@ -95,4 +54,76 @@ Like `useTriggerPopoverTriggers` but returns an empty map outside a root.
 ```ts
 const unstable_useTriggerPopoverTriggersOptional: () => ReadonlyMap<string, RegisteredTrigger>;
 ```
+
+### unstable_useLiveCompletionAdapter
+
+<Callout type="tip">
+<strong>Experimental.</strong> Under active development and may change without notice.
+</Callout>
+
+Bridges an async completion source (a server search, a gateway RPC) into the
+synchronous `Unstable_TriggerAdapter` that `ComposerTriggerPopover` consumes.
+`search(query)` returns the last fetched items synchronously and schedules a
+debounced fetch when the query changes; when results arrive the returned
+`adapter` identity changes, which re-runs the popover's lookup so the fresh
+items render. This is a search-only adapter (`categories` are empty).
+
+`isLoading` is `true` while a fetch is in flight. Pass it to the popover's
+`isLoading` prop to render a loading state.
+
+```tsx
+const mentions = unstable_useLiveCompletionAdapter({
+  fetcher: (query) => searchUsers(query),
+});
+
+<ComposerTriggerPopover
+  char="@"
+  adapter={mentions.adapter}
+  isLoading={mentions.isLoading}
+  directive={{ onInserted }}
+/>
+```
+
+<ParametersTable {...unstable_useLiveCompletionAdapter} />
+
+### unstable_useMentionAdapter
+
+<Callout type="tip">
+<strong>Experimental.</strong> Under active development and might change without notice.
+</Callout>
+
+Creates a spreadable `{ adapter, directive }` bundle for `@` mentions.
+Supports tools registered in model context, explicit items, or both —
+flat or categorized.
+
+```tsx
+const mention = unstable_useMentionAdapter();
+<ComposerTriggerPopover char="@" {...mention} />
+```
+
+<ParametersTable {...unstable_useMentionAdapter} />
+
+### unstable_useSlashCommandAdapter
+
+<Callout type="tip">
+<strong>Experimental.</strong> Under active development and may change without notice.
+</Callout>
+
+Bundles slash command definitions (with inline `execute` callbacks) into
+`{adapter, action}` that plug directly into `ComposerTriggerPopover`.
+`execute` stays in the hook closure and is never attached to the returned
+`TriggerItem`, keeping items serializable.
+
+```tsx
+const slash = unstable_useSlashCommandAdapter({
+  commands: [
+    { id: "summarize", execute: () => runSummarize(), icon: "FileText" },
+    { id: "translate", execute: () => runTranslate(), icon: "Languages" },
+  ],
+});
+
+<ComposerTriggerPopover char="/" {...slash} />
+```
+
+<ParametersTable {...unstable_useSlashCommandAdapter} />
 {/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/hooks/model-context.mdx

@@ -3,7 +3,7 @@ title: Model Context Hooks
 description: React hooks for registering assistant-ui tools, data renderers, instructions, and model context providers.
 ---
 
-import { useAssistantInteractable, useAuiToolOverrides, useInteractableState } from "@/generated/typeDocs";
+import { useAuiToolOverrides } from "@/generated/typeDocs";
 
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
@@ -14,19 +14,10 @@ import { useAssistantInteractable, useAuiToolOverrides, useInteractableState } f
 
 ## API Reference
 
-### useAssistantInteractable
-
-Registers an interactable with the AI assistant.
-
-This hook handles registration only. To read and write the interactable's
-state, use [useInteractableState](/docs/api-reference/hooks/model-context#useinteractablestate) with the returned id.
-
-<ParametersTable {...useAssistantInteractable} />
-
 ### useAuiToolOverrides
 
-<Callout type="warn">
-<strong>Deprecated.</strong> Experimental, API may change.
+<Callout type="tip">
+<strong>Experimental.</strong> Experimental, API may change.
 </Callout>
 
 Overrides toolkit entries for the current assistant scope.
@@ -40,12 +31,4 @@ Overrides are registered at priority 1000, above toolkit defaults. Only one
 mounted override provider may define a given tool name at a time.
 
 <ParametersTable {...useAuiToolOverrides} />
-
-### useInteractableState
-
-Reads and writes the state of a registered interactable.
-
-Pair with [useAssistantInteractable](/docs/api-reference/hooks/model-context#useassistantinteractable) which handles registration.
-
-<ParametersTable {...useInteractableState} />
 {/* api-reference:end */}