import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
/**
 * Serve this connector over HTTP instead of stdio.
 *
 * Not a second product surface — the platform's own `POST /mcp` is that — but the way a REAL
 * coding agent can drive the packaged server. A stdio server lives and dies with one process, so an
 * agent that issues one command per turn would restart it on every call and supersede its own
 * connector session each time. Over HTTP the server outlives the turn, which is what lets the agent
 * that is running it also BE the parent: take a model task, reason about it, hand the answer back.
 *
 * Bound to loopback only, and holding whatever token started it. It is a development transport for
 * the machine it runs on, and binding it anywhere else would publish that token's access.
 */
export declare const serveHttp: (server: McpServer, port: number, log: (line: string) => void) => Promise<() => Promise<void>>;