import { Tree } from '@nx/devkit';
/**
 * Registers the @abgov/adsp-sdk-mcp-server MCP server in the workspace-root
 * `.mcp.json` so a coding agent (Claude Code and other MCP clients) can look up
 * grounded ADSP docs and `@abgov/adsp-service-sdk` reference instead of guessing.
 *
 * It's a stdio knowledge server (no credentials), but wiring is not just config:
 * it's also a dev dependency, so the version the client executes is the one the
 * lockfile resolved and `npm audit` can see. `--no` is what makes that binding
 * real — npm assumes `--yes` when stdin isn't a TTY, which is always the case for
 * a stdio MCP server, so without it a resolution miss would silently fetch from
 * the registry instead of failing. Merges into an existing `.mcp.json` and never
 * clobbers a user-customized `adsp-sdk` entry (or a pinned version), so it's safe
 * to re-run and to run for every generated service.
 *
 * The caller is responsible for the install task; every app/service generator
 * already returns one for its own dependencies, and `init` returns one for this.
 *
 * The reconnect reminder lives here, not in each caller — project-scoped MCP
 * servers load at session start, so a file write mid-session (whether from
 * an app/service generator or the standalone `init` generator) leaves the
 * entry configured but inert until the client reconnects, and every caller
 * needs to say so, not just one.
 */
export declare function addAdspMcpServer(host: Tree): void;