A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
0 ★ · luno-cms/mcp · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository luno-cms/mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
**Agents BUILD / OPERATE. Humans REGISTER / GOVERN. Applications CONSUME.** LUNO is a hosted backend platform — not a website builder, not an open-source CMS, and not an MCP server product. MCP is how your agent connects to LUNO. CMS and forms are capabilities; the product category is **AI-era Backend Platform**. | | | |---|---| | **BUILD** | AI agents define schemas, forms, and backend structure via blueprints and templates. | | **OPERATE** | Agents read and change content, media, auth settings, and other backend resources. | | **GOVERN** | Humans control production through scoped agent keys, approval workflows, publish gates, and safety controls. | Quick start Works with **Claude Code**, **Cursor**, and **Codex**. Issue an agent key in the LUNO Console → **MCP / API / Hook** → **API / MCP**. > **Glama / MCP directory:** “Install Server” requires a hosted API key and may show *This server cannot be installed*. Use npx -y @luno-cms/mcp setup instead — see Quick start (recommended) below. Production safety by design - **Scoped agent keys** — restrict to content-only or full backend access - **Human approval** — keys without publish permission stop at review (pendingHumanApproval) - **Destructive-action protection** — agents cannot hard-delete; archive requires confirmation - **Dry runs & confirmation tokens** — preview schema changes before applying - **Idempotent operations** — safe retries after timeouts - **Audit trail** — agent activity and audit logs in Console Agent-readable by design MCP schemas and tool descriptions were redesigned for agent readability. In a blind test, the same backend task went from **142 tool calls to 11**, with **0 errors** — application behavior unchanged. MCP Resources (#90) Static **Resources** (resources/list, resources/read) ship agent-readable guides without Admin API calls: | URI | Topic | |-----|--------| | luno://forms/field-types | Field types + snapshot shapes | | luno://content/schema-guide | Form Set / entry / revision hierarchy | | luno://publishing-guide | Draft → publish, can_publish | | luno://permissions | Scopes, blocked actions, archive token | | luno://api-reference | Tool cheat sheet (not full OpenAPI) | Inventory: docs/RESOURCES.md. Live per-tenant schema: get_form_set_schema tool. --- - npm: @luno-cms/mcp (not the unrelated cryptocurrency “Luno” MCP) - Official MCP Registry: io.github.luno-cms/mcp - Glama: luno-cms/mcp - mcpservers.org: luno-rest · - Source: github.com/luno-cms/mcp - Site: luno.rest · Docs: doc.luno.rest Directory checklist: docs/DISCOVERY.md **Product docs (EN):** AI Agents · doc.luno.rest **Product docs (JA):** AI Agents --- Quick start (recommended) From your **site repository root**, pick **one** AI agent and run setup (Claude Code / Cursor / Codex). The CLI opens the browser to confirm. Do not paste a key into the agent chat. Use --key or --no-browser only when you cannot use the browser. | Choice | What gets written | |--------|-------------------| | Claude Code | .claude/skills/luno/ + .mcp.json | | Cursor | .cursor/skills/luno/ + .cursor/mcp.json | | Codex | .agents/skills/luno/ + .codex/config.toml | Shared: .agents/luno/{dev,stg,prod}.env (keys; gitignored). Public default is **prod** (luno-prod). dev / stg stay on disk for explicit setup --env stg / run stg / env switch stg. Then: 1. Open the project in the chosen agent 2. Approve workspace trust / MCP if prompted 3. Ask: List the form sets on this LUNO, or draft one entry. Don't publish or change the schema. Later: teammates run npx @luno-cms/mcp login. Use --env stg only if you have access. **Verified clients:** Claude Code / Cursor / Codex (Golden Path E2E). Post-setup notes by client | Client | Notes | |--------|-------| | Claude Code | If tools are missing, reconnect (/mcp) | | Cursor | Settings → MCP: enable luno-prod. Start a new Agent chat if needed | | Codex | Project .codex/config.toml (with cwd) plus home config: Codex prefers **~/.codex/config.toml**, so setup may offer codex mcp add (with LUNO_PROJECT_ROOT). Check: codex mcp list (luno-prod, etc.). First MCP tool calls may need **approval**. Prefer **luno-prod** | /luno is an optional shortcut after setup. It is not required, and it must not ask for a key.