KilnKiln
Coming soon · on the roadmap

An API and MCP server for the site your AI built.

Kiln already lets people edit a static site by clicking it. The next step is letting tools and AI agents read and change that same content programmatically. Scoped to the exact fields you allow, sanitized on the server, and every change committed to your own GitHub repo where you can review or undo it.

Ask for early access See how it works

Two ways in. Same content, no new database.

Your page already declares what's editable, with data-cms tags. That doubles as the schema, so there's nothing extra to model. Point either interface at a page and you get its fields.

For code

The REST API

Read a page's fields as JSON, write field-level edits back, list history, add items to a repeating list. Authenticated with a per-site token that you scope like an editor: certain pages, certain fields, read-only or read-write. Wire it into a script, a cron job, a form handler, or a Zapier step.

For AI

The MCP server

Connect Kiln to Claude, Cursor, or any assistant that speaks MCP. The agent can list a page's fields, read them, and propose edits. "Mark us closed on the 4th" becomes a real edit to your hours, and the assistant hands you back the commit link.

The page is the interface.

A rough sketch of the shape. Read the fields, change one, and the write becomes a commit that your host redeploys, the same pipeline every click-to-edit change already flows through.

# Read what's editable on a page
GET  /api/v1/sites/you/your-site/pages/index.html/fields
→ { "hero_headline": { "value": "Fresh sourdough daily", "kind": "text" },
    "hours":         { "value": "Mon–Sat 7–3",         "kind": "text" } }

# Change one field — it becomes a Git commit
PATCH /api/v1/sites/you/your-site/pages/index.html
      { "edits": [{ "key": "hours", "html": "Closed July 4th" }] }
→ { "committed": true, "commit": "https://github.com/you/your-site/commit/9f2c…" }

Illustrative — the exact shape may change before launch.

What people would use it for.

The common thread: small, recurring content changes that are too minor to hire for and too frequent to do by hand.

1

Set-and-forget updates

"Every Monday, update the specials from this spreadsheet." An agent reads the sheet, writes one field, and commits. You review it, or let it publish.

2

Sync from a source of truth

Pull events from a calendar or products from a database into the page. Kiln stays the presentation layer, with no build step and nothing to keep in sync by hand.

3

Edit with your AI assistant

Tell Claude or Cursor to change the copy, swap a photo caption, or add a blog post. It edits the real page and shows you the commit.

4

Bulk changes across pages

Add a seasonal banner to forty location pages, or update a phone number everywhere, in one reviewable batch instead of forty clicks.

5

Publish from other tools

A form submission, a webhook, or a CI step updates a field. Kiln becomes something the rest of your stack can write to.

6

Read your content anywhere

A native app, a second site, or an email newsletter reads a page's fields as JSON. The page is both the website and the data source.

Write access you can actually trust.

Giving a script or an AI the keys to your website is only sensible if it's boxed in. Kiln's API inherits every guardrail the editor already enforces.

Scoped

Only the fields you allow

A token can be limited to a single field on a single page. Even a confused or misused agent can't touch the rest of your site, your menu, or your config.

Sanitized

No scripts, ever

Every write is checked on the server, not just in a browser. An agent can't slip a <script> or a tracking pixel into a page, no matter what it sends.

Reversible

Every change is a commit

Nothing is a silent database write. Each edit is a Git commit with a name on it, so you can review it, diff it, or roll it back in one click.

Where this is headed.

Honest about the order. The MCP connector comes first because it's the most useful and the most fun to try.

First

MCP server

Connect Kiln to your AI assistant and edit a live site end to end. Free to use, listed where agent builders look.

Next

REST API + SDKs

The HTTP endpoints above, plus small JavaScript and Python clients and a couple of ready-made recipes (sync from a sheet, sync from a calendar).

Then

Scoped tokens & automations

Issue and revoke scoped API tokens from your dashboard, schedule recurring syncs, and connect Zapier and GitHub Actions.

Later

A recipe library

Share and install ready-made automations, the same place plugins will live.

What it'll cost.

The plan is simple: reading is free, and every plan includes a monthly allowance of writes, enough for personal automation and for trying it with your AI. If you self-host, you run your own worker, so there's nothing to meter. Heavy, always-on automation, multiple scoped tokens, scheduled syncs, and the integrations will live on a paid tier for people automating at scale. The MCP connector itself will always be free. Nothing here is final, and none of it changes today's plans.

Questions, early.

Is any of this available now?

Not yet. This page describes what's coming so you can tell us whether it fits what you're building. Editing by clicking the page, inviting editors, and the members area all work today.

Is it safe to let an AI edit my live site?

That's the whole design. A token is scoped to specific pages and fields, every write is sanitized on the server so scripts can't get in, and each change is a Git commit you can review or undo. An agent can't reach anything you didn't hand it.

How fast do changes go live?

A write is a commit, and your host rebuilds from it, usually within about a minute. It's built for content that changes through the day or the week, not for a live data feed that updates every second.

Do I need a database or a schema?

No. Your page's data-cms tags already say what's editable, and that's what the API reads and writes. Same content, same repo, no new moving parts.

Will it work if I self-host?

Yes. Kiln is open source, so the API runs on your own worker. You bear the compute, so there's nothing for us to meter.

How do I get early access?

Email [email protected] and tell us what you'd automate. That genuinely shapes what we build first.

AI builds the site. Kiln keeps it current.

If you're building agents or automations that need a safe place to write to a real website, we'd like to build the right thing with you.

Ask for early access