One registry, four surfaces
Define a tool once. Wove derives the REST API, the MCP server, the OpenAPI spec and the audit log from it.
v0.1.0 is out — the first tagged release
The CMS your
The CMS your
agents can
actually use
Every publishing action in Wove is a typed, permissioned, audited tool. People use it through a modern admin. Agents use the same tools over MCP. Nobody gets a second-class API.
Apache-2.0 · Bun 1.2 · SQLite · one container
79Typed tools
13Block types
4Site templates
5AI providers
1Container
0JS on your pages
The whole loop
Write. Build.
Automate. Review.
A complete CMS — posts, pages, media, menus, SEO, redirects, collections, roles — plus the agentic parts nobody else ships in core.
Write
- Posts in Markdown, with a WYSIWYG editor and a raw-Markdown toggle
- Drafts, scheduling, revisions, trash and restore, autosave recovery
- Draft a post or rewrite a selection with AI — your key, your model
Build
- 13 designed section blocks — hero, features, FAQ, stats, gallery and more
- Drag to reorder, undo/redo, property forms generated from each block schema
- Four site templates carry design, menus and pages as one JSON file
Automate
- Point any MCP client at Wove and it discovers every tool, typed and described
- The in-admin site chat turns a request into a reviewable plan with diffs
- A real scheduler publishes what's due, audited as
system
Review
- Admin, editor, author and contributor, with ownership enforced per tool
- Contributors submit, editors approve — agents use the same pending queue
- An audit log of who did what, through which channel, on every mutation
What's in the box
A complete CMS,
not a demo
Agents get keys, not passwords
Scoped agent identities, enforced at the tool boundary, attributed line by line in the audit log.
Leave WordPress in one job
Point Wove at a WXR export: posts, media, menus, SEO. Gutenberg becomes clean Markdown. Re-runs are idempotent.
A site look is just JSON
Templates carry design, menus and pages as data. Four built-ins, live preview, import and export.
Bring your own AI key
Anthropic, OpenAI, Google, xAI or anything OpenAI-compatible. Metered, encrypted at rest, never locked in.
Self-host in one container
Bun and Hono on SQLite. No database server, no PHP. docker compose up and you own the whole stack.
Watch an agent work
One prompt.
Four tool calls.
Nothing ships unreviewed.
This is an MCP session against a Wove site. The agent never touches a database — it calls the same tools the admin calls, inside the scopes you gave its key.
Launch a pricing page and link it in the nav.
→ ai.generatePage { "prompt": "pricing page, three tiers", "slug": "pricing" }
✓ page draft created · 6 blocks · validated against the block schema
→ block.validate { "blocks": [ hero, stats, faq, cta, … ] }
✓ ok · 0 errors
→ menu.set { "location": "primary", "items": [ …, { "label": "Pricing", "href": "/pricing" } ] }
✓ menu updated · primary · 5 items
→ post.publish { "id": "pg_8f21" }
✎ awaiting review · key scope is content:write, not content:publish
Queued in Content → Pending review. An editor approves it, and every line above
is already in the audit log — attributed to launch-bot, via MCP, with its arguments.Get started
Running in
about a minute
Deploy the single container, or clone the repo and run it locally. No database server, no PHP, no build step for the public site's HTML.
DeployDocker
export WOVE_SECRET=$(openssl rand -hex 32)
export WOVE_SITE_URL=https://your-domain.example
docker compose up -dCore, the admin at /admin and the public site behind one port. Update with docker compose pull && docker compose up -d.
Connect an agentmcp.json
{
"mcpServers": {
"wove": {
"url": "http://localhost:4000/mcp",
"headers": {
"Authorization": "Bearer wove_…"
}
}
}
}In the admin: Agents → New agent, pick scopes, copy the key. Full guide in the README.
Questions
The honest answers
Is Wove free?
Yes. Wove is Apache-2.0 and the open-source core is complete on its own — self-host it forever with no feature gates. A hosted edition at usewove.com is planned for zero-ops hosting, managed agent access and optional metered AI; it adds operations and tenancy, never features. AI is bring-your-own-key, so any model spend is yours and goes to your provider, not to us.
Do I need to know Markdown?
No. Posts are stored as Markdown, but you write them in a WYSIWYG editor — with a raw-Markdown toggle if you want it. Pages aren’t Markdown at all: they’re typed block documents you assemble in a visual builder, or generate from a prompt.
Can I migrate from WordPress?
Yes. Export everything from WordPress (Tools → Export → All content) and import the WXR file in Wove. Posts, pages, media, tags, menus, featured images and Yoast/RankMath SEO come across as a background job with a per-item report. Media is downloaded through the normal pipeline so it gets WebP renditions, links and image URLs are rewritten, Gutenberg markup becomes clean Markdown, and re-runs are idempotent. Unsupported shortcodes and missing attachments are reported as warnings, never fatal.
Which AI providers does it support?
Anthropic (Claude), OpenAI (GPT-5 family), Google (Gemini), xAI (Grok), and any OpenAI-compatible endpoint — Ollama, LM Studio, OpenRouter. You bring the key; it’s encrypted at rest and never returned by the API. Every call is metered — tokens, model, who, through what — so you can see usage. Wove records it; it never prices it.
How do agents connect?
In the admin, create an agent, pick its scopes (content:write, ai:use, …) and copy its key. Point any MCP client at /mcp with that key as a bearer token and it discovers every tool the admin has, each with a JSON schema and a description. Anything that doesn’t speak MCP can POST to /api/tools/<name> instead. Either way, scopes are enforced at the tool boundary and every call lands in the audit log.
It's time
to leave
WordPress
Clone it, run it, point an agent at it. If you don't like it, you still have every post you imported — in Markdown, on your own disk.