Every WordPress page builder asks you to make the same trade: build fast now, and accept that your pages live inside a proprietary format you can never fully leave. Shilpi is my attempt to remove that trade entirely.
Open the database behind a typical builder page and you find serialised arrays, base64 blobs, or shortcode soup. It renders fine — until you want to move to a different tool, hand the markup to a developer, or let an AI agent work on it. Then you discover you never really owned the page. You owned a licence to render it.
Shilpi is an AI-native WordPress theme and visual builder that stores every page as three plain fields: HTML, CSS and JavaScript. You edit them on a visual canvas. And because they are just open web standards, an AI agent can read and rewrite them — which is why Shilpi ships 34 scoped MCP tools that let Claude Code, Cursor, or any MCP client build your entire site.
Key takeaways
- No proprietary format. Pages are stored as readable HTML, CSS and JS — leaving Shilpi means copying markup, not rebuilding a site.
- Whole-site AI control. 34 MCP tools with OAuth let an agent create pages, templates, styles and menus — not just suggest copy inside one block.
- Batteries included. Forms with stored submissions, native SEO metadata, accessible carousels, WooCommerce and ACF support — no plugin stack required.
- One-time pricing from $25. Stop paying and the AI layer switches off; the builder and your published pages keep working, with no watermark.
A page is three fields. That is the whole idea.
Shilpi does not invent a storage format. Every page, template and reusable part is exactly this:
Semantic markup. Real <section>, <article> and heading tags — the structure a screen reader and a search crawler both expect.
A stylesheet you can read, with design tokens that carry four responsive breakpoints each.
Page-scoped behaviour. No global bundle loaded on every request just because one page needed a slider.
You still build visually. The canvas gives you 83 native responsive elements, a structure tree, and a live preview. But what gets saved is the thing you would have written by hand if you had the time.
Why storing plain HTML changes everything downstream
This is not a purity argument. It has four practical consequences.
You can actually leave
Migrating off most builders means rebuilding every page. Migrating off Shilpi means copying markup into whatever comes next.
Developers can read it
Hand a page to a developer and they see HTML, not a settings object. Code review becomes possible.
AI agents can edit it
An LLM is excellent at HTML and CSS. It is poor at guessing a proprietary schema. Plain markup is what makes the MCP layer reliable.
Nothing loads that you did not ask for
Page-scoped CSS and JS instead of a builder framework injected site-wide on every request.
The MCP layer: your agent already knows how to build this site
Most “AI website builders” give you a text box that writes copy inside one block. Shilpi exposes the site itself.
Connect Claude Code, Cursor, or any MCP client over OAuth and the agent gets 34 scoped tools — create and update pages, build headers and footers, manage design tokens and global classes, edit menus and taxonomies, upload media, read and write SEO metadata, run WooCommerce operations, and handle Code Hub snippets.
You can also import downloadable skills that teach the agent Shilpi’s conventions, so it writes markup that matches how the theme actually works instead of guessing.
The workflow
- Describe. Tell the agent what you want — a pricing section, a new archive template, a rebuilt header — or build it yourself on the canvas.
- Review. The output lands in the structure tree with a live preview. You read the markup before anything ships.
- Publish. It goes live as a normal WordPress page, with normal WordPress URLs and normal WordPress SEO.
What is built in, so you do not install a plugin for it
| Capability | What you get |
|---|---|
| Forms | Stored submissions in WordPress plus SMTP delivery — no separate form plugin |
| SEO metadata | Title, description, canonical, robots and social cards handled natively; works alongside Yoast or Rank Math if you prefer those |
| Carousels & sliders | Accessible by default, keyboard and screen-reader friendly |
| Templates | Headers, footers, singles, archives, search, 404, loops and reusable parts |
| WooCommerce | Store integration from v1.7 onward |
| ACF | Bind custom fields into your markup |
| Code Hub | Global CSS, JS and syntax-checked PHP snippets in one place |
| Design tokens | Colours, typography and spacing with four responsive breakpoints each |
Permissions you can close
Giving an AI agent write access to a live WordPress site is a real decision, and it deserves real controls. Shilpi’s model is straightforward:
- OAuth sign-in — no passwords stored anywhere.
- Revocable per app — disconnect any client and its access ends immediately.
- Temporary PHP access — PHP execution is a capability you open deliberately, with a visible counter, and it closes again.
- Syntax-checked snippets — PHP is validated before it can take a site down.
Shilpi vs a traditional widget builder
| Widget builders | Shilpi | |
|---|---|---|
| Storage | Proprietary serialised data | Plain HTML, CSS, JS |
| Leaving | Rebuild every page | Copy your markup |
| AI scope | Copy suggestions inside one block | Whole-site control via 34 MCP tools |
| Forms & SEO | Usually extra plugins | Native |
| Assets | Framework CSS/JS site-wide | Page-scoped |
| Pricing | Typically annual, renews forever | One-time from $25, or yearly from $10 |
Who Shilpi is for
Freelancers
Ship client sites faster without handing the client a format they can never move away from.
Agencies
Shared libraries across 25 production sites on the Agency plan, plus unlimited staging.
Developers using AI
You already work in Claude Code or Cursor. Now the WordPress site is in the same loop.
Anyone who reads their own markup
If you have ever opened DevTools and winced at what your builder emitted, this is for you.
Pricing
One-time licences, no forced renewals. A yearly option starts at $10/year, and every plan carries a 30-day refund policy.
Frequently asked questions
What happens if I stop paying?
The AI layer switches off. The builder, your templates, your forms and every published page keep working exactly as they are, with no watermark and no downgrade.
Can I paste existing HTML into Shilpi?
Yes. Paste body-only HTML and it renders on the canvas immediately, ready to restyle. This is usually the fastest way to migrate a page from somewhere else.
Do I need an SEO plugin?
Not for the basics. Shilpi handles title, description, canonical, robots and social cards natively. If you already run Yoast or Rank Math, they work alongside it.
Do I need to know how to code?
No. The visual canvas covers normal site building. Knowing HTML and CSS simply means you can go further, because the underlying code is always available to you.
Which AI tools does the MCP layer work with?
Any MCP client — Claude Code and Cursor are the ones most people use. Connection is over OAuth, and you can revoke any client at any time.
Is it safe to let an AI agent edit a live site?
Access is scoped and revocable, PHP execution is a temporary capability with a visible counter, and PHP snippets are syntax-checked. The recommended workflow is describe, review the markup, then publish.
Does Shilpi require other plugins?
No. It runs on standard WordPress hosting with no required plugins. WooCommerce and ACF are supported if you use them.
Build it visually. Own every line.
A WordPress builder that stores real HTML, CSS and JS — and hands your AI agent the keys to the whole site. From $25, one time, with a 30-day refund.
