MCP server
One config file away.
Tools for collections, entries, assets, change sets, previews, reports, and analytics. Publishing and deleting ask for confirmation first.
.mcp.json
{ "mcpServers": { "myna": { "command": "npx", "args": ["@myna-sh/mcp"], "env": { "MYNA_TOKEN": "myna_sk_…" } } } }
The agent drafts. You publish.
01
Agent drafts
Inside a change set. Nothing touches your site.
02
Myna validates
Against your schema. One preview link comes back.
03
You publish
Field-level diffs, then one click. Or send it back.
Every agent action is on the record.
- scoped keys
- Write permission never implies publish permission.
- attribution
- Every revision names the human, agent, or key behind it.
- immutable history
- Field-level diffs and one-click restore.
- previews
- A link to the real page, not a diff of JSON.
- audit activity
- One stream for humans, agents, keys, and the system.
- confirmation
- Destructive tools ask before they run.
More of Myna.
Change sets
Group a change, preview it, publish it at once.
Related entries and assets, one preview, one publish.
Read moreSchema as code
Collections are TypeScript in your repo.
The CLI shows the diff before it pushes. Types for your app come from the same file.
Read morePlatform
One API behind the dashboard, CLI, SDK, and MCP.
Nothing is dashboard-only.
Read more