mcpifylisted

# MCPify Turn an existing application's user-level capabilities into a narrow MCP interface, then take the approved server through packaging, deployment, discovery, client integration, publication, and operations. ## Select the mode Infer the mode from the request; if it is genuinely ambiguous, default to `analyze`. - `analyze`: inspect the repository, create or update `mcp-manifest.yaml`, and write an analysis report. Do not change application logic or add MCP runtime code. Read [analysis workflow](references/mode-analyze.md). - `generate`: implement only entries whose manifest status is `approved`. Read [generation workflow](references/mode-generate.md). - `audit`: inspect an existing manifest and MCP implementation without changing it unless the user separately asks for fixes. Read [audit workflow](references/mode-audit.md). - `test`: build and exercise the MCP integration safely. Read [test workflow](references/mode-test.md). - `package`: prepare a reproducible local package, container, MCPB artifact, or public remote-server metadata without publishing it. Read [release lifecycle](references/release-lifecycle.md) and [registry publication](references/registry-publication.md). - `deploy`: prepare or perform an explicitly requested deployment, including remote transport, authorization metadata, health checks, rollback, and gateway controls. Read [deployment](references/deployment.md). - `connect`: generate client/host configuration and verify discovery for a specified M