@assistant-ui/mcp-docs-server 0.1.38 → 0.2.0

package/.docs/raw/docs/(reference)/api-reference/integrations/react-data-stream.mdx

@@ -0,0 +1,37 @@
+---
+title: "@assistant-ui/react-data-stream"
+description: Data stream runtime hook and message conversion utilities for custom assistant-ui streaming backends.
+---
+
+import { reactDataStream_toLanguageModelMessages, reactDataStream_useCloudRuntime, reactDataStream_useDataStreamRuntime } from "@/generated/integrationTypeDocs";
+
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
+
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
+
+## API Reference
+
+### useDataStreamRuntime
+
+<ParametersTable {...reactDataStream_useDataStreamRuntime} />
+
+### toLanguageModelMessages
+
+<Callout type="warn">
+<strong>Deprecated.</strong> Use `toGenericMessages` from `assistant-stream` for framework-agnostic conversion.
+This function is kept for AI SDK compatibility.
+</Callout>
+
+<ParametersTable {...reactDataStream_toLanguageModelMessages} />
+
+### useCloudRuntime
+
+<Callout type="warn">
+<strong>Deprecated.</strong> This is under active development and not yet ready for prod use.
+</Callout>
+
+<ParametersTable {...reactDataStream_useCloudRuntime} />
+{/* api-reference:end */}

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

@@ -3,7 +3,7 @@ title: Model Context
 description: Provide model instructions, contextual state, and inline renderers to assistant-ui runtimes.
 ---
 
-import { ModelContextProvider, useAssistantContext, useAssistantInstructions, useInlineRender, useThreadModelContext } from "@/generated/typeDocs";
+import { ModelContextProvider, useAssistantContext, useAssistantInstructions, useInlineRender } from "@/generated/typeDocs";
 
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
@@ -47,12 +47,4 @@ const ModelContextClient: Resource<ClientOutput<"modelContext">, []>;
 ### useInlineRender
 
 <ParametersTable {...useInlineRender} />
-
-### useThreadModelContext
-
-<Callout type="warn">
-<strong>Deprecated.</strong> Use [useAuiState](/docs/api-reference/hooks/state#useauistate): `useAuiState((s) => s.thread.modelContext)`. See the [migration guide](https://assistant-ui.com/docs/migrations/v0-12).
-</Callout>
-
-<ParametersTable {...useThreadModelContext} />
 {/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/overview.mdx

@@ -3,6 +3,7 @@ title: API Reference
 description: Complete assistant-ui React API reference for building AI chat UIs with primitives, hooks, runtimes, adapters, tools, transport, voice, and integrations.
 ---
 
+{/* api-reference:skip-auto-generation */}
 
 import { Component, ContextLevel } from "./context";
 

package/.docs/raw/docs/(reference)/api-reference/primitives/assistant-if.mdx

@@ -3,10 +3,12 @@ title: AuiIf
 description: Conditional rendering primitive for showing React UI from assistant-ui thread, message, composer, and runtime state.
 ---
 
-{/* api-reference:skip-auto-generation */}
+import { AuiIf } from "@/generated/typeDocs";
 
-{/* api-manual:start */}
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
 
+{/* api-manual:start */}
 ## Anatomy
 
 ```tsx
@@ -21,26 +23,6 @@ import { AuiIf } from "@assistant-ui/react";
 
 `AuiIf` is a generic conditional rendering component that provides access to the full assistant state. It replaces the deprecated `ThreadPrimitive.If`, `MessagePrimitive.If`, and `ComposerPrimitive.If` components with a single, flexible API.
 
-## API Reference
-
-<ParametersTable
-  type="AuiIfProps"
-  parameters={[
-    {
-      name: "condition",
-      type: "(state: AssistantState) => boolean",
-      required: true,
-      description:
-        "A function that receives the assistant state and returns whether to render children.",
-    },
-    {
-      name: "children",
-      type: "ReactNode",
-      description: "Content to render when the condition returns true.",
-    },
-  ]}
-/>
-
 ## AssistantState
 
 The condition function receives an `AssistantState` object with the following properties:
@@ -210,16 +192,17 @@ const isThreadEmpty: AuiIf.Condition = (s) => s.thread.isEmpty;
 | `<MessagePrimitive.If speaking>`       | `<AuiIf condition={(s) => s.message.speech != null}>`       |
 | `<MessagePrimitive.If last>`           | `<AuiIf condition={(s) => s.message.isLast}>`               |
 | `<ComposerPrimitive.If editing>`       | `<AuiIf condition={(s) => s.composer.isEditing}>`           |
+{/* api-manual:end */}
 
-## AssistantIf
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
 
-<Callout type="warn">
-  <strong>Deprecated:</strong> Use `AuiIf` instead. This alias was removed in
-  v0.13.
-</Callout>
+## API Reference
 
-```tsx
-import { AssistantIf } from "@assistant-ui/react";
-```
+### AuiIf
 
-{/* api-manual:end */}
+Renders `children` while `condition` selects `true` from the assistant state.
+
+<ParametersTable {...AuiIf} />
+{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/primitives/composition.mdx

@@ -3,6 +3,7 @@ title: Composition
 description: How to compose primitives with custom components using asChild.
 ---
 
+{/* api-reference:skip-auto-generation */}
 
 `assistant-ui` primitives are composable. This means that all props are forwarded, classes are merged, and event handlers are chained.
 

package/.docs/raw/docs/(reference)/api-reference/primitives/index.mdx

@@ -37,6 +37,9 @@ Primitives are the low-level React components behind assistant-ui interfaces. Th
   <Card title={"ComposerPrimitive"} href={"/docs/api-reference/primitives/composer"}>
     {"Composable input primitives for assistant-ui prompts, send controls, cancellation, attachments, and composer state."}
   </Card>
+  <Card title={"Composition"} href={"/docs/api-reference/primitives/composition"}>
+    {"How to compose primitives with custom components using asChild."}
+  </Card>
   <Card title={"ErrorPrimitive"} href={"/docs/api-reference/primitives/error"}>
     {"Error primitives for rendering assistant-ui runtime, thread, and message failures inside custom chat interfaces."}
   </Card>

package/.docs/raw/docs/(reference)/api-reference/primitives/selection-toolbar.mdx

@@ -32,6 +32,8 @@ Place this component inside `ThreadPrimitive.Root`:
   <FloatingSelectionToolbar />
 </ThreadPrimitive.Root>
 ```
+
+To prevent tool cards or other message UI from being quoted, wrap the message text in `data-aui-quote-selectable`. If a message contains that marker, the toolbar only appears for selections inside the same marked region. Set the attribute to `"false"` to exclude an element instead; on the message root it disables quoting for the whole message.
 {/* api-manual:end */}
 
 {/* api-reference:start */}

package/.docs/raw/docs/(reference)/api-reference/tools/status.mdx

@@ -3,8 +3,6 @@ title: Tool Status
 description: Read tool arguments, execution status, and result state inside assistant-ui tool UI components.
 ---
 
-
-
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
 

package/.docs/raw/docs/(reference)/api-reference/tools/toolkits.mdx

@@ -27,18 +27,18 @@ optional model-output conversion.
 
 This helper keeps reusable tool definitions type-checked and convenient to
 export for a [Toolkit](/docs/api-reference/tools/toolkits#toolkit) registered with [Tools](/docs/api-reference/tools/toolkits#tools).
-Inference from parameter schemas is currently limited, so provide generic
-arguments when you need precise args or result types.
+When `parameters` is a Standard Schema (for example Zod v4), its input type
+is inferred for `execute`, `streamCall`, and model-output callbacks. Plain
+JSON Schema objects do not carry TypeScript input types, so provide generic
+arguments or annotate callbacks when you need precise args for JSON Schema.
 
 ```ts
-const getWeather = tool<{ city: string }, string>({
+import { z } from "zod";
+
+const getWeather = tool({
   type: "frontend",
   description: "Get the weather for a city.",
-  parameters: {
-    type: "object",
-    properties: { city: { type: "string" } },
-    required: ["city"],
-  },
+  parameters: z.object({ city: z.string() }),
   execute: async ({ city }) => `Sunny in ${city}`,
 });
 ```
@@ -84,7 +84,10 @@ type Toolkit = Record<string, ToolDefinition<any, any>>;
 
 ### defineMcpToolkit
 
-Defines MCP server tools as a spreadable toolkit fragment.
+Defines MCP server tools as a spreadable toolkit fragment. Pass a raw
+`McpServerConfig` for always-on servers, or `{ server, disabled, tools }`
+when a server should stay configured but not expose all tools for the current
+request.
 
 <ParametersTable {...defineMcpToolkit} />
 

package/.docs/raw/docs/(reference)/api-reference/utilities/miscellaneous.mdx

@@ -63,6 +63,10 @@ Takes the current part state and a `smooth` argument: `false` disables,
 the reveal. Returns the part state with `text` replaced by the revealed
 prefix and `status` reporting `running` until the reveal catches up.
 
+The reveal auto-disables under `prefers-reduced-motion: reduce`,
+committing the full text immediately; this takes precedence over an
+explicit `smooth={true}`.
+
 ```tsx
 const { text, status } = useSmooth(useMessagePartText(), {
   drainMs: 500,

package/.docs/raw/docs/cloud/ai-sdk-assistant-ui.mdx

@@ -340,7 +340,7 @@ export function Chat() {
               name: "history",
               type: "ThreadHistoryAdapter",
               description:
-                "Adapter for loading and saving thread history. Used to restore previous messages when switching threads. The adapter must implement `withFormat` when used with AI SDK — see [Persisting Chat History](/docs/runtimes/ai-sdk/v6#persisting-chat-history).",
+                "Adapter for loading and saving thread history. Used to restore previous messages when switching threads. The adapter must implement `withFormat` when used with AI SDK — see [Persisting Chat History](/docs/runtimes/ai-sdk/v7#persisting-chat-history).",
             },
           ],
         },
@@ -358,6 +358,12 @@ export function Chat() {
       description:
         "Custom transport implementation. Defaults to AssistantChatTransport which sends requests to '/api/chat'.",
     },
+    {
+      name: "onResumeError",
+      type: "(error: unknown) => void",
+      description:
+        "Optional callback when useChatRuntime finds a pending resumable stream id but the automatic reconnect fails. Use it for a toast, telemetry, or retry UI; the stale stream id is still cleared.",
+    },
   ]}
 />
 

package/.docs/raw/docs/cloud/langgraph.mdx

@@ -6,7 +6,7 @@ description: Integrate cloud persistence and thread management with LangGraph Cl
 
 ## Overview
 
-This guide shows how to integrate Assistant Cloud with [LangGraph Cloud](https://langchain-ai.github.io/langgraph/cloud/) using assistant-ui's runtime system and pre-built UI components.
+This guide shows how to integrate Assistant Cloud with [LangGraph Cloud](https://docs.langchain.com/langsmith/deploy-to-cloud-overview) using assistant-ui's runtime system and pre-built UI components.
 
 ## Prerequisites
 
@@ -410,9 +410,11 @@ npx assistant-ui@latest add thread-list
   <Tab>
 
 ```sh
-npx shadcn@latest add https://r.assistant-ui.com/thread-list.json
+npx shadcn@latest add @assistant-ui/thread-list
 ```
 
+The `@assistant-ui` namespace resolves through the registry entry configured in [Manual Setup](/docs/installation#manual-setup).
+
   </Tab>
   <Tab>
 

package/.docs/raw/docs/copilots/model-context.mdx

@@ -112,7 +112,7 @@ function MyComponent() {
 
   useEffect(() => {
     // Register context provider
-    return aui.modelContext().register({
+    return aui.modelContext.register({
       getModelContext: () => ({
         system: "You are a helpful search assistant...",
         tools: { myTool },

package/.docs/raw/docs/copilots/motivation.mdx

@@ -158,7 +158,7 @@ function SmartTransactionHistory({ userProfile }) {
   const aui = useAui();
 
   useEffect(() => {
-    return aui.modelContext().register({
+    return aui.modelContext.register({
       getModelContext: () => ({
         system: `
           User spending patterns:

package/.docs/raw/docs/guides/attachments.mdx

@@ -503,14 +503,14 @@ Add attachments from external sources (URLs, API data, CMS references) without n
 const aui = useAui();
 
 // Add an attachment from an external source
-await aui.composer().addAttachment({
+await aui.composer.addAttachment({
   name: "report.pdf",
   contentType: "application/pdf",
   content: [{ type: "text", text: "Extracted document content..." }],
 });
 
 // Optionally provide id and type
-await aui.composer().addAttachment({
+await aui.composer.addAttachment({
   id: "cms-doc-123",
   type: "document",
   name: "Product Spec",
@@ -532,7 +532,7 @@ const handleMultipleFiles = async (files: FileList) => {
   const filesToAdd = Array.from(files).slice(0, maxFiles);
 
   for (const file of filesToAdd) {
-    await aui.composer().addAttachment(file);
+    await aui.composer.addAttachment(file);
   }
 };
 ```

package/.docs/raw/docs/guides/branching.mdx

@@ -54,7 +54,7 @@ const AssistantMessage = () => (
 
 ## Programmatic Branch Navigation
 
-For headless or keyboard-shortcut flows, navigate directly to a branch by id via `aui.message().switchToBranch`:
+For headless or keyboard-shortcut flows, navigate directly to a branch by id via `aui.message.switchToBranch`:
 
 ```tsx
 import { useAui } from "@assistant-ui/react";
@@ -62,7 +62,7 @@ import { useAui } from "@assistant-ui/react";
 const SwitchToBranch = ({ branchId }: { branchId: string }) => {
   const aui = useAui();
   return (
-    <button onClick={() => aui.message().switchToBranch({ branchId })}>
+    <button onClick={() => aui.message.switchToBranch({ branchId })}>
       Go to branch
     </button>
   );

package/.docs/raw/docs/guides/chatgpt-subscription.mdx

@@ -0,0 +1,108 @@
+---
+title: ChatGPT Subscription
+description: Run your assistant-ui app on your ChatGPT Plus or Pro subscription via Codex OAuth. Local development without an OpenAI API key.
+platforms: ["react"]
+---
+
+If you have a ChatGPT Plus or Pro subscription, you can run your assistant-ui app against it locally instead of paying per token with an API key. OpenAI's Codex CLI authenticates via OAuth and caches tokens on your machine; requests made with those tokens hit the Responses API endpoint at `chatgpt.com` and bill to your plan. The same mechanism powers Codex itself and a growing set of local agents.
+
+This is a personal-use setup for apps running on your own machine. For anything deployed or shared, use an API key.
+
+## Log in with Codex
+
+Authenticate once with the Codex CLI. The login flow runs OAuth in your browser and writes access and refresh tokens to `~/.codex/auth.json`:
+
+```sh
+npx @openai/codex login
+```
+
+Everything below reads that file; no environment variables or API keys are involved.
+
+## AI SDK route
+
+The community AI SDK provider [`openai-oauth-provider`](https://github.com/EvanZhouDev/openai-oauth) picks up `~/.codex/auth.json` automatically, refreshes tokens as needed, and supports streaming, tool calls, and reasoning traces.
+
+```sh
+npm install openai-oauth-provider
+```
+
+In your chat route, swap `@ai-sdk/openai` for the OAuth provider. Starting from the default assistant-ui template route, only the model changes; `frontendTools` and the UI message stream response work as before:
+
+```ts title="/app/api/chat/route.ts" {10}
+import { createOpenAIOAuth } from "openai-oauth-provider";
+import { frontendTools } from "@assistant-ui/react-ai-sdk";
+import {
+  type JSONSchema7,
+  streamText,
+  convertToModelMessages,
+  type UIMessage,
+} from "ai";
+
+const openai = createOpenAIOAuth();
+
+export async function POST(req: Request) {
+  const {
+    messages,
+    system,
+    tools,
+  }: {
+    messages: UIMessage[];
+    system?: string;
+    tools?: Record<string, { description?: string; parameters: JSONSchema7 }>;
+  } = await req.json();
+
+  const result = streamText({
+    model: openai("gpt-5.3-codex"),
+    messages: await convertToModelMessages(messages),
+    system,
+    tools: {
+      ...frontendTools(tools ?? {}),
+    },
+  });
+
+  return result.toUIMessageStreamResponse({
+    sendReasoning: true,
+  });
+}
+```
+
+The provider discovers which models your plan includes (for example `gpt-5.4` and `gpt-5.3-codex`) from your ChatGPT account.
+
+## Eve agents
+
+Eve's `defineAgent` accepts a provider-authored AI SDK `LanguageModel`, so the same provider drops into an eve agent config:
+
+```ts title="agent/agent.ts"
+import { defineAgent } from "eve";
+import { createOpenAIOAuth } from "openai-oauth-provider";
+
+export default defineAgent({
+  model: createOpenAIOAuth()("gpt-5.3-codex"),
+});
+```
+
+## OpenAI-compatible proxy
+
+For stacks that take an OpenAI base URL rather than an AI SDK model, the same project publishes a sibling package, `openai-oauth`, whose CLI runs a local proxy:
+
+```sh
+npx openai-oauth
+# OpenAI-compatible endpoint ready at http://127.0.0.1:10531/v1
+```
+
+Point any OpenAI-compatible client at that URL. No real API key is involved, but most clients require one at construction, so pass a placeholder:
+
+```ts
+import { OpenAI } from "openai";
+
+const openai = new OpenAI({
+  baseURL: "http://127.0.0.1:10531/v1",
+  apiKey: "unused",
+});
+```
+
+The proxy binds to `127.0.0.1` by default; keep it that way, since any caller that can reach the endpoint bills your subscription.
+
+<Callout type="warn">
+  Your OAuth tokens live in `~/.codex/auth.json`, so this only works where that file exists. A deployed instance would bill every visitor to your subscription. `openai-oauth-provider` is an unofficial community package, available models depend on your ChatGPT plan, and OpenAI sanctions this auth flow for Codex tooling, so treat it as personal use.
+</Callout>