askit-build-mcplisted

# askit-build-mcp ## Purpose Author the plugin's MCP servers as one portable `.mcp.json` at the plugin root (the standard `{ "mcpServers": { ... } }` format) and wire the per-target `mcpServers` manifest pointer. Two modes: `create` adds a server; `improve` fixes findings. MCP is Universal-tier: the server definition is portable and both Claude and Codex ingest a bundled `.mcp.json` referenced by the native manifest's `mcpServers` pointer (Standard sec 3.9). Authoring depth is in [references/authoring-mcp.md](references/authoring-mcp.md). Follows the shared builder contract ([../../docs/reference/builder-pattern.md](../../docs/reference/builder-pattern.md)). ## When to use When the user asks to add, scaffold, author, or improve an MCP server (tools, resources, or prompts via the Model Context Protocol) for a plugin. ## create mode 1. Brief interview: server name (kebab-case), transport (`stdio` or `http`), the `command` plus `args` (stdio) or the `url` (http), and any secrets as an env-var NAME (never an inline value). Skip the interview if these are already in context. 2. Author or extend the root `.mcp.json`: add the server under `mcpServers`. Copy `templates/mcp.json` if the file does not exist yet. 3. Register the server in `library.json` `components.mcpServers` as `{ name, version, tier, status }`. 4. Wire the per-target pointer: run `node scripts/generators/gen-manifest.mjs <plugin-root> --write --target=all`. Each native manifest gains `"mcpServers": "./.mcp.json"`.