Yichus / Reference / API MCP tools

api_deploy

If api_verify is proven under the declared topology, generate the Yichus API engine JavaScript (handlers + Principal injection + DB IO). Refuses when any property is violated or blocked, and when a property named in require is not proven. The refusal says what to change; instances: 1 is offered only for properties it changes, never for lost-edits, which is fixed with a version check. The emitted HTTP server refuses to listen unless YICHUS_AUTH is jwt (JWKS), clerk-api-key (API keys checked with Clerk via CLERK_SECRET_KEY), proxy-header (X-User-Id plus YICHUS_TRUST_PROXY_AUTH=1), public (only when every route is a public_route), or dev (YICHUS_DEV_AUTH=1). The engine also serves its routes as MCP tools at /mcp, so an agent can call the deployed API.

Kind: Deploy. Family ship: MCP servers list it once api_tools opens that family. Origin: Yichus/Mcp::catalog.

CLI: yichus api deploy — the same engine generation; the CLI writes the file, the tool returns it.

Parameters

Read the result according to this tool’s scope: static checks, bounded execution checks, and descriptive diagrams answer different questions. A successful call is not a general approval of the program. The safety and permissions guide compares the checks and provides editable ownership, guard, and role examples.