import type * as React from "react";
/**
* Layout shell for the MCP server picker. Pure presentational composition —
* the consumer (ui-kit) supplies the molecules (search input, filter chips,
* server cards, summary chips, etc.) and all the domain data + callbacks
* via children. The shell only owns spacing, container queries, and the
* `data-slot` hooks for queryability.
*
* Typical composition:
*
*
*
*
*
*
*
*
*
* {servers.map(s => )}
*
*
*
* Each subcomponent is a thin
with consistent layout — no internal
* state, no domain knowledge. Selection / search / filter behavior belongs
* in the consumer (ui-kit), where the picker's domain state already lives
* (`useToolSelection`, `usePickerSearch`, etc.).
*/
export declare function McpServerPicker({ className, ...props }: React.ComponentProps<"div">): React.JSX.Element;
/**
* Toolbar row — search input, category filter, unoptimized toggle, etc.
* Stacks on narrow containers, flows inline at `@3xl`.
*/
export declare function McpServerPickerHeader({ className, ...props }: React.ComponentProps<"div">): React.JSX.Element;
/**
* Responsive grid of server cards. 1 col by default, 2 at `@md`, 3 at
* `@3xl`, 4 at `@5xl` — sized to comfortably fit `McpServerCard` widths.
*/
export declare function McpServerPickerGrid({ className, ...props }: React.ComponentProps<"div">): React.JSX.Element;
/**
* Responsive grid of tool cards (denser than the server grid). 1 col by
* default, 2 at `@xl`, 3 at `@4xl` — sized to fit `McpToolCard` widths.
* Used inside drill-in views and grouped tool sections.
*/
export declare function McpServerPickerToolGrid({ className, ...props }: React.ComponentProps<"div">): React.JSX.Element;
//# sourceMappingURL=mcp-server-picker.d.ts.map