/**
 * `qodo-skills` MCP server — browser stub. See `manager.browser.ts` and
 * `path.browser.ts` for the rationale.
 *
 * The Node version reads SKILL.md bodies + supporting files from disk
 * (via `node:fs`), which is fundamentally Node-only. The browser stub
 * throws on `callTool` so a consumer who somehow constructs the server
 * in a browser build gets a typed error rather than `node:fs` resolving
 * to an empty object at bundle time.
 *
 * QodoClient's constructor instantiates this server only when
 * `ClientOptions.skills` is provided; the manager's browser stub
 * already throws on `discover()`, so this stub primarily exists for
 * the bundler's import resolver.
 */
import type { McpInProcessHandler } from '../../client/QarRegistryClient.js';
import type { SkillsManager } from '../manager.js';
import type { McpToolResult } from './types.js';
export declare const QODO_SKILLS_TOOL_NAMES: readonly ["list_skills", "get_skill", "get_skill_file"];
export type QodoSkillsToolName = (typeof QODO_SKILLS_TOOL_NAMES)[number];
export { qodoSkillsFunctionToolDefs } from './wireDefs.js';
export declare class QodoSkillsMcpServer {
    constructor(_skills: SkillsManager, _opts?: {
        readonly emit?: (event: never) => void;
    });
    get loadedSkillFqns(): readonly string[];
    get cachedBodyBytes(): number;
    dispose(): void;
    callTool(_toolName: string, _args: Record<string, unknown>): Promise<McpToolResult>;
}
export declare function asMcpHandler(server: QodoSkillsMcpServer): McpInProcessHandler;
//# sourceMappingURL=server.browser.d.ts.map