Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Cinematic website prompts plus demo footage, tuned for Lovable, Bolt, Cursor, Claude and Codex.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
NIGHTMARQUEE_TOKEN, NIGHTMARQUEE_NO_TELEMETRY, NIGHTMARQUEE_TIMEOUT_MSLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add nightmarquee --env NIGHTMARQUEE_TOKEN=your-value --env NIGHTMARQUEE_NO_TELEMETRY=your-value --env NIGHTMARQUEE_TIMEOUT_MS=your-value -- npx -y nightmarqueeCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"nightmarquee": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nightmarquee"
],
"env": {
"NIGHTMARQUEE_TOKEN": "your-value",
"NIGHTMARQUEE_NO_TELEMETRY": "your-value",
"NIGHTMARQUEE_TIMEOUT_MS": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
NIGHTMARQUEE_NO_TELEMETRY envNIGHTMARQUEE_TIMEOUT_MS envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub ant-dev-lab, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: NIGHTMARQUEE_TOKEN
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.6) llegó al registro hace 26 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, topo^alpin
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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