import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import type { ConnectorClient } from "./client.js";
import type { TabId } from "../connector/store.js";
/**
 * Large payloads live behind MCP resources instead of being inlined.
 *
 * A full HAR, a complete console history or an unabridged Lighthouse result is
 * exactly what you want when something needs proper examination, and exactly
 * what should never be pushed into a context window uninvited. Tools return a
 * `resource_link` so the agent can fetch the whole thing deliberately.
 */
export declare const RESOURCE_SCHEME = "browser-tools";
/** "all" reads across every tab; anything else names one. */
export declare function scopeToOptions(scope: string): {
    tabId?: TabId;
    allTabs?: boolean;
};
export declare function consoleUri(tabId: TabId | null | undefined): string;
export declare function networkUri(tabId: TabId | null | undefined): string;
export declare function harUri(tabId: TabId | null | undefined): string;
export declare function screenshotUri(name: string): string;
export declare function auditUri(reportId: string): string;
export declare function registerResources(server: McpServer, client: ConnectorClient): void;