The content backend built for humans and AI agents

Structured pages, clean REST APIs, and a production MCP server in one stack. Skip the vendor lock-in setup. Ship your content-backed product this week.

App screenshot
BUILT-IN MCP SERVER

Your content is agent-ready from day one

Garchi ships with a production MCP server and 20+ tools. AI agents create pages, manage data, reorder sections, and upload generated assets — working on your real schemas, not guessing from scraped docs.

PLUG INTO YOUR AI TOOL PUBLISH CONTENT BY CHATTING REAL SCHEMAS, 20+ TOOLS WORKS WITH CHATGPT WORKS WITH CLAUDE ANY MCP-COMPATIBLE AGENT

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...

using list-space-tool

using create-data-item-tool

Done — I created the blog article in the Website space. Details: Title: Understanding MCP Servers Slug: understanding-mcp-servers Item ID: 460 Categories: AI and MCP Metadata added: author: OpenAI date_published: 2026-04-08

This isn't a chatbot wrapper. The agent reads your actual content model, calls real API tools, and writes real records — same schemas your team uses in the dashboard.

Set up your content backend in one command

Starter kits for the frameworks you already use. Or skip the kit and call the REST API from any stack.

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

Built for founders who ship One backend for content, structure, and speed

Stop duct-taping admin panels, markdown files, and database tables. Garchi gives you a real content backend so you can focus on your product.

Content models that grow with your product

Model pages with reusable sections. Extend data items with custom metadata. No migrations when your blog post suddenly needs an author bio, or your product page needs pricing tiers.

Your team and your codebase, in sync

Editors work in the dashboard. Developers work in code. Separate workspaces per project, granular permissions, no Slack threads about who broke production.

AI workflows that run on real schemas

The MCP server gives agents governed access to your content model — same tools, same permissions, same audit trail your team uses. Not a chatbot bolted on the side.

Multilingual without the plugin tax

Every page and section supports language-specific content natively. Pick your languages per workspace. Manage translations in one place.

Secure, cloud-hosted, and always available

Your content and media are stored on AWS infrastructure with encrypted API keys and signed webhook delivery. Focus on your product - Garchi handles the uptime.

Fast APIs, any stack

REST endpoints, 600 requests per minute, Node.js and PHP SDKs if you want them. No vendor lock-in, no GraphQL learning curve unless you ask for it.

One content backend. Whatever you're building.

Garchi manages structured content and stays out of the way. Most teams end up using it across three big surfaces:

🚀

Use Case One

Product content

SaaS dashboards, AI products, marketplaces, internal tools — anything with a content model that needs to live somewhere other than your app database.

📣

Use Case Two

Marketing surfaces

Landing pages, multi-region sites, campaign pages, microsites. Edit copy without a deploy. Ship variants without a CMS migration.

📚

Use Case Three

Content operations

Blogs, knowledge bases, multilingual documentation, editorial workflows. Structured enough to query, flexible enough to write in.

Garchi CMS Dashboard Preview

Or all three, in one workspace. Garchi doesn't care what you call it — it's just structured content with an API.

Flexible content models that fit your product, not the other way around

Your blog post has authors. Your product page has pricing tiers. Your case study has industry tags. Garchi's data items start with a clean schema and extend with whatever metadata your product needs — no migrations, no rigid templates.

Works with your stack

Your CMS should fit your architecture. Not replace it.

Garchi manages content. You choose everything else - your framework, your database, your hosting, your auth.

Stack-agnostic by design

Using Next.js? Laravel? Rails? Go? It doesn't matter. Garchi exposes a REST API. If your stack can make an HTTP request, it can use Garchi. No framework dependency, no SDK requirement.

Set up in minutes, not days

Sign up, create a space, add your content, grab your API key. The starter kits get you running in one command. The API docs are complete and current. No onboarding call required.

Built to grow with you

Start with one space and a handful of items. Scale to multiple workspaces, thousands of records, webhooks, and agent-driven content workflows — same platform, no replatform.