Self-Managed // Agent access // Early access

WordPress hosting your agent can provision and run

Nova provides a documented path from account creation to a live WordPress site and an authenticated, site-bound MCP connection.

Who it is for

  • Claude Code users who want a WordPress deployment target and an operational toolset.
  • Cursor and ChatGPT/Codex users connecting an agent to content and hosting operations.
  • Developers wiring an agent to account, checkout, provisioning, and MCP APIs.

The Self-Managed plan

Self-Managed

$49/month

You or your AI agent at the controls.

Self-managed (unmanaged by Nova) WordPress hosting for one site: run it yourself, or hand it to your AI agent over Nova's MCP server.

  • + One WordPress site, 10 GB storage, 100 GB bandwidth, and one custom domain
  • + 30 site audits and 20 AI drafts per month
  • + Agent access included in early access: 23 site-bound MCP tools

Agent onboarding flow

An agent can create an account, get the owner to verify by email, sign in, hand the owner a Stripe checkout link, provision the site and receive MCP credentials without the owner opening the dashboard.

  1. 1. POST /api/agent-onboarding/register

    Create the account receipt with an email, password, and idempotency key. No session or token is issued.

  2. 2. GET /api/agent-onboarding/{onboarding_id}

    Ask the owner to verify the email, then poll with X-Poll-Token at intervals of at least five seconds.

  3. 3. POST /api/auth/login

    After verification, sign in with the password set during registration and receive a JWT.

  4. 4. POST /api/agent-onboarding/checkout

    Request a checkout URL for plan host and hand that URL to the account owner.

  5. 5. GET /api/agent-onboarding/{onboarding_id}

    Poll with the JWT until the signed Stripe webhook records host/active and the state becomes paid.

  6. 6. POST /api/tenants

    Provision the one allowed site, then poll the receipt until the tenant becomes site_active.

  7. 7. POST /api/agent-onboarding/{onboarding_id}/finalize

    Finalize once to receive the MCP key and connection configuration; save the plaintext key immediately.

Register

curl -X POST https://nova.host/api/agent-onboarding/register \
  -H "Content-Type: application/json" \
  -d '{"email":"owner@example.com","password":"replace-with-a-strong-password","company_name":"Example Co","idempotency_key":"agent-run-001"}'

Connect the MCP server

The dashboard labels this format .mcp.json. The endpoint uses Streamable HTTP and a Bearer key.

WordPress core provides the Abilities API, while the WordPress project maintains the separate MCP Adapter. Nova’s independent hosted integration requires neither on the tenant site.

{
  "mcpServers": {
    "nova": {
      "type": "http",
      "url": "https://mcp.nova.host/mcp",
      "headers": { "Authorization": "Bearer <key>" }
    }
  }
}

Managed vs self-managed (unmanaged) hosting

Self-Managed puts the account owner or agent in charge of the site. Nova’s Scale, Momentum, Infinite, and Synergy plans are managed: Nova operates the WordPress site, and Agent access is enabled per account during early access. The same distinction is often described as managed versus unmanaged WordPress hosting.

FAQ

Is Self-Managed managed WordPress hosting?

No. Self-Managed is unmanaged by Nova. The account owner or an authorized agent operates the site. Scale, Momentum, Infinite, and Synergy are Nova-operated managed plans.

Can Claude Code provision a WordPress site?

It can follow Nova’s documented onboarding flow: register, wait for owner email verification, sign in, hand checkout to the owner, provision after webhook-confirmed payment, and finalize MCP access.

Does the Nova MCP server require a WordPress plugin?

There is no separate MCP plugin. Tenant sites run Nova's mu-plugins, while the authenticated Streamable HTTP server is hosted at https://mcp.nova.host/mcp.

How does this relate to the WordPress Abilities API and MCP Adapter?

WordPress core provides the Abilities API. The MCP Adapter is the WordPress project's separate adapter. Nova's server is an independent, hosted integration backed by Nova's tenant-side mu-plugins and requires neither on the tenant site.