# Novence [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Novence-ai/mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/novence-2

## Description
Hosted MCP for creating, checking, deploying, and hosting static sites for AI agents.

## Tools
Capabilities this server exposes over MCP:

- **bootstrap** — Signup without a prior `nv_` key; OTP after live URL
- **create_project** — Project lifecycle (`share_gate_emails` OTP on `*.novence.ai` only; `site_mcp` visitor MCP on Pro/Scale; `data_edit_emails` + `data_edit_names` owner `/edit` on Pro/Scale)
- **get_upload_url** — Upload site files
- **list_files** — Manage project files
- **set_redirects** — Stage `/_redirects` (SPA: `/* /index.html 200`); call `deploy` to apply
- **put_site_data** — Live `/data/{name}.json` without a deploy (Pro/Scale)
- **get_site_brief** — Private webmaster brief + inbox (Pro/Scale). Session start: get then list.
- **deploy** — Publish, poll, preview aliases (Pro/Scale), rollback last 5
- **publish_html** — One HTML document → `index.html` + deploy (omit project_id to create)
- **run_checks** — Quality checks (Lighthouse, a11y, links)
- **configure_custom_domain** — Custom domains (CNAME www → fallback.novence.ai; apex ALIAS **or** URL-redirect)
- **create_form** — Forms
- **checkout** — Paid plans (verified email; after 2nd project or a 402)
- **get_quotas_and_usage** — Quotas, usage, and opt-in site traffic
- **create_account_session** — Billing/account console kit (never embed `nv_` in HTML)

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "novence": {
    "url": "https://api.novence.ai/mcp"
  }
}
```

## Documentation

## What the Novence MCP server does

The Novence MCP server gives AI agents an interface for building and operating static websites on Novence. It supports project creation, file uploads, deployment, checks, custom domains, forms, and usage inspection. A simpler publishing path accepts one HTML document and turns it into an `index.html` deployment; a full project workflow can manage multiple files and project settings.

The service is hosted rather than self-managed. Agents connect to `https://api.novence.ai/mcp` using streamable HTTP. The repository contains a Claude Code plugin and installation package, while the hosting API remains on Novence infrastructure.

## How it works

An unauthenticated session can begin with `bootstrap(email)`. Novence sends an OTP after a live URL is available; verification unlocks the account’s Free quotas and provides an `nv_` API key. Later sessions send that value as `Authorization: Bearer nv_…`. The initial connection can therefore omit headers, which is useful for first-time setup.

A typical workflow creates a project, requests upload URLs, uploads site files, confirms those uploads, and calls `deploy`. Agents can poll deployment status, obtain preview URLs where the plan supports them, or roll back one of the last five deployments. Redirect rules are staged through `set_redirects` and take effect on deployment. `put_site_data` can update `/data/{name}.json` without a deployment on Pro and Scale plans.

Quality checks cover Lighthouse, accessibility, and links. Forms, custom domains, private webmaster briefs, site events, quotas, usage, and opt-in traffic data are available through their corresponding tools.

## Setup and configuration

The Novence MCP server requires no local process. Configure an MCP client with the endpoint URL. For Claude Code, install the repository’s plugin through the Claude plugin marketplace and leave the API key blank initially; after bootstrap, save the key in the plugin settings and reload plugins.

Cursor and generic MCP clients use the same endpoint-only configuration for bootstrap. After receiving a key, store it as `NOVENCE_API_KEY` and send it as a bearer header. The account key must not be embedded in generated HTML. Custom domains require DNS configuration: `www` uses a CNAME to `fallback.novence.ai`, while an apex domain uses either an ALIAS record or a URL redirect.

## Tools and capabilities

- Create projects, list and inspect them, and update project settings.
- Upload, list, retrieve, and delete project files.
- Publish complete projects or a single HTML document.
- Run checks and retrieve their results.
- Configure domains, redirects, forms, previews, and deployment rollbacks.
- Update site data, manage webmaster briefs, and inspect site events on supported plans.
- View quotas, usage, opt-in analytics, billing options, and account console sessions.

## Limitations and notes

The Novence MCP server is hosted; the repository’s Dockerfile and catalog adapter expose public schemas for directory tooling and do not contain the hosting API. Several capabilities depend on Pro or Scale, including visitor MCP access, owner editing, live site data, private briefs, preview aliases, and some traffic features. Paid checkout requires a verified email and may be prompted after a second project or a payment response. The `site_mcp` visitor feature and email-based editing settings are configured at the project level.

_Full upstream README: https://allmcps.com/mcp/novence-2/readme_