/**
 * Argument and environment resolution for `harper mcp`. The CLI deliberately
 * avoids pulling in a flag-parsing dep (Harper's no-new-deps policy) — a few
 * `--key=value` and `--key value` arguments plus a positional subcommand is
 * the entire vocabulary.
 *
 * Two connection modes:
 *   - **UDS** (default): connects to the locally-running Harper instance via
 *     the operationsApi domain socket. **Only the operations profile is
 *     reachable this way** — the application profile is mounted on the
 *     application HTTP server, which doesn't expose a UDS in v1. Filesystem
 *     permissions on the operations socket are the access gate; no
 *     credentials are required or sent.
 *   - **HTTPS**: `--target https://host:port` connects over the network.
 *     Required for `--profile application`. Credential precedence
 *     (highest first):
 *       `--bearer` > `--username` + `--password` > URL-embedded user/pass
 *       > saved JWT from `~/.harperdb/credentials.json` (populated by
 *       `harper login` and looked up via `cliCredentials.normalizeTarget`).
 */
export interface McpCliOptions {
    subcommand: 'bridge' | 'print-config' | 'doctor' | 'help';
    profile: 'operations' | 'application';
    target?: string;
    mountPath: string;
    username?: string;
    password?: string;
    bearer?: string;
    rejectUnauthorized: boolean;
    client?: 'claude-desktop' | 'cursor' | 'zed';
    help: boolean;
}
export declare function parseArgs(argv: readonly string[]): McpCliOptions;
