/**
 * Long Tail Admin MCP Server
 *
 * Unified system management — every tool maps directly to a REST API
 * route handler. The tools are organized by route file:
 *
 *   tasks.ts               — routes/tasks.ts
 *   escalations.ts         — routes/escalations/ (incl. metadata + bulk)
 *   workflow-config.ts     — routes/workflows/config.ts
 *   workflows.ts           — routes/workflows/discovery.ts + invocation.ts
 *   mcp-servers.ts         — routes/mcp.ts
 *   yaml-workflows.ts      — routes/yaml-workflows/
 *   users.ts               — routes/users.ts + routes/roles.ts
 *   maintenance.ts         — routes/dba.ts
 *   agents.ts              — routes/agents.ts
 *   agent-subscriptions.ts — routes/agents.ts (subscription sub-routes)
 *   bot-accounts.ts        — routes/bot-accounts.ts
 *   controlplane.ts        — routes/controlplane.ts
 *   pipelines.ts           — routes/pipelines.ts
 *   topics.ts              — routes/topics.ts
 *   settings.ts            — routes/settings.ts
 *   exports.ts             — routes/exports.ts
 *
 * This server replaces three previously separate servers:
 *   - long-tail-db-query (read-only task/escalation/health queries)
 *   - long-tail-workflow-compiler (compile + deploy)
 *   - mcp-workflows-longtail (list + get + invoke compiled workflows)
 *
 * The long-tail-human-queue server remains separate because
 * escalate_and_wait has special durable signal semantics that
 * are deeply wired into the YAML worker infrastructure.
 */
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
export declare function createAdminServer(options?: {
    name?: string;
    fresh?: boolean;
}): Promise<McpServer>;
export declare function getAdminServer(): McpServer | null;
export declare function stopAdminServer(): Promise<void>;