Call any route, and set up agents in one command

myna api

The commands cover the management API, but never all of it at once. myna api calls the rest.

myna api '/projects/:project/entries?collection=posts'
myna api POST /projects/:project/change-sets --data '{"title": "Autumn refresh"}'
myna api DELETE /projects/:project/previews/:preview

The method is optional when it is GET, and a leading /v1 is accepted, so a path copied out of the API reference works unmodified. The response envelope is passed through whole.

--data takes inline JSON or @file, --header name:value repeats, and --include reports the status and headers on stderr. Errors render as problem details with the usual exit codes, and --json emits the same single versioned document as every other command:

myna --json api /projects/:project/releases | jq -r '.data.data[].releaseNumber'

--idempotency-key is opt-in. Sending one makes a request eligible for automatic retry, and only the caller knows whether replaying a particular call is safe.

The SDK has the same escape hatch:

const { status, headers, body } = await myna.raw("GET", "/projects/my-site/releases");

myna mcp install

myna mcp install          # every client detected on this machine
myna mcp list             # what is installed here, and what already has Myna
myna mcp uninstall

Claude Code, Cursor, VS Code, and Windsurf are written directly; Codex prints the TOML block to paste. --transport http configures the hosted server over OAuth, which stores no credential at all. --scope, --name, --key, --dir, --print, and --force are also available.

The credential never lands in a client's configuration file — most of those live in the repository. It goes to ~/.config/myna/mcp.json at 0600, where @myna-sh/mcp reads it. A server entry the command did not write stays as it is unless --force says otherwise.

myna skills install

myna skills install
myna skills list

Three skills — myna-change-sets, myna-schema, and myna-publishing — written to ~/.agents/skills and to any tool-specific skill directory that already exists. They cover the change-set workflow, schema deployment, and the publish gates.

They describe the workflow. Scopes, confirm: true, and the publish gates enforce it. A skill file that differs from the bundled version is reported and left alone; --force takes the bundled one.

Embedded images

An ast_ id counts as an asset reference wherever it appears in an entry's data, including inside a markdown or rich-text body, where it is part of a delivery URL rather than a whole field value.

Publishing an entry promotes every image it references. Orphan listings exclude those images, deletion is blocked while one is in use, and the altText collection policy covers them.

Upgrading

npm install -g @myna-sh/[email protected]

An entry published before this release promotes its embedded images the next time it publishes. Republish to pick them up.