Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Cinematic website prompts plus demo footage, tuned for Lovable, Bolt, Cursor, Claude and Codex.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
NIGHTMARQUEE_TOKEN, NIGHTMARQUEE_NO_TELEMETRY, NIGHTMARQUEE_TIMEOUT_MSAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"nightmarquee": {
"command": "npx",
"args": [
"-y",
"nightmarquee"
],
"env": {
"NIGHTMARQUEE_TOKEN": "your-value",
"NIGHTMARQUEE_NO_TELEMETRY": "your-value",
"NIGHTMARQUEE_TIMEOUT_MS": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add nightmarquee --env NIGHTMARQUEE_TOKEN=your-value --env NIGHTMARQUEE_NO_TELEMETRY=your-value --env NIGHTMARQUEE_TIMEOUT_MS=your-value -- npx -y nightmarqueeTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"nightmarquee": {
"command": "npx",
"args": [
"-y",
"nightmarquee"
],
"env": {
"NIGHTMARQUEE_TOKEN": "your-value",
"NIGHTMARQUEE_NO_TELEMETRY": "your-value",
"NIGHTMARQUEE_TIMEOUT_MS": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"nightmarquee": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nightmarquee"
],
"env": {
"NIGHTMARQUEE_TOKEN": "your-value",
"NIGHTMARQUEE_NO_TELEMETRY": "your-value",
"NIGHTMARQUEE_TIMEOUT_MS": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
NIGHTMARQUEE_NO_TELEMETRY envNIGHTMARQUEE_TIMEOUT_MS envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto ant-dev-lab bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: NIGHTMARQUEE_TOKEN
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.6) kam vor 26 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, yontu
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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