Works with AI agents and tools

Your content, out of the code. Edited by you or your AI.

Whether you coded your app yourself or built it with an AI coding tool, Garchi keeps its pages, posts, product data, images and translations in a hosted CMS. Your app reads them over an API. You and your team edit them in a dashboard, or ask your AI to, and nothing goes live until you publish.

No CMS to host. No admin panel to build. No redeploy for a copy change.

Free Sandbox plan · no card required

Draft · Review · Live
Your AI drafts it. You publish it. No redeploy.

Your app is live. The changes keep coming.

Copy, prices, images and posts change every week, long after the code is done.

  • You want to try a new headline on the landing page.
  • A product price is wrong.
  • There is a new blog post to publish.
  • The hero image is out of date.
  • A customer asks for a German version.
  • Marketing rewrote the pricing copy on Friday.

Today each of those means a code change and a redeploy, or re-prompting your coding agent and checking what else it touched. In Garchi it's a quick edit in the dashboard, or one sentence to your AI.

How it works

Your code declares the fields. Garchi holds the values.

Your components say what they need, whether you wrote them or your AI did. The same fields show up in Garchi, where you, your team or your AI agent fills them in.

StepItem.tsx — your code, your repo
StepItem.tsx
type Props = {  step_number?: string;  title?: string;  description?: string;  icon?: string;  [x: string]: any;}; export default function StepItem({  step_number,  title,  description,  icon,  ...props}: Props) {  return ( … );}

It declares the fields it needs. Nothing else.

Garchi — your content, edited by anyone
The Garchi section editor showing icon, description, step number and title fields filled in, next to the page they render on.

Those same fields, filled in, with the page updating beside them.

The same four fields, in both places step_number title description icon
  1. Keep the app you built

    Your framework, your hosting and the code you or your AI wrote stay as they are. Garchi sits behind them and replaces none of it.

  2. Move the content out

    Text, images and product data leave the repo and live in Garchi, so changing them never touches the code.

  3. Change it from anywhere

    Update a headline, fix a price or publish an article from the dashboard, or ask your AI to. No pull request and no deploy.

Your team
uses the dashboard.
Your app
reads the REST API.
Your AI tools
use MCP.

All three work on the same content. Use the dashboard, the API or MCP depending on the task.

WORKS WITH YOUR AI TOOLS

Bring the AI tools you already use

Connect Claude, ChatGPT, Claude Code or Cursor and it works on your real content: drafting pages, writing posts, updating products, reordering sections and using the images already in your space. Setup is a URL and one approval.

MCP is the open standard these AI tools use to connect to other software. Garchi's MCP server is built in, so you have nothing to code. Everything the agent writes waits as a draft until you publish it.

CONNECT YOUR AI CLIENT WORKS ON YOUR REAL CONTENT MODEL 20+ TOOLS

YOUR AI AGENT

@Garchi CMS show me available spaces
Here are the available Garchi CMS spaces:
Blog space
Website
Create a blog article on MCP servers in Website space under the category AI and MCP

Thinking…

Reading your Website space

Writing the article as a draft

Done. I've drafted the article in your Website space.
Title: Understanding MCP Servers
Category: AI and MCP
Status: Draft, ready for you to review and publish

The agent reads your content model and calls the same operations your team uses in the dashboard.

Drafts and undo

Let an agent near your content. Not near your live site.

Let an AI edit your live site directly and one bad sentence reaches your customers. In Garchi its changes stay drafts until you publish them, and you can roll any of them back.

A list of pages in Garchi, each marked with a Draft badge.

You would rather see a change before your customers do.

Nothing goes live on its own

Everything an agent writes stays a draft. It reaches the public only when a person publishes it.

Restore points in Garchi listed by time, each labelled AI agent, with a Restore button.

You notice it days later, and nobody remembers what it said before.

Changes leave a trail you can walk back

Every change leaves a restore point for 30 days, labelled with who made it. Rolling back takes a click.

A draft preview banner above a page rendered on its own site, showing unpublished content.

Reading a diff doesn't tell you whether the page actually looks right.

See it on your real site first

Drafts render on your own frontend, visible to you and nobody else, until you are happy with it.

Last deploy 6 days ago
Last content change 4 min ago

Fixing one word means a pull request and a deploy.

Nobody deploys to fix a typo

Content lives outside your codebase. Whoever changes it, you ship code only when the code changes.

Also included Multilingual content per space Hosted, maintained and upgraded for you A REST API any stack can call Node.js and PHP SDKs Notes on your content that agents can read Separate spaces with per-space collaborators On Pro: review an agent session and recover it in one go

What's included

Everything your site needs behind it, already running

A dashboard for editing, an API for your app and a connection for your AI tools. We host and maintain all of it, so you can get back to your product.

Content you can manage without the code

Pages built from reusable sections, articles, products, categories, images and translations. Whoever owns the content can edit it, with no application code involved.

An API your frontend can rely on

Your application stays yours. Garchi serves its content over REST, with Node.js and PHP SDKs and starter kits for Next.js, Nuxt, SvelteKit and Laravel.

An MCP server you don't have to write

Claude, ChatGPT, Claude Code and Cursor reach the same content through Garchi's built-in MCP server. You have no agent integration to build or keep running.

Hosted and ready

No CMS server to run and no content infrastructure to maintain. Each project gets its own space, with its own content and collaborators.

Starter kits

Scaffold a connected project with one command

Starting a new project? Run one command yourself or hand it to your coding agent. Kits for Next.js, Nuxt, SvelteKit and Laravel, or call the REST API from any stack.

npx @lumenharbor/garchi-starter-kit -k next

Content modelling

Content models that fit your product

Your blog post has authors. Your product page has pricing tiers. Your case study has industry tags. Garchi's data items start with a base schema, and you add the metadata your content needs without touching your app's database.

Publishing

Publish without building another integration

Need something on LinkedIn, Instagram or Facebook? Draft it in Garchi, get it approved, then publish or schedule it from the same place as the rest of your content.

A social post in Garchi marked Draft, with its text, its LinkedIn destination and an attached image, beside an approval rail reading Written, Approved, Scheduled, Published.
A post waits as a draft until someone approves it. Every change to it is kept in the post's own history.

From draft to published

  1. Draft

    Write it, or let an agent draft it from content you already have.

  2. Approve

    Someone reads it and signs it off.

  3. Schedule

    Send now or set a time. Editing an approved post reopens the approval.

  4. Publish

    Garchi posts to each channel and records what happened on each one.

Your AI can draft a post and send it for approval. Approving, scheduling and publishing stay with you and your team.

Channels you can connect

  • LinkedIn — Company pages and personal profiles
  • Instagram — Business and Creator accounts
  • Facebook — Pages

Images and video both work. Every plan includes a number of publishes, and every post keeps a record of what was sent and what each channel did with it.

Keep the tools you already use

Already use a dedicated social platform? Keep it. Garchi handles straightforward publishing from your content workflow, and your existing tools carry on with engagement, analytics, listening and broader campaign management.

Built for

Solo builders, product teams and agencies

Whichever sounds like you, you start on the same free plan.

Building with AI

Keep the copy out of the generated code

You prompted the frontend into existence. Now every wording change means prompting again and hoping nothing else moves. Put the content in Garchi, and the same AI can still edit it through MCP.

Product teams and developers

Let non-developers change the site

Give marketing and content people somewhere to manage landing pages, articles and product copy. Developers keep the architecture and ship code only when the code changes.

Agencies and client projects

Hand the client the keys

Build the site, then hand the client somewhere to manage it. Paid plans include several spaces, each with its own content and collaborators, so clients never see each other's work.

The Garchi CMS dashboard showing a space with its pages and content items
Blogs, knowledge bases, marketing pages, product catalogues and multilingual docs all fit. If it's content rather than application logic, it can live in Garchi.

Product tour

See Garchi CMS in action

Start with one space. Add the rest when you need it.

Sign up, connect your AI tool and ask it to build your first page in Garchi. Sandbox is free, and the dashboard works just as well if you'd rather click.

Free Sandbox plan · no card required