Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Cinematic website prompts plus demo footage, tuned for Lovable, Bolt, Cursor, Claude and Codex.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
NIGHTMARQUEE_TOKEN, NIGHTMARQUEE_NO_TELEMETRY, NIGHTMARQUEE_TIMEOUT_MS「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"nightmarquee": {
"command": "npx",
"args": [
"-y",
"nightmarquee"
],
"env": {
"NIGHTMARQUEE_TOKEN": "your-value",
"NIGHTMARQUEE_NO_TELEMETRY": "your-value",
"NIGHTMARQUEE_TIMEOUT_MS": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add nightmarquee --env NIGHTMARQUEE_TOKEN=your-value --env NIGHTMARQUEE_NO_TELEMETRY=your-value --env NIGHTMARQUEE_TIMEOUT_MS=your-value -- npx -y nightmarquee動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"nightmarquee": {
"command": "npx",
"args": [
"-y",
"nightmarquee"
],
"env": {
"NIGHTMARQUEE_TOKEN": "your-value",
"NIGHTMARQUEE_NO_TELEMETRY": "your-value",
"NIGHTMARQUEE_TIMEOUT_MS": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"nightmarquee": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nightmarquee"
],
"env": {
"NIGHTMARQUEE_TOKEN": "your-value",
"NIGHTMARQUEE_NO_TELEMETRY": "your-value",
"NIGHTMARQUEE_TIMEOUT_MS": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
NIGHTMARQUEE_NO_TELEMETRY envNIGHTMARQUEE_TIMEOUT_MS envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント ant-dev-lab で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:NIGHTMARQUEE_TOKEN
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.1.6)がレジストリに届いたのは26 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Zoo MCP
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Cinematic website prompts with live previews, inside your editor.
Art-directed prompts for hero sections, landing pages, SaaS, portfolio, e-commerce and 3D/WebGL scenes. Each is tuned for Lovable, Bolt, Cursor, Claude and Codex, and each has a live demo you can scroll.
An MCP (Model Context Protocol) stdio server. Node 20 or newer.
Claude Code
claude mcp add nightmarquee -- npx -y nightmarquee
Or as a Claude Code plugin, which adds the same server plus the skills below:
/plugin install nightmarquee --marketplace ant-dev-lab/nightmarquee-mcp
Claude Desktop / Cursor: add to your MCP config:
{
"mcpServers": { "nightmarquee": { "command": "npx", "args": ["-y", "nightmarquee"] } } }
Claude Desktop reads ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows. Cursor reads ~/.cursor/mcp.json, or .cursor/mcp.json inside a project.
Codex: the CLI, the IDE extension and the ChatGPT app share one config.
codex mcp add nightmarquee -- npx -y nightmarquee
That writes this to ~/.codex/config.toml, which you can also add by hand (or to .codex/config.toml in a trusted project):
[mcp_servers.nightmarquee]
command = "npx" args = ["-y", "nightmarquee"]
Codex uses the tools but does not show MCP prompts as commands yet, so ask for a design in plain language and it calls nightmarquee_search_prompts. Prompts come back in the Codex dialect unless you pass another tool.
No account needed. Free prompts work immediately.
nightmarquee_search_prompts: browse by query, category or tiernightmarquee_get_prompt: fetch one by slug, optionally with your own brand name and a tool dialect (lovable, bolt, cursor, claude, codex). Without one you get codex in Codex and claude elsewherenightmarquee_get_footage: fresh download links for a demo's footage, when the ones from nightmarquee_get_prompt have expirednightmarquee_sign_in: connect an account to unlock Unlimited promptsnightmarquee_whoami: check what's connectedCategories are hero, landing, saas, portfolio, ecommerce, 3d and mobile.
Ask for a design in plain language and the model will usually reach for nightmarquee_search_prompts on its own. Or drive it directly:
nightmarquee_get_prompt(slug: "glasshouse-nine", tool: "cursor", brand: "Northwind")
Every prompt in the catalog is also registered as an MCP prompt, so the whole library shows up in your client's command palette. In Claude Code that means a slash command per design:
/mcp__nightmarquee__glasshouse-nine
Other clients surface MCP prompts their own way. Claude Desktop lists them in the attachment (+) menu; Codex does not list them yet. The list is built from the catalog fetched at startup, so if the server can't reach nightmarquee.com when your editor launches, the tools still work but the per-prompt commands won't appear until you restart.
Most demos play video. When your account may download it, nightmarquee_get_prompt returns the footage from the demo, every clip, with a signed link per file, and the prompt text ends with a note naming each clip. The agent downloads the files into public/ under their names and then builds, so the page you get plays the same footage as the demo. The links last 10 minutes; nightmarquee_get_footage fetches fresh ones without the prompt.
A free prompt's footage needs a free account, and the rest come with Unlimited. Without an account, the prompt text still arrives in full, with one line saying how many clips the demo plays and that nightmarquee_sign_in gets them. Each account can fetch 30 packs an hour, shared with downloads on the site.
In Lovable and Bolt, download the files from the prompt page on nightmarquee.com and upload them there.
The same catalog also installs as agent skills, for editors that read SKILL.md files:
npx skills add ant-dev-lab/nightmarquee-mcp
That adds a nightmarquee guide and one skill per free prompt. They carry no prompt text: each fetches the current prompt, through this server when it is installed and from nightmarquee.com when it is not.
Some prompts are free, currently glasshouse-nine, aetheris-voyage, nordlys-fintech, solstice-festival, lumen-observatory, sumi-atelier, wren and fieldnote. The rest need Unlimited. Run nightmarquee_search_prompts with tier: "free" for the live list.
Run nightmarquee_sign_in and approve the code in your browser. It waits about a minute; if you took longer, run it again and it picks up the same request rather than issuing a new code. Either way the rest unlock in the same session, no restart. Fetching a locked prompt without an entitlement returns a teaser and a pricing link, never the body.
For headless environments where no browser is reachable, carry a token across instead: sign in once on a machine that has a browser, copy the token value (nm_live_…) out of ~/.nightmarquee/credentials.json, and set it there.
{ "env": { "NIGHTMARQUEE_TOKEN": "nm_live_..." } }
Connections are listed on your account page and can be revoked from there; the next call falls back to free-only.
| Variable | Effect |
|---|---|
NIGHTMARQUEE_TOKEN | Use this token instead of the stored one. Wins over credentials.json. |
NIGHTMARQUEE_API | Point at a different backend. Defaults to https://nightmarquee.com. |
NIGHTMARQUEE_HOME | Directory for credentials.json. Defaults to ~/.nightmarquee. |
NIGHTMARQUEE_TIMEOUT_MS | Ceiling on every API request, in milliseconds. Defaults to 10000; unparseable or non-positive values fall back to the default, and anything above 2147483647 is clamped to it. |
NIGHTMARQUEE_NO_TELEMETRY | Set to 1 (any non-empty value works) to stop sending the install ID and your client's name. See below for exactly what this does and doesn't cover. |
Full policy: https://nightmarquee.com/privacy
Credentials are stored locally at ~/.nightmarquee/credentials.json, mode 0600.
Fetching a prompt is an HTTP request to nightmarquee.com, so the server necessarily sees which prompt slug and tool dialect you asked for, and logs that. That is true in every configuration.
On top of that, each request carries three headers by default:
x-nm-install: a random UUID generated on your machine on first run and kept in credentials.json. Not derived from anything, tied to nothing else.x-nm-client: the name and version your MCP client reports, e.g. claude-code/2.1.240. In Codex this package also asks for the Codex dialect itself, so turning telemetry off does not change which prompt text you get.x-nm-version: the version of this package.If you are signed in, the request also carries a bearer token identifying your NightMarquee account.
Never sent, in any configuration: the prompts or code you write, file paths, file contents, or anything else from your project.
Request records are used to operate the service and to understand which prompts people use, nothing else. They are held in our Supabase database.
NIGHTMARQUEE_NO_TELEMETRY=1 drops x-nm-install and x-nm-client. `x-nm-version` is still sent, and requests are still made and still logged server-side, and the log rows just carry no install ID and no client name. If you are signed in, the bearer token identifies your account regardless of this setting.
Your data is not sold, rented, or shared with third parties for their own purposes. It is processed only by the infrastructure providers running the service on our behalf: Vercel (hosting), Supabase (database), and Lemon Squeezy (payments, for subscribers only). No advertising or analytics networks receive any of it.
Account data is kept while your account exists. Email to delete your account and we remove your data within 30 days, except records we must keep for tax and accounting (held by the merchant of record).
Request records are not currently expired on a fixed schedule; they are deleted on request along with your account.
Tokens and local credentials are under your control at any time: revoke a connected editor from your account page, which deletes the token outright, or delete ~/.nightmarquee/credentials.json to remove the local copy.
Privacy questions, data access, and deletion requests:
The server code in this package is MIT.
The prompt text it fetches is licensed separately: free prompts cover personal and non-commercial projects, Unlimited adds commercial use, and the prompt text itself may not be republished or resold. Full terms: https://nightmarquee.com/license.
MIT © NightMarquee