import type { McpCliOptions } from './options.ts';
interface HttpOptions {
    hostname?: string;
    port?: number | string;
    protocol: 'http:' | 'https:';
    socketPath?: string;
    rejectUnauthorized: boolean;
    authHeader?: string;
}
export interface BridgeOptions {
    connection: HttpOptions;
    mountPath: string;
    stdin?: NodeJS.ReadableStream;
    stdout?: NodeJS.WritableStream;
    stderr?: NodeJS.WritableStream;
}
/**
 * Run the bridge until stdin closes (host disconnects) or the GET stream
 * errors. Returns a promise that resolves on graceful shutdown.
 */
export declare function runBridge(opts: BridgeOptions): Promise<void>;
/**
 * Resolve `--target` / UDS path + creds → HttpOptions.
 *
 * UDS-mode caveat: only the **operations** profile is reachable via the
 * local Unix Domain Socket. The application profile is mounted on the
 * application HTTP server (the same listener that serves your REST
 * endpoints), which doesn't expose a UDS in v1. Selecting
 * `--profile application` without `--target` is a user error — we throw
 * here rather than silently routing to the operations UDS (which would
 * misleadingly return the operations tool list under super_user auth).
 */
export declare function resolveConnection(opts: McpCliOptions): HttpOptions;
export {};
