Luno Cms MCP

Name: Luno Cms MCP
Author: luno-cms

作者：luno-cms版本 0.2.51i★ –i在你的电脑上运行

注册名称io.github.luno-cms/mcp

安装

概览

作者提供的说明（英文原文）

LUNO — AI-era Backend Platform (not Luno crypto). BUILD/OPERATE, REGISTER/GOVERN, CONSUME.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：LUNO_API_URL, LUNO_AGENT_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： LUNO_API_URL, LUNO_AGENT_KEY

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "luno-cms": {
      "command": "npx",
      "args": [
        "-y",
        "@luno-cms/mcp"
      ],
      "env": {
        "LUNO_API_URL": "your-value",
        "LUNO_AGENT_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add luno-cms --env LUNO_API_URL=your-value --env LUNO_AGENT_KEY=your-value -- npx -y @luno-cms/mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "luno-cms": {
      "command": "npx",
      "args": [
        "-y",
        "@luno-cms/mcp"
      ],
      "env": {
        "LUNO_API_URL": "your-value",
        "LUNO_AGENT_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "luno-cms": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@luno-cms/mcp"
      ],
      "env": {
        "LUNO_API_URL": "your-value",
        "LUNO_AGENT_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

LUNO_API_URL 必填 env
LUNO admin API base URL, e.g. https://api.luno.rest/admin
LUNO_AGENT_KEY 机密必填 env
Required secret. Agent API key (sk-agent-…) from LUNO Console → MCP / API / Hook → API / MCP

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 luno-cms 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32572 个服务器的 0%
发布到注册中心的时间比此分类中其他 32572 个服务器的 47% 更新
基础检查结果等于或优于此分类中其他 32572 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Luno Cms MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：LUNO_API_URL, LUNO_AGENT_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.51）于上个月进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, AvaHR

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

AvaHR

作者：avahr.com

Read hiring data and create inactive assessment and questionnaire drafts for human review.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

LUNO — AI-era Backend Platform

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

npx -y @luno-cms/mcp setup

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.

cd my-site

npx -y @luno-cms/mcp setup

→ lists agents found on this machine (or pass --agent claude|cursor|codex)

→ opens the browser to confirm (or --key / --no-browser)

→ healthcheck against production (https://api.luno.rest/admin)

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:

Open the project in the chosen agent
Approve workspace trust / MCP if prompted
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.

After a teammate clones (.mcp.json is there, keys are not):

npx @luno-cms/mcp login

or: npx @luno-cms/mcp login --key 'sk-agent-…'

login refreshes .agents/luno/ .env only. It does not rewrite MCP config. Use the same command for expired keys or 401. First-time machines still run setup.

Non-interactive:

npx @luno-cms/mcp setup --agent claude --yes --key 'sk-agent-…'

npx @luno-cms/mcp login --key 'sk-agent-…' npx @luno-cms/mcp env status

Explicit staging (internal / Benchmark / Partner only):

npx @luno-cms/mcp setup --env stg --key 'sk-agent-…'

npx @luno-cms/mcp run stg

Issue keys in Console → Settings → Agent API keys (per env / per site). Default scope full (content + form definitions). Use content to restrict to articles only.

Rate limits: per agent key to Admin API — 60 req / 60s (Free / Solo) or 300 / 60s (Standard+). Over limit → HTTP 429 + RATE_LIMITED + Retry-After. Console JWT traffic is not limited this way. Details: AI Agents rate limits.

Scope	When to use
full (recommended)	Articles + Form Set / Contact / Blueprint
content	Create / update / publish articles only
schema	Same privileges as `full` (compat)

Environment / CLI

Variable	Example	Description
`LUNO_API_URL`	`https://api.luno.rest/admin`	Admin API base (include `/admin`)
`LUNO_AGENT_KEY`	`sk-agent-…`	Agent API key

npx @luno-cms/mcp --version    # print package version (no MCP start)

npx @luno-cms/mcp # start MCP from env vars npx @luno-cms/mcp run prod # load .agents/luno/prod.env then start npx @luno-cms/mcp setup npx @luno-cms/mcp env …

Generated MCP configs use npx -y @luno-cms/mcp@latest run so reconnect fetches the newest publish (avoids a stale unpinned npx cache). Re-run npx @luno-cms/mcp setup (or edit mcp.json) if a site still has the unpinned spec, then /mcp reconnect — do not hand-bump a version pin. Confirm the running package with --version or get_mcp_runtime.

MCP server names: luno-dev / luno-stg / luno-prod

Cursor Plugin (optional)

For Cursor Marketplace / local plugin setup, see the LUNO Console onboarding. For normal site work, prefer npx @luno-cms/mcp setup above.

Multiple keys at once

One MCP entry = one key. Split by site or scope with different MCP server names. Active key limits depend on plan.

Resuming an existing project

get_project_overview — project summary + intentCapabilities (recommended first)
Contact / inquiry → create_contact_form (dryRun: true first). Content → match purposeLabels then a template
Then get_form_set_schema / list_entries as needed
Separate from greenfield Golden Path (builtin template → entry → publish)

Tools

Content (`content` scope and above)

Tool	Description
`get_project_overview`	Project summary + `intentCapabilities` (Contact vs Form Set) / nextMoves / Form Sets / Contact / Masters / storage / locales / public API
`get_tenant_schema`	Full project schema
`list_form_sets` / `get_form_set_schema`	Form Set list / definition (`get_form_set_schema` includes form-set `schema-context` + `snapshotShape.example`; selects may include `masterEntityKey` / public records URL)
`get_public_api_info`	Agent key `projectId` + public API base (entries / master-entities)
`list_entries` / `get_entry`	Entry list / detail
`create_entry` / `bulk_create_entries` / `update_entry`	Create entry / bulk create (≤50 slugs) / update slug
`list_revisions` / `save_revision` / `get_pub_preview_url` / `publish_revision`	Revisions / preview URL for human review / publish (`can_publish=false` keys stop at submit + `pendingHumanApproval`)
`submit_entry_for_review`	Submit for approval
`list_media`	Media list
`upload_media`	Upload (`filePath` / `sourceUrl` / `base64` → asset id)
`list_master_entities` / `get_master_entity`	Master entities
`list_master_records` / `create_master_record`	List / create records (`label` string or `{ default, ja, … }`; optional `color` `#RRGGBB`)
`update_master_record` / `update_master_tree`	Update records / tree (not available with agent keys — see below)
`get_project_content_locales`	Content locale settings (includes `content_default_locale`)
`patch_project_content_locales`	Update locales (tenant_admin JWT only)
`search_admin_help`	Search Console help KB
`get_admin_help_article`	One help article (Markdown)
`ask_admin_help`	Help RAG Q&A (related articles if LLM unset)
`translate_entry_locales`	AI locale batch translate (Standard+, 1 ticket / run)
`get_login_branding`	Login branding (no auth; includes `login_background` / `hide_luno_logo` / `hide_powered_by`)
`get_login_appearance`	Login appearance settings (auth required)
`update_login_appearance`	Update login appearance (background=Standard+, WL=Business+)
`list_console_login_ip_allowlists`	Login IP allowlist (Business+)
`add_console_login_ip_allowlist`	Add IP rule (tenant scope)
`delete_console_login_ip_allowlist`	Delete IP rule

Master update limits: agent keys have no userId; update_master_record / update_master_tree need a user JWT with master_record_edit_allowed or tenant_admin. List / create (create_master_record) work with content scope. Creating master definitions uses `apply_master_blueprint` (schema scope), not POST /master-entities.

Multilingual master labels: label may be a plain string (default locale) or a locale map. When site multilingual is OFF, only default is stored. Blueprint record.label stays a plain string (normalized internally).

Master record color: optional #RRGGBB on create_master_record, update_master_record (user JWT), and apply_master_blueprint records. Omit keeps an existing color (create = none). null clears. #fff / named colors are rejected.

Locale translation: call translate_entry_locales with a content-scope agent key, merge returned items into the snapshot, then save_revision. Returns 400 if site multilingual is OFF.

Golden Path smoke (staging)

E2E over a real MCP stdio client:

# LUNO_API_URL + LUNO_AGENT_KEY (dedicated smoke project recommended)

pnpm golden-path-smoke

Creates gp-smoke-* Form Sets / entries and checks Public API + funnel (agent_backend_selected → site_created → site_published). **Staging Golden Path CI

只显示了开头部分；其余内容请在仓库中阅读