NoaCG Broadcast Graphics and Playout

Name: NoaCG Broadcast Graphics and Playout
Author: NoaCG

作者：NoaCG版本 0.12.4i★ –i在你的电脑上运行

注册名称io.github.NoaCG/noacg

安装

概览

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

Make broadcast graphics for NoaCG Studio and play them out live on CasparCG, OBS, vMix or OGraf.

PopNx MCP 的三大支柱

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

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

它能帮你做什么

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

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

安装

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

安装之前

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

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

你需要

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

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

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

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

{
  "mcpServers": {
    "noacg": {
      "command": "npx",
      "args": [
        "-y",
        "@noacg/cli",
        "mcp"
      ],
      "env": {
        "NOACG_URL": "your-value",
        "NOACG_AGENT_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add noacg --env NOACG_URL=your-value --env NOACG_AGENT_KEY=your-value -- npx -y @noacg/cli mcp

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

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "noacg": {
      "command": "npx",
      "args": [
        "-y",
        "@noacg/cli",
        "mcp"
      ],
      "env": {
        "NOACG_URL": "your-value",
        "NOACG_AGENT_KEY": "your-value"
      }
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "noacg": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@noacg/cli",
        "mcp"
      ],
      "env": {
        "NOACG_URL": "your-value",
        "NOACG_AGENT_KEY": "your-value"
      }
    }
  }
}

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

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

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

需要你填写的值

NOACG_URL env
The NoaCG deployment to use. Defaults to https://noacg.studio.
NOACG_AGENT_KEY 机密 env
A scoped agent key for saving graphics without noacg login, for CI.

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

它能做什么

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

基础检查i

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

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

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

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

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

常见问题

NoaCG Broadcast Graphics and Playout 安全吗？

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

它需要哪些密钥或代码？

你需要填写：NOACG_AGENT_KEY

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

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

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.12.4）于6天前进入注册中心。

哪些应用可以使用它？

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

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, SSTracker free youth training

替代选择

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

如何看卡片：★ 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昨天更新

安装

SSTracker free youth training

作者：sstracker.app

Free youth sports drills, practice plans and age-group answers for parents and coaches.

在云端运行今天更新

安装

作者的 README

打开 README

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

@noacg/cli

The NoaCG CLI - the agent door into NoaCG Studio. Make broadcast graphics for NoaCG from a coding agent, or from your own terminal: scaffold, validate, inspect, screenshot, package, save - against any NoaCG deployment. The full account is the repo's docs/AGENT_CLI.md.

The package is `@noacg/cli`; the command it installs is `noacg`. So npm i -g @noacg/cli gives you noacg validate …, and every command below is spelled the way you will type it.

One tool, three entrances. The MCP server is not a second thing to choose between. noacg mcp runs this same package as an MCP server, and the Claude Code / Codex plugin carries the noacg-graphic skill, which drives this same package from the terminal. Pick the entrance your agent uses -

Entrance	For	Install
the plugin	Claude Code, Codex	two commands, below - it brings the skill (`/noacg:graphic` in Claude Code) and runs nothing until a graphic is being made; the optional `noacg-mcp` plugin adds the always-on MCP server
the MCP server	any MCP client	`npx -y @noacg/cli mcp` over stdio
the terminal	an agent that runs shell commands, and you	`npm i -g @noacg/cli`

Whichever you pick, the noacg-graphic skill is the same text: what a NoaCG graphic must expose, and the loop to get there. It is the contract, not design guidance.

Connecting NoaCG Playout to a CasparCG server is a different tool, NoaCG Bridge, downloaded from noacg.studio/downloads (the newest Bridge release on the repository's Releases page). It is not about authoring, has its own version number, and needs nothing from this package.

Paste this to your agent

The short way in: one prompt that runs this CLI through npx in the session you have open, with nothing installed first. The agent checks its setup, connects your NoaCG account in the browser if needed, asks what to make, and saves each finished graphic to your library with its link. Copy it from noacg.studio/downloads; it names the exact CLI version to run.

The commands it runs are below, for anyone who would rather run them by hand.

Install

npx @noacg/cli doctor                 # no install: runs the published build

npm i -g @noacg/cli # or install it once

Claude Code: the noacg plugin ships the skill as /noacg:graphic, with nothing to install first; the skill runs this CLI from the terminal. The optional noacg-mcp plugin adds the always-on MCP server (cli/plugin-mcp/README.md says what it costs). In a Claude Code session (2.1.275 or later), one command adds the marketplace, asks you to confirm it, and installs:

/plugin install noacg --marketplace NoaCG/NoaCG-Studio

From a terminal or a setup script, the same install is two commands:

claude plugin marketplace add NoaCG/NoaCG-Studio

claude plugin install noacg@noacg-studio

For the MCP server on its own: claude mcp add noacg -- npx -y @noacg/cli mcp.

A plugin installed from this marketplace does not update itself until you say so. Claude Code turns auto-update on only for Anthropic's own marketplaces, so the skill text stays the version you installed. Turn it on once in /plugin, Marketplaces, noacg-studio, Enable auto-update, and new versions arrive at the start of a session. Or update by hand: claude plugin marketplace update noacg-studio && claude plugin update noacg@noacg-studio. noacg doctor names the installed version whenever it is behind the CLI you are running.

Codex: the same plugin, from the same repository. codex plugin add installs the skill, so there is nothing to copy by hand; codex plugin add noacg-mcp@noacg-studio adds the optional always-on server the same way.

codex plugin marketplace add NoaCG/NoaCG-Studio

codex plugin add noacg@noacg-studio

The same goes for Codex, in its own spelling: codex plugin marketplace upgrade noacg-studio && codex plugin add noacg@noacg-studio.

On a Codex without codex plugin, do it the long way instead: copy skill/noacg-graphic/ from this package to ~/.codex/skills/noacg-graphic/, then codex mcp add noacg -- npx -y @noacg/cli mcp.

Any MCP client: run npx -y @noacg/cli mcp as a stdio server - command npx, args -y @noacg/cli mcp.

Use

npx @noacg/cli types

npx @noacg/cli scaffold --type scoreboard --design neutral --name "Football scoreboard" --out ./football-scoreboard

...design it: edit football_scoreboard.html, css/template.css, js/template.js ...

(the html is named after the GRAPHIC, not the folder: the name's spaces become underscores)

npx @noacg/cli validate ./football-scoreboard --screenshots ./shots npx @noacg/cli inspect ./football-scoreboard npx @noacg/cli login # once per machine: a scoped key that can only create graphics in your library npx @noacg/cli save ./football-scoreboard

Command	What it does
`doctor`	Which browser and which NoaCG deployment (`NOACG_URL`) this tool will use, the bridge version it found, and whether a key is held - plus a line for an installed plugin whose skill is behind this CLI, and one for a CLI behind npm's `latest`. Both silent when there is nothing to update.
`types`	The graphic types the deployment knows: fields, operator events, designs, neutral scaffold.
`scaffold --type [--design \	neutral] [--name N] [--set key=value]... --out `	A complete, valid package from a type: a catalog chassis or the NEUTRAL scaffold (fields, machine, controls and runtime on a plain spine).
`scaffold --fields "Label:kind[=value],..." [--name N] --out`	A typeless graphic with exactly the fields you declare.
`validate [--no-bench] [--no-house-contract] [--screenshots ]`	The static gate + the live runtime bench, every finding as a teaching line, readiness rows, optional off/on-air/stress frames - and the package's generated half regenerated from the sources. Third-party OGraf packages: manifest conformance + a host-driven lifecycle check.
`inspect`	The operator surface NoaCG derives from the graphic's own contract (inputs, buttons, steps).
`screenshot --state off\	onair\	stress --out `	One transparent frame.
`pack ... --name N [--save] [--out ] [--rundown ] [--layer n]...`	Several graphics as ONE package - layers plus an optional rundown of cues. `--save` validates them and sends the package to your NoaCG Home, where it waits on Home → Productions with an Install button that creates the production; `--out` writes it as a file for the Import a package card. With `--save`, `--share --license cc-by-4.0 --shown-as S --description D` also sends it for review to Community packs, without cues, when you want it shared.
`docs [topic]`	The skill's reference texts.
`mcp`	The same verbs as an MCP server over stdio.
`login [--name N] [--no-browser] [--key ]`	Get a scoped agent key for this machine: opens the NoaCG consent page, receives a one-time code on a loopback listener, redeems it. The key can only create graphics in your library; revoke it in Settings → Account → Agent access or with `logout`. `NOACG_AGENT_KEY` for CI.
`logout [--local]` / `whoami`	Revoke + forget this machine's key / show which key is held and whether it is still valid.
`save ... [--name N] [--folder F] [--no-bench]`	Validate (gate + bench), refuse on errors, then put the graphics in your NoaCG library in one delivery and print each `#/graphic/` link. All of them arrive or none; running the same command again after an interruption resumes it and never saves a second copy. Save = the library, never a production.
`bridge [--port 8899] [--origin URL]… [--no-open] [--quiet]`	NoaCG Bridge: hold the AMCP socket a browser cannot, on a loopback-only HTTP surface the NoaCG page speaks the playout protocol to. It opens a link that pairs your browser with one click; binds `127.0.0.1` and refuses anything else; refuses origins that are not your NoaCG. Leave it running. `caspar agent` is its old name and still runs it.
`caspar status\	send\	play\	stop [--server HOST] [--amcp-port 5250]`	The same AMCP with no browser at all: check a server, send one command, or put a production's output URL on a channel (`play --url --channel 1 --layer 20`).

Add --json to any command for one JSON object on stdout. Exit codes: 0 clean, 1 findings or refused, 2 usage/IO error. Environment: NOACG_URL (default https://noacg.studio; a dev server or self-host works), NOACG_BROWSER (a Chromium executable; otherwise the system Chrome/Edge or a Playwright-installed Chromium is used), NOACG_AGENT_KEY (a key for CI - beats the stored one), NOACG_CREDENTIALS_DIR (the folder login keeps its key in, for more than one login on one account; default the per-user config directory).

The package on disk

<slug>/

SOURCES - edit these GENERATED - never edit; noacg validate rebuilds them .html .ograf.json the OGraf v1 manifest (+ v_noacg) css/template.css graphic.mjs the OGraf Web Component js/template.js FIELDS.md README.md controlpanel.html js/gsap.min.js images/ fonts/

One folder is a valid EBU OGraf v1 Graphic, the SPX/CasparCG package and the workspace you edit. Zip it and it imports through the studio's Import door; drop it in an OGraf renderer and it plays. Those two are what the folder satisfies IN PLACE; the graphic itself is plain HTML, CSS and JS, and NoaCG exports it to an OBS/vMix overlay, H2R or LiveOS from the same sources. In through NoaCG, out to anything.

MCP

The same verbs, spoken over stdio - npx -y @noacg/cli mcp. One tool, noacg, with the terminal's grammar: command is the verb (types, scaffold, validate, inspect, screenshot, docs, save - the last after noacg login) and the other arguments are that verb's flags, so { "command": "validate", "path": "./my-graphic", "screenshots": true } returns the frames as images. The skill's references are also resources (noacg://docs/ ). The noacg-graphic skill ships under skill/.

One tool rather than seven because an MCP client puts every tool's schema into the model's context in every session where the server is configured, whether or not that session is about graphics. This shape is about 590 tokens against about 1,160 for the seven-tool one it replaced. The teaching is in the skill, which loads only when a graphic is being made.

bridge and caspar are deliberately not MCP tools: they drive live playout hardware, which is an operator's decision rather than an authoring agent's.

Develop

npm install

npm run build # generates the plugin's skill copy, then tsc NOACG_URL=http://localhost:5174 npm test # against a NoaCG dev server's /bridge npm run check:skill # every shipped copy of the skill matches cli/skill/

Licence

Apache-2.0 - deliberately different from NoaCG Studio itself, which is AGPL-3.0-only. This tool is the door into NoaCG for coding agents, so it is licensed to be installed anywhere without a policy review: a permissive licence, an explicit patent grant, no copyleft reaching anything you build with it. The AGPL on the studio protects the hosted application; it was never meant to gate the client that talks to it.

Graphics you create are yours. Nothing in either licence attaches to the templates this tool scaffolds or to what you export and put on air.

One third-party note, since a scaffolded package carries it: the animation runtime bundled into a graphic (`js/gsap.min.

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