Publishing

Content that lands where it belongs

Noverva does not want to be your CMS. Publishing connectors are planned: they will write into the one you already run, track what happened, and tell you when the published version and Noverva's copy stop agreeing. Today, MCP is the connector that is available.

Connect a site
Connectors

What exists today, and what does not

Planned means planned. Nothing on this page is described as available before it is.

WordPress

planned

A free plugin plus REST: drafts, scheduling, media, taxonomies, featured images, and Yoast / Rank Math / AIOSEO metadata. Not yet available.

Generic REST

planned

Map Noverva fields onto your own endpoint, for custom CMS and internal publishing pipelines. Not yet available.

Webhooks

planned

Signed, retried, replay-protected events for state changes. Not yet available.

Google Search Console

planned

The measured half of the analytics picture, read-only by OAuth consent. Not yet available.

MCP

available

Not a publishing target — a control surface. Drive Noverva from any MCP-capable AI client.

Ghost

planned

Admin API. Straightforward mapping; scheduled after the SDK stabilises.

Webflow

planned

CMS collections. Field mapping is per-site, so onboarding needs a mapping step.

Shopify

planned

Blog articles and pages. Product content is a separate, larger problem.

HubSpot

planned

CMS Hub blog posts and landing pages.

Notion

planned

Useful as a review surface more than a publishing target.

Wix

planned

Blog API.

Next.js / headless

planned

Git-backed and API-backed variants. Deploy hooks rather than direct writes.

Planned capabilities

What each planned connector is designed to do

None of these connectors is available yet. Platforms differ, and pretending otherwise produces silent failures, so each connector will declare what it supports and Noverva will grey out what a platform cannot do rather than attempt it and lose the data.

Capabilities planned for each connector; none is available yet
CapabilityWordPressRESTWebhook
Create draftSupportedSupportedSupported
PublishSupportedSupportedSupported
ScheduleSupportedSupportedNot supported
Media uploadSupportedSupportedNot supported
Categories & tagsSupportedSupportedNot supported
Featured imageSupportedSupportedNot supported
SEO metadataSupportedSupportedNot supported
Canonical URLSupportedSupportedNot supported
Author mappingSupportedNot supportedNot supported
Sync stateSupportedSupportedNot supported
Drift detectionSupportedNot supportedNot supported

A webhook connector is a delivery mechanism, not a CMS — it cannot report back what happened to the content after you receive it, which is why sync state and drift detection are not planned there.

WordPress · planned

A real plugin, not an API example

The Noverva plugin is not available yet. As designed, it will be free, install from your dashboard, and connect with a scoped token you can revoke from either end. It will write SEO metadata into whichever of Yoast, Rank Math or All in One SEO you already run, and keep a local log of everything Noverva did to your site.

Scoped tokens, rotatable and revocable from either side
HMAC-signed requests with a replay window
Draft, publish and schedule
Media transfer with alt text preserved
Categories, tags, authors, featured images
Yoast / Rank Math / AIOSEO metadata
Duplicate and slug-conflict protection
Local activity log and one-click disconnect