# alchemy.new

> alchemy.new deploys curated, versioned Alchemy packages into your own cloud account in one click. Cloudflare first; AWS and other providers follow.

alchemy.new is not affiliated with Alchemy at alchemy.run. It uses Alchemy as the deployment engine.

- Registry: https://alchemy.new/
- Human docs: https://alchemy.new/docs
- MCP endpoint: the API base URL plus `/mcp`. The web app reads that base from `VITE_API_URL`. The deployed base is the stage API Worker `workers.dev` URL.
- Project manifest schema: https://alchemy.new/schema/v1/project.json
- Full agent guide: https://alchemy.new/llms-full.txt
- Alchemy.run docs: https://alchemy.run

A package is a GitHub release or an npm package version. Each release ships `alchemy.new.jsonc` at its root and the Alchemy entrypoint it names; alchemy.new reads both from the release, never from a branch. Container images must be prebuilt and referenced by digest with `image`; alchemy.new copies them into the deployer's Cloudflare registry and never builds them. Every required parameter has a `default` or a `generate` rule, so each listed project deploys in one click. The publisher skill at `.agents/skills/publish-to-alchemy-new/SKILL.md` writes the file and prepares the release. Do not present a deploy link (`?github=owner/name` or `?npm=package`) as working until a release that contains the file is published. Then the skill asks before any registry upload. Share links carry safe form state only. Provider credentials and secret parameters never appear in URLs.