import { ReactNode } from 'react';
export type McpRequirementInfoItem = {
    id: string;
    icon: ReactNode;
    title: string;
    meta: ReactNode;
    mono?: boolean;
};
export type McpRequirementsStatusProps = {
    /**
     * The unmet requirements to show. An empty array renders the satisfied
     * "Ready" state, so callers must not pass an empty array while data is still
     * resolving — use `loading` for that, and `unverifiedCount` for requirements
     * whose status couldn't be confirmed.
     */
    requirements: McpRequirementInfoItem[];
    /**
     * Count of requirements whose status couldn't be confirmed. Surfaced in the
     * empty ("Couldn't verify") and read-only states; it is intentionally not
     * shown on the direct setup action, which lists only requirements the viewer
     * can act on.
     */
    unverifiedCount?: number;
    /**
     * Renders the direct setup action. Provide it only when the viewer can
     * actually complete setup — its presence (not a permission flag) is what
     * switches between the action and the read-only admin-handoff guidance.
     */
    onSetup?: () => void;
    /**
     * Requirement data isn't ready yet. Renders a skeleton sized to the resolved
     * states so the column doesn't flash "Ready" (or empty) before it's known.
     */
    loading?: boolean;
    className?: string;
};
/**
 * Presentational requirements state for a gateway table row. An `onSetup`
 * callback turns missing requirements into a secondary action; without it,
 * the same summary becomes a ghost disclosure with permission guidance.
 */
export declare function McpRequirementsStatus({ requirements, unverifiedCount, onSetup, loading, className, }: McpRequirementsStatusProps): import("react").JSX.Element;
//# sourceMappingURL=mcp-requirements-status.d.ts.map