LUNO
LUNO là backend kỷ nguyên AI dành cho con người (Console) và agent (MCP): danh tính, nội dung, biểu mẫu, lưu trữ và API công khai — không phải trình xây dựng website.
Tài liệu
Why now
AI agents are not only here to write code.
They read data, operate services, execute changes, and finish work.
That shift needs a production backend agents can actually operate — with humans still governing what ships.
import { createClient } from '@luno-cms/mcp';
export async function initBackend() {
return createClient({ env: 'production' });
}
TERMINAL
- $ npx @luno-cms/mcp setup
- Step 1/3 · Detecting Cursor / Claude Code / Codex
- Step 2/3 · Writing MCP config + skills
- Step 3/3 · Connecting to LUNO staging
- Success! LUNO MCP server ready
Agent Human governance Schema API / MCP Auth Publish Prod
- BUILD AI builds the backend Hand over requirements. Agents create schemas, forms, content structures, and other backend resources.
- OPERATE AI runs the backend Through MCP or APIs, agents read, create, update, revise, and publish backend resources.
- GOVERN Humans control production Permissions, review, approval, and audit — humans decide what agents can change and what ships.
mcp · setup
live
Connect Cursor, Claude Code, or Codex with @luno-cms/mcp — the agent interface for schema through publish.
mcp · setup
- $npx @luno-cms/mcp setup
- →1) Claude Code 2) Cursor 3) Codex
- ✓Wrote.cursor/mcp.json + skills
- ✓MCP server luno-stg ready
- Cursor
- Claude
- Claude Code
- Codex
- OpenAI
- Copilot
- GitHub
Edit and publish content in place
Entries, fields, and publish flow — a human admin surface you can use as-is.

- 01 Scoped agent keys Agents work only inside scoped keys and permissions — authority is bounded by design.
- 02 Human approval Approval and publish boundaries stay with the org. Review before changes go live.
- 03 Audit trail See who published what. Agent actions land on the same operational trail as humans.
Production Backend
Let AI agents run your backend.
Hand your AI coding agents a production backend. Content, forms, auth, storage, APIs, and publishing are already built into the platform — no backend to assemble from scratch.
Infrastructure
Stop building the infrastructure.
The servers, runtime, database, mail, and secure access are already in place.
Identity & Access
Stop rebuilding identity.
Authentication, authorization, MFA, SSO, and organizations are ready from the start.
Content & Data
Stop rebuilding content systems.
CMS, forms, data, storage, and search are already part of the backend.
Application
Stop wiring backend services together.
APIs, webhooks, workflows, jobs, and notifications work together out of the box.
Security
Stop adding security afterward.
Access control, audit logs, encryption, secrets, and policies are built into the foundation.
Delivery & Operations
Stop maintaining the backend.
Deployment, environments, monitoring, logging, and backups are handled by the platform.
Infrastructure Identity & Access Content & Data Application Security Delivery & Ops
Traffic · Firewall · Updates
live
-
Traffic Production load
-
Firewall Blocked at the edge
-
Updates Patches applied for you
-
01 Security response Don’t bolt defense on later. Access control and ops stay in the foundation.
-
02 Firewall The edge absorbs the noise first — so the app surface stays thin.
-
03 Updates Leave breaking plugin updates behind. The platform carries the patches.
-
142 → 11 tool calls
Same backend task with improved MCP schema — 142 calls and ~236 minutes down to 11 calls and 12.8 minutes.
-
12 → 0 errors
Agent operations on a structured backend surface — fewer round trips, fewer failures, production-ready results.
-
Human governance
Scoped keys, approval, and audit — agents operate fast; humans keep production under control.