novence-deploylisted

Deploy and host static sites and HTML artifacts with Novence MCP. Use when creating projects, publishing a single HTML report/dashboard/artifact, uploading site files, running quality checks, deploying, attaching domains, managing Novence forms and quotas, or adding third-party widgets and /data JSON files.
Novence-ai/mcp · ★ 1 · Data & Documents · score 68

Install: claude install-skill Novence-ai/mcp

# Novence deploy Use the Novence MCP tools (server `novence`) for static-site hosting. Static-only is not a dead end. Improve sites with **third-party widgets** and **baked-in data files** — no plugin marketplace, no per-site server. Product: https://novence.ai/site-data ## Prerequisites - No API key required to start. If unauthenticated, call `bootstrap(email)` — the session adopts the `nv_` key. See `SETUP.md`. - **Claude Code plugin:** leave **Novence API key** blank until after bootstrap, then set it in plugin settings (`userConfig` / Keychain) and `/reload-plugins`. Empty `${user_config.api_key}` is unauthenticated. - **Cursor / shell:** connect with the MCP URL only; after bootstrap, `export NOVENCE_API_KEY='nv_…'` and add env interpolation in MCP headers. ## One HTML file (artifact) When the user has a **single HTML document** (report, dashboard, deck, Claude-style artifact) and needs a live URL: 1. If unauthenticated, `bootstrap(email)`. 2. Read the file if it is on disk, then call `publish_html` with the HTML string. Omit `project_id` to create a project; pass it to replace the live page. 3. Poll `get_deployment_status` until live or failed. 4. Return only the `url` (`https://{suffix}.novence.ai/`). Do **not** use the multi-file upload loop for one HTML file. Shell: `npx novence deploy report.html`. ## Typical loop (multi-file sites) On session start (Pro/Scale, existing project): `get_site_brief` then `list_site_events` (forms still email the owner). 1. `