Coming soon

User communication primitives for solo-built SaaS.

One API. One MCP server. Changelog, waitlist, feedback, and notifications. Designed for the way you build with AI in 2026.

Nordva is in development. This page is a preview of the planned surface area. Details may change before launch.

example

$ claude mcp add https://mcp.example.com

Illustrative example. The real MCP endpoint will be published at launch.

Four primitives, one API.

Communicate with users at every moment that matters: pre-launch, launch, in-product, and ongoing. No need to stitch four SaaS subscriptions together.

Coming soon

Changelog & Release Notes

Headless changelog with subscriber lists, public read endpoints, and an MCP tool that publishes from your AI assistant.

POST /v1/changelog/entries

Coming soon

Waitlist + Referral

Standalone waitlist with viral referral mechanics. Position calculation, invite queue, and leaderboard. No logic to write.

POST /v1/waitlist/signups

Coming soon

User Feedback Triage

Submit feedback, classify with an LLM, and route to Linear, GitHub, Slack, or email. Confidence scores included.

POST /v1/feedback

Coming soon

In-App Notifications

Polling-first notification API for product events. Streaming via Server-Sent Events on higher tiers.

POST /v1/notifications

Built for AI-assisted development

Designed for the way you write code in 2026.

Every endpoint will be mirrored as an MCP tool, with descriptions written as LLM instructions rather than docstrings, so your AI assistant calls the right tool with the right arguments without reading another SaaS dashboard.

One API key for every primitive. REST and MCP share auth.
Idempotency keys on every POST. Agent retries don't create duplicates.
OpenAPI 3.1 spec generated from the same Zod schemas the runtime validates against.
Errors include remediation. Agents know what to fix without your help.

Code samples are illustrative only and may change before launch.

example only

// In Claude Code or Cursor
publish_changelog_entry({
  title: "CSV export 3× faster",
  body_markdown: "## What changed\nWe rewrote...",
  category: "improvement",
  version: "2.4.1"
})

→ entry_id:  ce_01J9X...
→ public_url: changelog.example.com/...

curl -X POST https://api.example.com/v1/changelog/entries \
  -H "Authorization: Bearer <your-api-key>" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"title":"CSV export 3× faster",
       "body_markdown":"## What changed...",
       "category":"improvement"}'

# → 201 Created
#   {"data":{"entry_id":"ce_01J9X..."}}

Less overhead

Ship faster. Skip the plumbing.

Every primitive Nordva covers is a category of work you and your AI assistant no longer have to build from scratch, or coordinate across four separate SaaS accounts.

Changelog

Read Beamer's docs, configure a widget, hardcode a deploy step

Tell your AI assistant to publish the entry. It calls the MCP tool.

Waitlist

Write position logic, generate referral codes, handle duplicates

POST one JSON body. Position and referral code come back in the response.

Feedback

Triage feedback manually, copy-paste to Linear or Slack

Submit feedback through the API. Classification and routing happen server-side.

Notifications

Build a polling loop, manage state, wire up a notification UI

GET /v1/notifications/unread on a timer. One endpoint, no infrastructure.

The difference compounds. Less time spent on communication infrastructure is more time spent on the product.

One key. One install. One surface.

Today you stitch together four SaaS subscriptions to cover this surface area. Nordva is being built to cover all of it through a single API and a single MCP server.

Capability	Beamer	Waitlist.email	Canny	Knock	Nordva
Changelog API	ui	-	-	-	✓
Waitlist API	-	partial	-	-	✓
Referral mechanics	-	✓	-	-	✓
Feedback triage API	-	-	ui	-	✓
Notification API	-	-	-	✓	✓
MCP server	✗	✗	✗	✗	✓
Single API key for all	-	-	-	-	✓

Comparison reflects planned scope. Nordva is not yet publicly available.