Anyone can put your files on a server. Blinki reads the site your AI built, works out which bits are the headline, the prices, the photos and the opening hours, and hands you an editor where you change them by clicking on them.
Free to build. £24.99 a month once it is live on your own domain.Made it with Claude, ChatGPT, Lovable or Bolt? Add Blinki as a connector, say yes when it asks to connect, and publish straight out of your editor. Nothing to install and no build step to learn.
Claude
ChatGPT
Cursor
Copilot
Windsurf
VS Code
Gemini
Replit
Lovable+ any other MCP clienthttps://blinki.co.uk/mcp
There is no pipeline to learn and nothing to install. The bit that matters happens after you publish.
Paste the Blinki endpoint into Claude, ChatGPT, Cursor or whichever tool you build with.
Make a key in your Blinki dashboard and paste it in alongside the endpoint. That is the setup done.
Tell your tool to publish to Blinki. It asks which business the site is for, and tells you the price before anything goes live.
Open the editor, click a headline or a photo, and type. You never have to go back to the AI to fix a price.
This is the part that is actually ours. Anybody can put your files somewhere. Reading a site written by a language model and working out which bits a shop owner will want to change is the hard part.
That is the whole difference. A site sitting on a host is a set of files: to change a word, somebody edits the code again. A site read by our engine has a panel of fields behind it, and the person who owns the business changes the word.
Published on your own domain, with the parts that usually cost extra somewhere else already in it.
This is the comparison that matters if you have built something with an AI tool and you are wondering where to put it.
| Blinki | A hosting provider | A site builder | |
|---|---|---|---|
| Takes a site your AI built | |||
| Publishes straight from the tool you built in | Sometimes | ||
| Turns the content into editable fields | |||
| You can change a price without touching code | |||
| Checks the site for broken links and missing alt text | |||
| Domain, mailbox and phone number on the same bill | Sometimes | ||
| You keep the design your AI actually made |
The skill is a single file that tells your AI how we read a site, so the build arrives already marked up and every part is editable the moment it lands.
A single markdown file you give to Claude, ChatGPT or whichever tool you use.
Headlines, prices, photos, hours and contact details all come through as fields.
If something is missing we tell you what and where before it goes live.
No going back through the code to make a word changeable.
Both halves, because the first half on its own is marketing.
This is a publishing platform for websites: pages, posts, products, forms. If your AI built you a booking system with user accounts and a database behind it, that is an application and it wants a different kind of host.
Marketing site here, application elsewhere, pointed at a subdomain, is a perfectly normal arrangement and plenty of people run exactly that.
The engine does not re-theme what you built. It reads the markup and adds an editing layer over the top, so the site that goes live is the site your tool made, down to the spacing.
That is the opposite of moving into a template builder, where you rebuild the design in their components and lose whatever was interesting about it.
Including the ones about leaving, because a page that will not answer those is hiding something.
A single address you paste into an AI tool once, which lets that tool talk to Blinki directly. After that you tell your tool to publish and it does, without you exporting files or dragging a folder anywhere.
Any tool that speaks MCP, which includes Claude, ChatGPT, Cursor and a growing list of others. If you build somewhere that does not, you can still upload the site the ordinary way and the engine reads it the same.
Not to publish, and not to edit afterwards. That is the point of the editor. You need enough to have got your AI tool to build something in the first place, which for most people is describing what they want.
Nothing to build. £24.99 a month, or £239.88 a year, once it is live on your own domain. Domains, mailboxes and phone numbers are separate and land on the same invoice.
Yes. Publish again and the new version goes live. Content you have changed in the Blinki editor is reconciled with the new build rather than thrown away, so an edit you made on Tuesday is not lost by a rebuild on Friday.
It tells you which part, and where, before anything is published. Usually it is a section that has content and layout tangled together. Hand the skill to your AI tool, ask it to fix that section, and republish.
No, and it is a fair thing to check. Hosting takes your files and serves them. This reads them: it works out which text is a headline, which is a price, which image is the hero, and what your opening hours are, and turns each into a typed field with its own editing control.
The test is whether the person who owns the business can change a price on a Sunday without you. On hosting they cannot. Here they can.
Yes, and you should. Buy one here from £12.99 a year and it is connected automatically, or point one you already own at us.
Both are read as collections, so posts and products are proper pages with their own addresses rather than rows in a database you cannot see. They are edited in the same place as the rest of the site.
No. The shop’s buy button points at your own payment link, so the money goes from your customer to you.
That is largely what it is for. You build, you publish, and the client gets a login that shows fields rather than code. Nothing they can type in a text field can break the page, because plain text slots refuse markup outright.
The site comes down, and your domain and your files are still yours. Export the site or point the domain elsewhere. We do not hold anything hostage.
No. It is monthly, and you can stop at the end of any month.
Connect once, publish whenever, and change it yourself afterwards. You only pay when it is live on your own domain.