/**
 * The TracePass MCP server factory.
 *
 * `createMcpServer(config)` builds an `McpServer` with every
 * TracePass tool registered, bound to an API client. It is
 * TRANSPORT-AGNOSTIC — it knows nothing about stdio vs HTTP. The
 * caller connects it to a transport:
 *   - the hosted `/mcp` route → WebStandardStreamableHTTPServerTransport
 *   - the standalone npm package → StdioServerTransport
 *
 * One factory, every transport — so the tool surface can never
 * drift between the hosted endpoint and the local package.
 */
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
/** Server identity reported to MCP clients.
 *
 *  THIS IS THE ONLY PLACE THE VERSION IS WRITTEN. `http.ts` reads it for both
 *  the server card and the initialize response — do not re-type the literal
 *  there. Keep it in step with `package.json` + `server.json` on a release;
 *  a stale value here makes a correct deploy look like a failed one, because
 *  the endpoint keeps reporting the old version while serving the new code. */
export declare const MCP_SERVER_INFO: {
    readonly name: "tracepass";
    readonly version: "1.7.4";
};
export interface CreateMcpServerConfig {
    /** Base URL of the TracePass app — e.g. "https://app.tracepass.eu".
     *  The hosted route passes its own origin; the npm package passes
     *  the public URL (or a customer override). */
    baseUrl: string;
    /** The caller's tp_ API key — every v1 call is made as this key. */
    apiKey: string;
}
/**
 * Build a fully-wired TracePass `McpServer`. The caller is
 * responsible for connecting it to a transport via `.connect()`.
 */
export declare function createMcpServer(config: CreateMcpServerConfig): McpServer;
//# sourceMappingURL=server.d.ts.map