import type { RepoStack } from "../profile/scan.js";
import type { McpServer, StdioServer } from "./servers.js";
/**
 * Enterprise MCP handling. Locked-down orgs block MCP three ways: the feature is
 * policy-disabled, egress is blocked (so remote servers AND `npx -y`/`uvx`
 * runtime downloads fail), or process-spawning is blocked. MCP is a convenience
 * layer — filesystem/search/git/graph are all reachable via allowlisted CLI
 * tools — so when it's blocked, capability degrades to CLI tools, not to nothing.
 * Schemas verified against code.claude.com/docs/en/managed-mcp.
 */
/**
 * The no-MCP fallback steering: map each MCP capability to the allowlisted CLI
 * tool that does the same job, so the agent loses the wrapper, not the function.
 */
export declare function mcpFallbackSteering(stack: RepoStack): string;
/** Only stdio servers can be vendored to an exact local command (http needs egress). */
export declare function stdioServers(servers: Record<string, McpServer>): Record<string, StdioServer>;
/** The `managed-mcp.json` an admin deploys: empty map disables MCP; a populated map is the fixed set. */
export declare function managedMcpExample(servers: Record<string, StdioServer>): {
    mcpServers: Record<string, {
        type: "stdio";
        command: string;
        args: string[];
    }>;
};
/** The enterprise control playbook — deployment paths + allowlist, all verified. */
export declare function enterpriseMcpDoc(mode: "none" | "offline", servers: Record<string, StdioServer>): string;