import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
export declare const SERVER_NAME = "misarblog";
/**
 * Reported by `initialize`. Read from package.json (always shipped by npm, one
 * level above dist/) so it can never drift from the published version again:
 * the hardcoded "2.0.0" outlived several 5.x releases.
 */
export declare const SERVER_VERSION: string;
export interface BuildServerOptions {
    /**
     * Register tools that only make sense on the user's own machine.
     *
     * `login` opens a browser and binds a loopback listener; `status` and
     * `upload_image` read local state and files. On the hosted HTTP endpoint the
     * caller already presents a key and has no local filesystem, so exposing them
     * there would advertise capabilities that cannot work.
     */
    includeLocalTools?: boolean;
}
export declare function buildServer(options?: BuildServerOptions): McpServer;
/**
 * Machine-readable summary of the server's surface.
 *
 * Derived from a real `buildServer()` rather than a hand-written list: the
 * previous metadata endpoint on /api/v1/mcp hardcoded 15 tool names and had
 * already drifted from the 20 that route actually served.
 *
 * Reads the SDK's private registries because `McpServer` exposes no public
 * enumeration; the shapes are pinned by the exact-versioned SDK dependency and
 * covered by a test, so a breaking change surfaces at CI rather than in prod.
 */
export declare function describeServer(options?: BuildServerOptions): {
    name: string;
    version: string;
    transport: string;
    tools: {
        name: string;
        description: string;
    }[];
    prompts: {
        name: string;
        description: string;
    }[];
    resources: string[];
    auth: string;
    docs: string;
};
//# sourceMappingURL=server.d.ts.map