@assistant-ui/mcp-docs-server 0.1.31 → 0.1.33

package/.docs/raw/docs/ui/part-grouping.mdx

@@ -10,18 +10,19 @@ import { PartGroupingSample } from "@/components/docs/samples/part-grouping";
 
 ## Basic Usage
 
-For adjacent grouping, use `MessagePrimitive.GroupedParts`. Return a group-key path for each part; adjacent parts that share a group key are coalesced and rendered through the group case.
+For adjacent grouping, use `MessagePrimitive.GroupedParts`. For the common case — grouping by `part.type` — pass `groupPartByType` to map each part type to a group-key path. Adjacent parts that share a group key are coalesced and rendered through the group case.
 
 ```tsx title="/components/assistant-ui/thread.tsx"
+import { MessagePrimitive, groupPartByType } from "@assistant-ui/react";
+
 const AssistantMessage: FC = () => {
   return (
     <MessagePrimitive.Root className="...">
       <div className="...">
         <MessagePrimitive.GroupedParts
-          groupBy={(part) => {
-            if (part.type === "tool-call") return ["group-tool"];
-            return null;
-          }}
+          groupBy={groupPartByType({
+            "tool-call": ["group-tool"],
+          })}
         >
           {({ part, children }) => {
             switch (part.type) {
@@ -42,6 +43,8 @@ const AssistantMessage: FC = () => {
 };
 ```
 
+Reach for an inline `groupBy={(part) => …}` only when the helper isn't expressive enough — e.g. you need to branch on `part.toolName`, `part.parentId`, or part metadata.
+
 ## How Adjacent Grouping Works
 
 `groupBy` receives each part and returns either `null` for an ungrouped leaf or a group-key path such as `["group-chainOfThought", "group-tool"]`. Group keys must start with `"group-"` so your render function can distinguish synthetic groups from real part types.
@@ -89,7 +92,7 @@ function ParentGroup({
 
 <MessagePrimitive.GroupedParts
   groupBy={(part) => {
-    if (!part.parentId) return null;
+    if (!part.parentId) return [];
     return [`group-parent-${part.parentId}`];
   }}
 >
@@ -117,7 +120,7 @@ Organize adjacent tool calls by tool name:
 ```tsx
 <MessagePrimitive.GroupedParts
   groupBy={(part) => {
-    if (part.type !== "tool-call") return null;
+    if (part.type !== "tool-call") return [];
     return [`group-tool-${part.toolName}`];
   }}
 >
@@ -147,10 +150,9 @@ Combine multiple text parts into cohesive blocks:
 
 ```tsx
 <MessagePrimitive.GroupedParts
-  groupBy={(part) => {
-    if (part.type === "text") return ["group-text-block"];
-    return null;
-  }}
+  groupBy={groupPartByType({
+    text: ["group-text-block"],
+  })}
 >
   {({ part, children }) => {
     switch (part.type) {
@@ -177,12 +179,11 @@ Separate different types of content for distinct visual treatment:
 
 ```tsx
 <MessagePrimitive.GroupedParts
-  groupBy={(part) => {
-    if (part.type === "text") return ["group-content-text"];
-    if (part.type === "tool-call") return ["group-content-tools"];
-    if (part.type === "reasoning") return ["group-content-reasoning"];
-    return null;
-  }}
+  groupBy={groupPartByType({
+    text: ["group-content-text"],
+    "tool-call": ["group-content-tools"],
+    reasoning: ["group-content-reasoning"],
+  })}
 >
   {({ part, children }) => {
     switch (part.type) {
@@ -205,6 +206,52 @@ Separate different types of content for distinct visual treatment:
 </MessagePrimitive.GroupedParts>
 ```
 
+### Keep Standalone Tool UIs Out of the Trace
+
+Tool UIs fall into three buckets: prompting the user (human-in-the-loop), informing the user (generative UI), and traces of what the model is doing (routine tool calls). The first two should be surfaced on their own, while the last belongs folded into a collapsible chain-of-thought group.
+
+Mark a tool with `display: "standalone"` to keep its UI out of the grouped trace. `human` tools and MCP apps are standalone automatically; every other tool defaults to `"inline"` and opts in explicitly:
+
+```tsx
+const toolkit = {
+  ask_user: { type: "human", render: AskUI }, // standalone (forced)
+  search_web: { type: "frontend", render: SearchUI }, // inline trace (default)
+  checkout: {
+    type: "frontend",
+    render: CheckoutUI,
+    display: "standalone", // opt in
+  },
+} satisfies Toolkit;
+```
+
+The synthetic `"standalone-tool-call"` key on `groupPartByType` matches all of these. `MessagePrimitive.GroupedParts` passes the live tool-UI registry to `groupBy` as a second `context` argument, and the helper reads it to resolve the registry-driven cases — MCP-app calls are detected from the part alone, so nothing is threaded in:
+
+```tsx
+<MessagePrimitive.GroupedParts
+  groupBy={groupPartByType({
+    reasoning: ["group-chainOfThought", "group-reasoning"],
+    "tool-call": ["group-chainOfThought", "group-tool"],
+    "standalone-tool-call": [], // ungrouped — rendered on its own
+  })}
+>
+  {({ part, children }) => {
+    switch (part.type) {
+      case "group-chainOfThought":
+        return <div className="chain-of-thought">{children}</div>;
+      case "tool-call":
+        return part.toolUI ?? <ToolFallback {...part} />;
+      // ...
+      default:
+        return null;
+    }
+  }}
+</MessagePrimitive.GroupedParts>;
+```
+
+<Callout type="info">
+  The `"mcp-app"` key is deprecated in favor of `"standalone-tool-call"`, which is a superset (it also matches MCP-app tool calls). Existing `"mcp-app"` usage keeps working.
+</Callout>
+
 ### Group by Custom Metadata
 
 Use any custom metadata in your parts for grouping:
@@ -219,7 +266,7 @@ const priorityStyles = {
 <MessagePrimitive.GroupedParts
   groupBy={(part) => {
     const priority = part.metadata?.priority;
-    if (!priority) return null;
+    if (!priority) return [];
     return [`group-priority-${priority}`];
   }}
 >
@@ -300,9 +347,9 @@ const stream = createAssistantStream(async (controller) => {
   parameters={[
     {
       name: "groupBy",
-      type: "(part: PartState, index: number, parts: readonly PartState[]) => GroupKey",
+      type: "(part: PartState) => readonly `group-${string}`[]",
       description:
-        "Maps a part to a group-key path. Return null, undefined, or [] to leave the part ungrouped. Group keys must start with group-.",
+        "Maps a part to a group-key path. Return `[]` to leave the part ungrouped. Group keys must start with `group-`. Prefer `groupPartByType` for the common `part.type → path` case.",
       required: true,
     },
     {
@@ -315,6 +362,19 @@ const stream = createAssistantStream(async (controller) => {
   ]}
 />
 
+### groupPartByType helper
+
+`groupPartByType` builds a `groupBy` from a `part.type → group-key path` map. Part types missing from the map are left ungrouped. The returned function carries an internal memo fingerprint so the tree survives unrelated re-renders.
+
+```typescript
+import { groupPartByType } from "@assistant-ui/react";
+
+groupPartByType({
+  reasoning: ["group-thought", "group-reasoning"],
+  "tool-call": ["group-thought", "group-tool"],
+});
+```
+
 ### GroupPart Type
 
 ```typescript
@@ -331,34 +391,9 @@ type GroupPart<TKey extends `group-${string}` = `group-${string}`> = {
 2. **Handle ungrouped parts**: Always include leaf cases for the part types your message can render.
 3. **Only render `children` for groups**: Leaf parts receive a sentinel `children` value that throws if rendered accidentally.
 4. **Use `group-` prefixes**: Synthetic group keys must start with `group-` so they cannot collide with real part types.
-5. **Keep `groupBy` stable**: Prefer a module-level function or `useCallback` for frequently re-rendering message trees.
 
 ## Common Patterns
 
-### Conditional Grouping
-
-Only group when certain conditions are met:
-
-```tsx
-<MessagePrimitive.GroupedParts
-  groupBy={(part, index, parts) => {
-    const hasManyParts = parts.length >= 5;
-    if (!hasManyParts) return null;
-    if (part.type === "tool-call") return ["group-tools"];
-    return null;
-  }}
->
-  {({ part, children }) => {
-    if (part.type === "group-tools") {
-      return <div className="rounded-lg border p-3">{children}</div>;
-    }
-    if (part.type === "tool-call") return part.toolUI ?? <ToolFallback {...part} />;
-    if (part.type === "text") return <MarkdownText />;
-    return null;
-  }}
-</MessagePrimitive.GroupedParts>
-```
-
 ### Nested Grouping
 
 Create hierarchical adjacent groups by returning multiple keys:
@@ -370,7 +405,7 @@ Create hierarchical adjacent groups by returning multiple keys:
       return ["group-chainOfThought", "group-reasoning"];
     if (part.type === "tool-call")
       return ["group-chainOfThought", `group-tool-${part.toolName}`];
-    return null;
+    return [];
   }}
 >
   {({ part, children }) => {
@@ -391,10 +426,9 @@ Adjust group appearance based on the group node's status or indices:
 
 ```tsx
 <MessagePrimitive.GroupedParts
-  groupBy={(part) => {
-    if (part.type === "tool-call") return ["group-tools"];
-    return null;
-  }}
+  groupBy={groupPartByType({
+    "tool-call": ["group-tools"],
+  })}
 >
   {({ part, children }) => {
     if (part.type === "group-tools") {

package/.docs/raw/docs/ui/reasoning.mdx

@@ -31,7 +31,7 @@ Render reasoning parts through `MessagePrimitive.GroupedParts`. Group consecutiv
 While reasoning is streaming, `part.status.type === "running"`. Pass that to `defaultOpen` so the accordion auto-opens during streaming and lets the user collapse it once the model moves on.
 
 ```tsx title="/app/components/assistant-ui/thread.tsx"
-import { MessagePrimitive } from "@assistant-ui/react";
+import { MessagePrimitive, groupPartByType } from "@assistant-ui/react";
 import { MarkdownText } from "@/components/assistant-ui/markdown-text";
 import { ToolFallback } from "@/components/assistant-ui/tool-fallback";
 import {
@@ -47,10 +47,9 @@ const AssistantMessage: FC = () => {
     <MessagePrimitive.Root className="...">
       <div className="...">
         <MessagePrimitive.GroupedParts // [!code ++]
-          groupBy={(part) => { // [!code ++]
-            if (part.type === "reasoning") return ["group-reasoning"]; // [!code ++]
-            return null; // [!code ++]
-          }} // [!code ++]
+          groupBy={groupPartByType({ // [!code ++]
+            reasoning: ["group-reasoning"], // [!code ++]
+          })} // [!code ++]
         > // [!code ++]
           {({ part, children }) => { // [!code ++]
             switch (part.type) { // [!code ++]

package/.docs/raw/docs/ui/sources.mdx

@@ -119,8 +119,25 @@ Displays the favicon for the given URL. Falls back to the domain initial inside
 | Prop | Type | Default | Description |
 |------|------|---------|-------------|
 | `url` | `string` | — | URL used to derive the favicon and fallback initial |
+| `faviconUrl` | `(domain: string) => string` | DuckDuckGo's `ip3` endpoint | Override the favicon source — useful in environments where the default service is unreachable |
 | `className` | `string` | — | Additional CSS classes applied to the `<img>` or fallback `<span>` |
 
+#### Customizing the favicon provider
+
+The default `<Sources>` component renders `<SourceIcon>` without forwarding `faviconUrl`, so the prop only applies when you compose `Sources.Icon` directly:
+
+```tsx
+<Sources.Root href={url}>
+  <Sources.Icon
+    url={url}
+    faviconUrl={(domain) => `https://my-favicon-proxy.example.com/${domain}.ico`}
+  />
+  <Sources.Title>{title}</Sources.Title>
+</Sources.Root>
+```
+
+To change the default for every source in your app, edit the `defaultFaviconUrl` constant at the top of your copied `sources.tsx` — that is the single source of truth used by `<Sources>`.
+
 ### `SourceTitle`
 
 Truncated title text rendered as a `<span>`.

package/.docs/raw/docs/ui/streamdown.mdx

@@ -1,6 +1,6 @@
 ---
-title: Streamdown
-description: Alternative markdown renderer with built-in syntax highlighting, math, and diagram support.
+title: Streamdown Markdown Renderer
+description: Stream markdown into a React chat UI with syntax highlighting, math, and Mermaid diagrams. Powered by Vercel Streamdown, integrated for assistant-ui.
 links:
   - label: Streamdown
     url: https://github.com/vercel/streamdown
@@ -26,6 +26,36 @@ For additional features, install the optional plugins:
 
 <PackageManagerTabs packages={["@streamdown/code", "@streamdown/math", "@streamdown/mermaid", "@streamdown/cjk"]} />
 
+## CSS setup
+
+Streamdown's controls (code-block copy/download buttons, mermaid fullscreen overlay) and the streaming caret are written as Tailwind utility classes. Tailwind v4 does not scan `node_modules` by default, so add a `@source` directive for Streamdown (and one per installed plugin) to the same global stylesheet that imports Tailwind:
+
+```css
+@import "tailwindcss";
+
+@source "../node_modules/streamdown/dist/*.js";
+@source "../node_modules/@streamdown/code/dist/*.js";
+@source "../node_modules/@streamdown/math/dist/*.js";
+@source "../node_modules/@streamdown/mermaid/dist/*.js";
+@source "../node_modules/@streamdown/cjk/dist/*.js";
+```
+
+Adjust the relative path to wherever your project's `node_modules` lives. In a pnpm or Turbo monorepo with hoisted dependencies, you typically need more `../` segments to reach the workspace root. Only include the plugin lines for packages you actually installed.
+
+Without these directives, the copy/download/fullscreen buttons render with no padding or cursor styling (and look broken), and the `caret` indicator stays invisible.
+
+<Callout type="info">
+  Streamdown's components assume the shadcn/ui design tokens (`--background`, `--muted-foreground`, `--border`, etc.). If you are not on shadcn/ui, copy the minimum variable set from the [Streamdown README](https://github.com/vercel/streamdown#css-custom-properties-design-tokens).
+</Callout>
+
+If you opt into the `animated` prop or use `createAnimatePlugin` for word-level fade-in, also import the keyframes once at your app entry:
+
+```ts
+import "streamdown/styles.css";
+```
+
+The bare `caret` prop does **not** require this import; only the word-level animation does.
+
 ## Basic Usage
 
 ```tsx
@@ -173,6 +203,8 @@ Display a caret indicator during streaming:
 <StreamdownTextPrimitive caret="circle" /> // ●
 ```
 
+The caret is implemented as a Tailwind `::after` utility on the wrapper, so it only appears if your Tailwind setup includes the `@source` directive from [CSS setup](#css-setup).
+
 ### Link Safety
 
 Show confirmation before opening external links:

package/.docs/raw/docs/ui/thread-list.mdx

@@ -1,6 +1,6 @@
 ---
-title: ThreadList
-description: Switch between conversations. Supports sidebar or dropdown layouts.
+title: Thread List Component
+description: Sidebar or dropdown component for switching between AI chat conversations. Persistent thread state, search, and active selection — built for assistant-ui apps.
 platforms: ["react"]
 ---
 

package/.docs/raw/docs/ui/thread.mdx

@@ -1,6 +1,6 @@
 ---
-title: Thread
-description: The main chat container with messages, composer, and auto-scroll.
+title: Thread Component
+description: Stream-ready React chat container with message list, composer, auto-scroll, and accessibility built in. Drop into any AI chat UI built with assistant-ui.
 platforms: ["react"]
 ---
 

package/.docs/raw/docs/ui/tool-group.mdx

@@ -29,10 +29,10 @@ This adds `/components/assistant-ui/tool-group.tsx` and `/components/assistant-u
 
 ### Use it in your application
 
-Use `MessagePrimitive.GroupedParts` and return `"group-tool"` for tool-call parts. The group case wraps `children`; the tool-call leaf renders the resolved tool UI or your fallback.
+Use `MessagePrimitive.GroupedParts` with `groupPartByType` to map tool-call parts to `"group-tool"`. The group case wraps `children`; the tool-call leaf renders the resolved tool UI or your fallback.
 
 ```tsx title="/components/assistant-ui/thread.tsx"
-import { MessagePrimitive } from "@assistant-ui/react";
+import { MessagePrimitive, groupPartByType } from "@assistant-ui/react";
 import { ToolFallback } from "@/components/assistant-ui/tool-fallback";
 import {
   ToolGroupContent,
@@ -44,10 +44,9 @@ const AssistantMessage = () => {
   return (
     <MessagePrimitive.Root>
       <MessagePrimitive.GroupedParts
-        groupBy={(part) => {
-          if (part.type === "tool-call") return ["group-tool"];
-          return null;
-        }}
+        groupBy={groupPartByType({
+          "tool-call": ["group-tool"],
+        })}
       >
         {({ part, children }) => {
           switch (part.type) {

package/.docs/raw/docs/utilities/heat-graph.mdx

@@ -4,7 +4,7 @@ description: Headless, composable activity heatmap components for React.
 platforms: ["react"]
 ---
 
-import { HeatGraphDemo } from "@/app/heat-graph/heat-graph-demo";
+import { HeatGraphDemo } from "@/app/(demos)/heat-graph/heat-graph-demo";
 
 `heat-graph` provides headless, Radix-style primitives for building GitHub-style activity heatmap graphs.
 

package/README.md

@@ -1,28 +1,23 @@
-# Assistant-UI MCP Docs Server
+# `@assistant-ui/mcp-docs-server`
 
-A Model Context Protocol (MCP) server that provides AI assistants with direct access to assistant-ui's documentation and examples.
+Model Context Protocol (MCP) server that gives AI assistants direct access to assistant-ui's documentation and example projects. Exposes `assistantUIDocs` (retrieve documentation by path) and `assistantUIExamples` (access complete example projects).
 
-> **📖 Full Documentation**
-> For detailed installation instructions, troubleshooting, and advanced usage, visit the [complete documentation](https://www.assistant-ui.com/docs/llm#mcp).
+> [!NOTE]
+> Detailed installation, troubleshooting, and advanced usage at [assistant-ui.com/docs/llm#mcp](https://www.assistant-ui.com/docs/llm#mcp).
 
 ## Installation
 
 ### Claude Code
 
 ```bash
-# Add to current project
 claude mcp add assistant-ui -- npx -y @assistant-ui/mcp-docs-server
-
-# Or add globally for all projects
+# or globally for all projects
 claude mcp add --scope user assistant-ui -- npx -y @assistant-ui/mcp-docs-server
 ```
 
 ### Claude Desktop
 
-Add to your Claude Desktop configuration:
-
-- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
-- Windows: `%APPDATA%\Claude\claude_desktop_config.json`
+Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):
 
 ```json
 {
@@ -35,39 +30,13 @@ Add to your Claude Desktop configuration:
 }
 ```
 
-### Cursor
-
-Add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):
+### Cursor / Windsurf
 
-```json
-{
-  "mcpServers": {
-    "assistant-ui": {
-      "command": "npx",
-      "args": ["-y", "@assistant-ui/mcp-docs-server"]
-    }
-  }
-}
-```
-
-### Windsurf
-
-Add to `~/.codeium/windsurf/mcp_config.json`:
-
-```json
-{
-  "mcpServers": {
-    "assistant-ui": {
-      "command": "npx",
-      "args": ["-y", "@assistant-ui/mcp-docs-server"]
-    }
-  }
-}
-```
+Add to `.cursor/mcp.json` (or `~/.cursor/mcp.json`) for Cursor, or `~/.codeium/windsurf/mcp_config.json` for Windsurf, using the same `mcpServers` block as above.
 
-### VSCode
+### VS Code
 
-Add to `.vscode/mcp.json` in your project:
+Add to `.vscode/mcp.json`:
 
 ```json
 {
@@ -83,7 +52,7 @@ Add to `.vscode/mcp.json` in your project:
 
 ### Zed
 
-Add to `settings.json` (open via `cmd+,` or `zed: open settings`):
+Add to `settings.json`:
 
 ```json
 {
@@ -91,38 +60,11 @@ Add to `settings.json` (open via `cmd+,` or `zed: open settings`):
     "assistant-ui": {
       "command": {
         "path": "npx",
-        "args": ["-y", "@assistant-ui/mcp-docs-server"],
-        "env": {}
-      },
-      "settings": {}
+        "args": ["-y", "@assistant-ui/mcp-docs-server"]
+      }
     }
   }
 }
 ```
 
-## Tools
-
-- **assistantUIDocs** - Retrieve documentation by path
-- **assistantUIExamples** - Access complete example projects
-
-## Managing the Server
-
-### Claude Code
-
-```bash
-# View configured servers
-claude mcp list
-
-# Get server details
-claude mcp get assistant-ui
-
-# Remove the server
-claude mcp remove assistant-ui
-
-# Restart the server
-claude mcp restart assistant-ui
-```
-
-## License
-
-MIT
+To list, get, or remove the server, use your editor's MCP management commands.

package/dist/constants.d.ts

@@ -1,10 +1,13 @@
-export declare const ROOT_DIR: string;
-export declare const PACKAGE_DIR: string;
-export declare const EXAMPLES_PATH: string;
-export declare const DOCS_PATH: string;
-export declare const CODE_EXAMPLES_PATH: string;
-export declare const MDX_EXTENSION = ".mdx";
-export declare const MD_EXTENSION = ".md";
-export declare const MAX_FILE_SIZE: number;
-export declare const IS_PREPARE_MODE: boolean | undefined;
+//#region src/constants.d.ts
+declare const ROOT_DIR: string;
+declare const PACKAGE_DIR: string;
+declare const EXAMPLES_PATH: string;
+declare const DOCS_PATH: string;
+declare const CODE_EXAMPLES_PATH: string;
+declare const MDX_EXTENSION = ".mdx";
+declare const MD_EXTENSION = ".md";
+declare const MAX_FILE_SIZE: number;
+declare const IS_PREPARE_MODE: boolean | undefined;
+//#endregion
+export { CODE_EXAMPLES_PATH, DOCS_PATH, EXAMPLES_PATH, IS_PREPARE_MODE, MAX_FILE_SIZE, MDX_EXTENSION, MD_EXTENSION, PACKAGE_DIR, ROOT_DIR };
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"constants.d.ts","sourceRoot":"","sources":["../src/constants.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,QAAQ,QAA+B,CAAC;AACrD,eAAO,MAAM,WAAW,QAAyB,CAAC;AAElD,eAAO,MAAM,aAAa,QAA6B,CAAC;AAGxD,eAAO,MAAM,SAAS,QAA8B,CAAC;AACrD,eAAO,MAAM,kBAAkB,QAA6C,CAAC;AAE7E,eAAO,MAAM,aAAa,SAAS,CAAC;AACpC,eAAO,MAAM,YAAY,QAAQ,CAAC;AAElC,eAAO,MAAM,aAAa,QAAmB,CAAC;AAE9C,eAAO,MAAM,eAAe,qBAE3B,CAAC"}
+{"version":3,"file":"constants.d.ts","names":[],"sources":["../src/constants.ts"],"mappings":";cAKa,QAAA;AAAA,cACA,WAAA;AAAA,cAEA,aAAA;AAAA,cAGA,SAAA;AAAA,cACA,kBAAA;AAAA,cAEA,aAAA;AAAA,cACA,YAAA;AAAA,cAEA,aAAA;AAAA,cAEA,eAAA"}

package/dist/constants.js

@@ -1,14 +1,18 @@
 import { fileURLToPath } from "node:url";
 import { dirname, join } from "node:path";
+//#region src/constants.ts
 const __dirname = dirname(fileURLToPath(import.meta.url));
-export const ROOT_DIR = join(__dirname, "../../../");
-export const PACKAGE_DIR = join(__dirname, "../");
-export const EXAMPLES_PATH = join(ROOT_DIR, "examples");
+const ROOT_DIR = join(__dirname, "../../../");
+const PACKAGE_DIR = join(__dirname, "../");
+const EXAMPLES_PATH = join(ROOT_DIR, "examples");
 const DOCS_BASE = join(PACKAGE_DIR, ".docs");
-export const DOCS_PATH = join(DOCS_BASE, "raw/docs");
-export const CODE_EXAMPLES_PATH = join(DOCS_BASE, "organized/code-examples");
-export const MDX_EXTENSION = ".mdx";
-export const MD_EXTENSION = ".md";
-export const MAX_FILE_SIZE = 10 * 1024 * 1024;
-export const IS_PREPARE_MODE = process.argv[1]?.includes("prepare-docs/prepare");
+const DOCS_PATH = join(DOCS_BASE, "raw/docs");
+const CODE_EXAMPLES_PATH = join(DOCS_BASE, "organized/code-examples");
+const MDX_EXTENSION = ".mdx";
+const MD_EXTENSION = ".md";
+const MAX_FILE_SIZE = 10 * 1024 * 1024;
+const IS_PREPARE_MODE = process.argv[1]?.includes("prepare-docs/prepare");
+//#endregion
+export { CODE_EXAMPLES_PATH, DOCS_PATH, EXAMPLES_PATH, IS_PREPARE_MODE, MAX_FILE_SIZE, MDX_EXTENSION, MD_EXTENSION, PACKAGE_DIR, ROOT_DIR };
+
 //# sourceMappingURL=constants.js.map

package/dist/constants.js.map

@@ -1 +1 @@
-{"version":3,"file":"constants.js","sourceRoot":"","sources":["../src/constants.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AACzC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAE1C,MAAM,SAAS,GAAG,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;AAE1D,MAAM,CAAC,MAAM,QAAQ,GAAG,IAAI,CAAC,SAAS,EAAE,WAAW,CAAC,CAAC;AACrD,MAAM,CAAC,MAAM,WAAW,GAAG,IAAI,CAAC,SAAS,EAAE,KAAK,CAAC,CAAC;AAElD,MAAM,CAAC,MAAM,aAAa,GAAG,IAAI,CAAC,QAAQ,EAAE,UAAU,CAAC,CAAC;AAExD,MAAM,SAAS,GAAG,IAAI,CAAC,WAAW,EAAE,OAAO,CAAC,CAAC;AAC7C,MAAM,CAAC,MAAM,SAAS,GAAG,IAAI,CAAC,SAAS,EAAE,UAAU,CAAC,CAAC;AACrD,MAAM,CAAC,MAAM,kBAAkB,GAAG,IAAI,CAAC,SAAS,EAAE,yBAAyB,CAAC,CAAC;AAE7E,MAAM,CAAC,MAAM,aAAa,GAAG,MAAM,CAAC;AACpC,MAAM,CAAC,MAAM,YAAY,GAAG,KAAK,CAAC;AAElC,MAAM,CAAC,MAAM,aAAa,GAAG,EAAE,GAAG,IAAI,GAAG,IAAI,CAAC;AAE9C,MAAM,CAAC,MAAM,eAAe,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,QAAQ,CACtD,sBAAsB,CACvB,CAAC"}
+{"version":3,"file":"constants.js","names":[],"sources":["../src/constants.ts"],"sourcesContent":["import { fileURLToPath } from \"node:url\";\nimport { dirname, join } from \"node:path\";\n\nconst __dirname = dirname(fileURLToPath(import.meta.url));\n\nexport const ROOT_DIR = join(__dirname, \"../../../\");\nexport const PACKAGE_DIR = join(__dirname, \"../\");\n\nexport const EXAMPLES_PATH = join(ROOT_DIR, \"examples\");\n\nconst DOCS_BASE = join(PACKAGE_DIR, \".docs\");\nexport const DOCS_PATH = join(DOCS_BASE, \"raw/docs\");\nexport const CODE_EXAMPLES_PATH = join(DOCS_BASE, \"organized/code-examples\");\n\nexport const MDX_EXTENSION = \".mdx\";\nexport const MD_EXTENSION = \".md\";\n\nexport const MAX_FILE_SIZE = 10 * 1024 * 1024;\n\nexport const IS_PREPARE_MODE = process.argv[1]?.includes(\n  \"prepare-docs/prepare\",\n);\n"],"mappings":";;;AAGA,MAAM,YAAY,QAAQ,cAAc,OAAO,KAAK,GAAG,CAAC;AAExD,MAAa,WAAW,KAAK,WAAW,WAAW;AACnD,MAAa,cAAc,KAAK,WAAW,KAAK;AAEhD,MAAa,gBAAgB,KAAK,UAAU,UAAU;AAEtD,MAAM,YAAY,KAAK,aAAa,OAAO;AAC3C,MAAa,YAAY,KAAK,WAAW,UAAU;AACnD,MAAa,qBAAqB,KAAK,WAAW,yBAAyB;AAE3E,MAAa,gBAAgB;AAC7B,MAAa,eAAe;AAE5B,MAAa,gBAAgB,KAAK,OAAO;AAEzC,MAAa,kBAAkB,QAAQ,KAAK,IAAI,SAC9C,sBACF"}

package/dist/index.d.ts

@@ -1,4 +1,8 @@
-import { McpServer } from "@modelcontextprotocol/sdk";
-export declare const server: McpServer;
-export declare function runServer(): Promise<void>;
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+
+//#region src/index.d.ts
+declare const server: McpServer;
+declare function runServer(): Promise<void>;
+//#endregion
+export { runServer, server };
 //# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,kCAAgD;AAcpE,eAAO,MAAM,MAAM,WAGjB,CAAC;AAeH,wBAAsB,SAAS,kBAW9B"}
+{"version":3,"file":"index.d.ts","names":[],"sources":["../src/index.ts"],"mappings":";;;cAca,MAAA,EAAM,SAGjB;AAAA,iBAeoB,SAAA,IAAS,OAAA"}