@assistant-ui/mcp-docs-server 0.1.8 → 0.1.10

package/.docs/raw/docs/runtimes/mastra/full-stack-integration.mdx

@@ -10,9 +10,9 @@ Integrate Mastra directly into your Next.js application's API routes. This appro
 <Steps>
 <Step>
 
-### Initialize Assistant UI
+### Initialize assistant-ui
 
-Start by setting up Assistant UI in your project. Run one of the following commands:
+Start by setting up assistant-ui in your project. Run one of the following commands:
 
 ```sh title="New Project"
 npx assistant-ui@latest create
@@ -190,10 +190,11 @@ export async function POST(req: Request) {
 ```
 
 Key changes:
+
 - We import the `mastra` instance created in `mastra/index.ts`. Make sure the import path (`@/mastra`) is correct for your project setup (you might need `~/mastra`, `../../../mastra`, etc., depending on your path aliases and project structure).
 - We retrieve the `chefAgent` using `mastra.getAgent("chefAgent")`.
 - Instead of calling the AI SDK's `streamText` directly, we call `agent.stream(messages)` to process the chat messages using the agent's configuration and model.
-- The result is still returned in a format compatible with Assistant UI using `toDataStreamResponse()`.
+- The result is still returned in a format compatible with assistant-ui using `toDataStreamResponse()`.
 
 Your API route is now powered by Mastra!
 
@@ -208,11 +209,11 @@ You're all set! Start your Next.js development server:
 npm run dev
 ```
 
-Open your browser to `http://localhost:3000` (or the port specified in your terminal). You should now be able to interact with your `chefAgent` through the Assistant UI chat interface. Ask it for cooking advice based on ingredients you have!
+Open your browser to `http://localhost:3000` (or the port specified in your terminal). You should now be able to interact with your `chefAgent` through the assistant-ui chat interface. Ask it for cooking advice based on ingredients you have!
 
 </Step>
 </Steps>
 
-Congratulations! You have successfully integrated Mastra into your Next.js application using the full-stack approach. Your Assistant UI frontend now communicates with a Mastra agent running in your Next.js backend API route.
+Congratulations! You have successfully integrated Mastra into your Next.js application using the full-stack approach. Your assistant-ui frontend now communicates with a Mastra agent running in your Next.js backend API route.
 
 To explore more advanced Mastra features like memory, tools, workflows, and more, please refer to the [official Mastra documentation](https://mastra.ai/docs).

package/.docs/raw/docs/runtimes/mastra/overview.mdx

@@ -4,9 +4,9 @@ title: Overview
 
 Mastra is an open-source TypeScript agent framework designed to provide the essential primitives for building AI applications. It enables developers to create AI agents with memory and tool-calling capabilities, implement deterministic LLM workflows, and leverage RAG for knowledge integration. With features like model routing, workflow graphs, and automated evals, Mastra provides a complete toolkit for developing, testing, and deploying AI applications.
 
-## Integrating with Next.js and Assistant UI
+## Integrating with Next.js and assistant-ui
 
-There are two primary ways to integrate Mastra into your Next.js project when using Assistant UI:
+There are two primary ways to integrate Mastra into your Next.js project when using assistant-ui:
 
 1.  **Full-Stack Integration**: Integrate Mastra directly into your Next.js application's API routes. This approach keeps your backend and frontend code within the same project.
     [Learn how to set up Full-Stack Integration](./full-stack-integration)
@@ -14,4 +14,4 @@ There are two primary ways to integrate Mastra into your Next.js project when us
 2.  **Separate Server Integration**: Run Mastra as a standalone server and connect your Next.js frontend to its API endpoints. This approach separates concerns and allows for independent scaling.
     [Learn how to set up Separate Server Integration](./separate-server-integration)
 
-Choose the guide that best fits your project architecture. Both methods allow seamless integration with the Assistant UI components.
+Choose the guide that best fits your project architecture. Both methods allow seamless integration with the assistant-ui components.

package/.docs/raw/docs/runtimes/mastra/separate-server-integration.mdx

@@ -5,7 +5,7 @@ title: Separate Server Integration
 import { Step, Steps } from "fumadocs-ui/components/steps";
 import { Callout } from "fumadocs-ui/components/callout";
 
-Run Mastra as a standalone server and connect your Next.js frontend (using Assistant UI) to its API endpoints. This approach separates your AI backend from your frontend application, allowing for independent development and scaling.
+Run Mastra as a standalone server and connect your Next.js frontend (using assistant-ui) to its API endpoints. This approach separates your AI backend from your frontend application, allowing for independent development and scaling.
 
 <Steps>
 
@@ -13,7 +13,7 @@ Run Mastra as a standalone server and connect your Next.js frontend (using Assis
 
 ### Create Mastra Server Project
 
-First, create a dedicated project for your Mastra server. Choose a directory separate from your Next.js/Assistant UI frontend project.
+First, create a dedicated project for your Mastra server. Choose a directory separate from your Next.js/assistant-ui frontend project.
 
 Navigate to your chosen parent directory in the terminal and run the Mastra create command:
 
@@ -97,15 +97,15 @@ With the agent defined and registered, start the Mastra development server:
 npm run dev
 ```
 
-By default, the Mastra server will run on `http://localhost:4111`. Your `chefAgent` should now be accessible via a POST request endpoint, typically `http://localhost:4111/api/agents/chefAgent/stream`. Keep this server running for the next steps where we'll set up the Assistant UI frontend to connect to it.
+By default, the Mastra server will run on `http://localhost:4111`. Your `chefAgent` should now be accessible via a POST request endpoint, typically `http://localhost:4111/api/agents/chefAgent/stream`. Keep this server running for the next steps where we'll set up the assistant-ui frontend to connect to it.
 
 </Step>
 
 <Step>
 
-### Initialize Assistant UI Frontend
+### Initialize assistant-ui Frontend
 
-Now, set up your frontend application using Assistant UI. Navigate to a **different directory** from your Mastra server project. You can either create a new Next.js project or use an existing one.
+Now, set up your frontend application using assistant-ui. Navigate to a **different directory** from your Mastra server project. You can either create a new Next.js project or use an existing one.
 
 Inside your frontend project directory, run one of the following commands:
 
@@ -117,10 +117,10 @@ npx assistant-ui@latest create
 npx assistant-ui@latest init
 ```
 
-This command installs the necessary Assistant UI dependencies and sets up basic configuration files, including a default chat page and an API route (`app/api/chat/route.ts`).
+This command installs the necessary assistant-ui dependencies and sets up basic configuration files, including a default chat page and an API route (`app/api/chat/route.ts`).
 
 <Callout title="Need Help?">
-  For detailed setup instructions for Assistant UI, including manual setup
+  For detailed setup instructions for assistant-ui, including manual setup
   steps, please refer to the main [Getting Started
   guide](/docs/getting-started).
 </Callout>
@@ -133,9 +133,9 @@ In the next step, we will configure this frontend to communicate with the separa
 
 ### Configure Frontend API Endpoint
 
-The default Assistant UI setup configures the chat runtime to use a local API route (`/api/chat`) within the Next.js project. Since our Mastra agent is running on a separate server, we need to update the frontend to point to that server's endpoint.
+The default assistant-ui setup configures the chat runtime to use a local API route (`/api/chat`) within the Next.js project. Since our Mastra agent is running on a separate server, we need to update the frontend to point to that server's endpoint.
 
-Open the main page file in your Assistant UI frontend project (usually `app/page.tsx` or `src/app/page.tsx`). Find the `useChatRuntime` hook and change the `api` property to the full URL of your Mastra agent's stream endpoint:
+Open the main page file in your assistant-ui frontend project (usually `app/page.tsx` or `src/app/page.tsx`). Find the `useChatRuntime` hook and change the `api` property to the full URL of your Mastra agent's stream endpoint:
 
 ```tsx {10} title="app/page.tsx"
 "use client";
@@ -163,7 +163,7 @@ export default function Home() {
 
 Replace `"http://localhost:4111/api/agents/chefAgent/stream"` with the actual URL if your Mastra server runs on a different port or host, or if your agent has a different name.
 
-Now, the Assistant UI frontend will send chat requests directly to your running Mastra server.
+Now, the assistant-ui frontend will send chat requests directly to your running Mastra server.
 
 <Callout title="Delete Default API Route">
   Since the frontend no longer uses the local `/api/chat` route created by the
@@ -179,18 +179,18 @@ Now, the Assistant UI frontend will send chat requests directly to your running
 
 You're ready to connect the pieces! Make sure your separate Mastra server is still running (from Step 4).
 
-In your Assistant UI frontend project directory, start the Next.js development server:
+In your assistant-ui frontend project directory, start the Next.js development server:
 
 ```bash npm2yarn
 npm run dev
 ```
 
-Open your browser to `http://localhost:3000` (or the port specified in your terminal for the frontend app). You should now be able to interact with your `chefAgent` through the Assistant UI chat interface. The frontend will make requests to your Mastra server running on `http://localhost:4111`.
+Open your browser to `http://localhost:3000` (or the port specified in your terminal for the frontend app). You should now be able to interact with your `chefAgent` through the assistant-ui chat interface. The frontend will make requests to your Mastra server running on `http://localhost:4111`.
 
 </Step>
 
 </Steps>
 
-Congratulations! You have successfully integrated Mastra with Assistant UI using a separate server approach. Your Assistant UI frontend now communicates with a standalone Mastra agent server.
+Congratulations! You have successfully integrated Mastra with assistant-ui using a separate server approach. Your assistant-ui frontend now communicates with a standalone Mastra agent server.
 
 This setup provides a clear separation between your frontend and AI backend. To explore more advanced Mastra features like memory, tools, workflows, and deployment options, please refer to the [official Mastra documentation](https://mastra.ai/docs).

package/.docs/raw/docs/ui/Thread.mdx

@@ -4,26 +4,64 @@ title: Thread
 
 import { Steps, Step } from "fumadocs-ui/components/steps";
 import { Callout } from "fumadocs-ui/components/callout";
+import { Tab, Tabs } from "fumadocs-ui/components/tabs";
+import { ParametersTable } from "@/components/docs";
 import { ThreadSample } from "../../../components/samples/thread-sample";
 
+A complete chat interface that combines message rendering, auto-scrolling, composer input,
+attachments, and conditional UI states. Fully customizable and composable.
 
-## Overview
-
-The raw message list and message composer UI.
 
 <ThreadSample />
 
+## Anatomy
+
+The Thread component is built with the following primitives:
+
+```tsx
+import { ThreadPrimitive } from "@assistant-ui/react";
+
+<ThreadPrimitive.Root>
+  <ThreadPrimitive.Viewport>
+    <ThreadPrimitive.Empty />
+    <ThreadPrimitive.Messages
+      components={{
+        EditComposer,
+        UserMessage, 
+        AssistantMessage,
+      }}
+    />
+    <ThreadPrimitive.ScrollToBottom />
+  </ThreadPrimitive.Viewport>
+  <ThreadPrimitive.Suggestion />
+  <ThreadPrimitive.If />
+</ThreadPrimitive.Root>
+```
+
 ## Getting Started
 
 <Steps>
   <Step>
 
-### Add `thread`
+### Add the component
+
+<Tabs items={["assistant-ui", "shadcn"]}>
+  <Tab>
+
+```sh
+npx assistant-ui@latest add thread
+```
+
+  </Tab>
+  <Tab>
 
 ```sh
 npx shadcn@latest add "https://r.assistant-ui.com/thread"
 ```
 
+  </Tab>
+</Tabs>
+
 This adds a `/components/assistant-ui/thread.tsx` file to your project, which you can adjust as needed.
 
   </Step>
@@ -34,7 +72,7 @@ This adds a `/components/assistant-ui/thread.tsx` file to your project, which yo
 ```tsx title="/app/page.tsx" {1,6}
 import { Thread } from "@/components/assistant-ui/thread";
 
-export default function Home() {
+export default function Chat() {
   return (
     <div className="h-full">
       <Thread />
@@ -45,3 +83,328 @@ export default function Home() {
 
   </Step>
 </Steps>
+
+## Examples
+
+### Welcome Screen
+
+```tsx
+<ThreadPrimitive.If empty>
+  <ThreadWelcome />
+</ThreadPrimitive.If>
+```
+
+### Viewport Spacer
+
+```tsx
+<ThreadPrimitive.If empty={false}>
+  <div className="min-h-8 grow" />
+</ThreadPrimitive.If>
+```
+
+### Conditional Send/Cancel Button
+
+```tsx
+<ThreadPrimitive.If running={false}>
+  <ComposerPrimitive.Send>
+    Send
+  </ComposerPrimitive.Send>
+</ThreadPrimitive.If>
+
+<ThreadPrimitive.If running>
+  <ComposerPrimitive.Cancel>
+    Cancel
+  </ComposerPrimitive.Cancel>
+</ThreadPrimitive.If>
+```
+
+### Suggestions
+
+```tsx
+<ThreadPrimitive.Suggestion
+  prompt="What's the weather in San Francisco?"
+  send
+/>
+```
+
+## API Reference
+
+The following primitives are used within the Thread component and can be customized in your `/components/assistant-ui/thread.tsx` file.
+
+### Root
+
+Contains all parts of the thread.
+
+<ParametersTable
+  type="ThreadPrimitiveRootProps"
+  parameters={[
+    {
+      name: "asChild",
+      type: "boolean",
+      default: "false",
+      description: "Merge props with child element instead of rendering a wrapper div.",
+    },
+    {
+      name: "className",
+      type: "string",
+      description: "CSS class name.",
+    },
+  ]}
+/>
+
+This primitive renders a `<div>` element unless `asChild` is set.
+
+### Viewport
+
+The scrollable area containing all messages. Automatically scrolls to the bottom as new messages are added.
+
+<ParametersTable
+  type="ThreadPrimitiveViewportProps"
+  parameters={[
+    {
+      name: "asChild",
+      type: "boolean",
+      default: "false",
+      description: "Merge props with child element instead of rendering a wrapper div.",
+    },
+    {
+      name: "autoScroll",
+      type: "boolean",
+      default: "true",
+      description:
+        "Whether to automatically scroll to the bottom when new messages are added while the viewport was previously scrolled to the bottom.",
+    },
+    {
+      name: "className",
+      type: "string",
+      description: "CSS class name.",
+    },
+  ]}
+/>
+
+This primitive renders a `<div>` element unless `asChild` is set.
+
+### Messages
+
+Renders all messages in the thread. This primitive renders a separate component for each message.
+
+```tsx
+<ThreadPrimitive.Messages
+  components={{
+    UserMessage: UserMessage,
+    EditComposer: EditComposer,
+    AssistantMessage: AssistantMessage,
+  }}
+/>
+```
+
+<ParametersTable
+  type="ThreadPrimitiveMessagesProps"
+  parameters={[
+    {
+      name: "components",
+      type: "MessageComponents",
+      required: true,
+      description: "Components to render for different message types.",
+      children: [
+        {
+          type: "MessageComponents",
+          parameters: [
+            {
+              name: "Message",
+              type: "ComponentType",
+              description: "Default component for all messages.",
+            },
+            {
+              name: "UserMessage",
+              type: "ComponentType",
+              description: "Component for user messages.",
+            },
+            {
+              name: "EditComposer",
+              type: "ComponentType",
+              description:
+                "Component for user messages being edited.",
+            },
+            {
+              name: "AssistantMessage",
+              type: "ComponentType",
+              description: "Component for assistant messages.",
+            },
+            {
+              name: "SystemMessage",
+              type: "ComponentType",
+              description: "Component for system messages.",
+            },
+          ],
+        },
+      ],
+    },
+  ]}
+/>
+
+
+### MessageByIndex
+
+Renders a single message at the specified index.
+
+```tsx
+<ThreadPrimitive.MessageByIndex
+  index={0}
+  components={{
+    UserMessage: UserMessage,
+    AssistantMessage: AssistantMessage
+  }}
+/>
+```
+
+<ParametersTable
+  type="ThreadPrimitiveMessageByIndexProps"
+  parameters={[
+    {
+      name: "index",
+      type: "number",
+      required: true,
+      description: "The index of the message to render.",
+    },
+    {
+      name: "components",
+      type: "MessageComponents",
+      description: "Components to render for different message types.",
+    },
+  ]}
+/>
+
+### Empty
+
+Renders children only when there are no messages in the thread.
+
+<ParametersTable
+  type="ThreadPrimitiveEmptyProps"
+  parameters={[
+    {
+      name: "children",
+      type: "ReactNode",
+      description: "Content to display when the thread is empty.",
+    },
+  ]}
+/>
+
+### ScrollToBottom
+
+A button to scroll the viewport to the bottom. Disabled when the viewport is already at the bottom.
+
+<ParametersTable
+  type="ThreadPrimitiveScrollToBottomProps"
+  parameters={[
+    {
+      name: "asChild",
+      type: "boolean",
+      default: "false",
+      description: "Merge props with child element instead of rendering a wrapper button.",
+    },
+    {
+      name: "className",
+      type: "string",
+      description: "CSS class name.",
+    },
+  ]}
+/>
+
+This primitive renders a `<button>` element unless `asChild` is set.
+
+### Suggestion
+
+Shows a suggestion to the user. When clicked, replaces the composer's value with the suggestion and optionally sends it.
+
+```tsx
+<ThreadPrimitive.Suggestion
+  prompt="Tell me about React hooks"
+  send
+/>
+```
+
+<ParametersTable
+  type="ThreadPrimitiveSuggestionProps"
+  parameters={[
+    {
+      name: "prompt",
+      type: "string",
+      required: true,
+      description: "The suggestion text to use when clicked.",
+    },
+    {
+      name: "send",
+      type: "boolean",
+      description:
+        "When true, automatically sends the message. When false, replaces or appends the composer text with the suggestion - depending on the value of `clearComposer`",
+    },
+    {
+      name: "clearComposer",
+      type: "boolean",
+      default: "true",
+      description:
+        "Whether to clear the composer after sending. When send is set to false, determines if composer text is replaced with suggestion (true, default), or if the suggestion's prompt is appended to the composer text (false).",
+    },
+    {
+      name: "autoSend",
+      type: "boolean",
+      deprecated: true,
+      description: "Deprecated. Use 'send' instead.",
+    },
+    {
+      name: "method",
+      type: "'replace'",
+      deprecated: true,
+      description: "Deprecated. This parameter is no longer used.",
+    },
+    {
+      name: "asChild",
+      type: "boolean",
+      default: "false",
+      description: "Merge props with child element instead of rendering a wrapper button.",
+    },
+    {
+      name: "className",
+      type: "string",
+      description: "CSS class name.",
+    },
+  ]}
+/>
+
+This primitive renders a `<button>` element unless `asChild` is set.
+
+### If
+
+Conditionally renders children based on thread state.
+
+<ParametersTable
+  type="ThreadPrimitiveIfProps"
+  parameters={[
+    {
+      name: "empty",
+      type: "boolean | undefined",
+      description: "Render children if the thread is empty (no messages).",
+    },
+    {
+      name: "running",
+      type: "boolean | undefined",
+      description: "Render children if the thread is running (assistant is responding).",
+    },
+    {
+      name: "disabled",
+      type: "boolean | undefined",
+      description: "Render children if the thread is disabled.",
+    },
+  ]}
+/>
+
+<Callout type="info">
+Multiple conditions can be combined on `ThreadPrimitive.If` - all specified conditions must match for children to render.
+</Callout>
+
+
+## Related Components
+
+- [ThreadList](/docs/ui/ThreadList) - List of threads
+- [ThreadListSidebar](/docs/ui/ThreadListSidebar) - Sidebar with thread list

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@assistant-ui/mcp-docs-server",
-  "version": "0.1.8",
+  "version": "0.1.10",
   "description": "MCP server for assistant-ui documentation and examples",
   "type": "module",
   "main": "dist/index.js",
@@ -8,18 +8,18 @@
     "assistant-ui-mcp": "./dist/stdio.js"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.17.3",
-    "zod": "^4.0.17",
+    "@modelcontextprotocol/sdk": "^1.19.1",
+    "zod": "^4.1.11",
     "gray-matter": "^4.0.3",
-    "cross-env": "^10.0.0"
+    "cross-env": "^10.1.0"
   },
   "devDependencies": {
-    "@types/node": "^24.3.0",
+    "@types/node": "^24.6.2",
     "tsup": "^8.5.0",
-    "tsx": "^4.20.4",
-    "typescript": "^5.9.2",
+    "tsx": "^4.20.6",
+    "typescript": "^5.9.3",
     "vitest": "^3.2.4",
-    "eslint": "^9.33.0"
+    "eslint": "^9.36.0"
   },
   "files": [
     "dist",