/** Direct-session config: always-on tools plus direct-only Cortex management. */ export declare function buildFullConfig(serverRoot: string): object; /** Remote execution and time tools, isolated for restricted composition. */ export declare function buildCoreConfig(serverRoot: string): object; /** Read-only task monitoring for top-level direct and thread sessions. */ export declare function buildTasksConfig(serverRoot: string): object; /** Manager answer channel, loaded for top-level direct and thread sessions. */ export declare function buildManagerQaConfig(serverRoot: string): object; /** Thread lifecycle control, loaded only for thread sessions. */ export declare function buildThreadConfig(serverRoot: string): object; /** Strict empty composition with no declared MCP servers. */ export declare function buildEmptyConfig(): object; /** Benchmark composition declaration; the server implementation is supplied separately. */ export declare function buildBenchmarkThreadConfig(serverRoot: string): object; /** TUI MCP config — loaded ONLY by Claude TUI-mode sessions (DR-0012). Isolated tool set: * cortex_plan_enter / cortex_plan_exit / cortex_ask_user replace the native * EnterPlanMode / ExitPlanMode / AskUserQuestion tools, which are excluded from --tools in TUI mode. */ export declare function buildTuiConfig(serverRoot: string): object; /** Slack MCP config — layered ON TOP of the full config (via the variadic `--mcp-config`) only for * sessions that originate from Slack (channel carries the `slack:` prefix). Isolated to the single * cortex-slack server so it can be added/removed independently of the base config; the Claude adapter * and the PI mcp-bridge each decide whether to load it based on the session's source channel. */ export declare function buildSlackConfig(serverRoot: string): object; /** Feishu MCP config — layered ON TOP of the full config (via the variadic `--mcp-config`) only for * sessions that originate from Feishu (channel carries the `feishu:` prefix). Isolated to the single * cortex-feishu server so it can be added/removed independently of the base config; the Claude adapter * and the PI mcp-bridge each decide whether to load it based on the session's source channel. */ export declare function buildFeishuConfig(serverRoot: string): object; /** Web MCP config — layered ON TOP of the full config (via the variadic `--mcp-config`) only for * sessions that originate from the Web UI (channel carries the `web:` prefix). Isolated to the single * cortex-web server (send_file tool) so it can be added/removed independently of the base config; the * Claude adapter decides whether to load it based on the session's source channel. */ export declare function buildWebConfig(serverRoot: string): object; export declare function generateMcpConfig(): void;