Respira API v2 is now live across Plugin, MCP, and WebMCP

Respira 3.3 is a fidelity release. The goal was not adding isolated endpoints; it was delivering one coherent safety and data model across plugin API, approval flow, snapshots, builder patching, desktop MCP, and WebMCP — while keeping respira/v1 behavior stable.

What shipped

The release includes a full respira/v2 contract and lifecycle model:

• Include-gated reads with canonical builder payloads and deterministic hashes.
• Snapshot capture, history, diff, and restore endpoints.
• Duplicate-before-edit enforcement for pages, posts, and custom post types.
• Stale-base approval blocking by default, with explicit privileged force override.
• Builder patch operations that target id first, then deterministic path.

How adoption works

Clients on MCP 3.3.1 negotiate capabilities per site by probing GET /wp-json/respira/v2/status. When v2 is available, they use it. When it is not, they automatically fall back to v1.

This means existing v1 integrations continue to run without migration pressure, while fidelity-aware clients gain snapshots, patching, and include-gated payload control immediately.

Patch update (March 5, 2026)

Respira 3.3.1 aligns the plugin with official WordPress MCP Adapter v0.4.1 lifecycle behavior. In plain English: cleaner server registration, safer transport permission wiring, and no workflow changes for your team.

Safety model in one sentence

Do you need site-level changes?

No blocking changes are required. If your site is on plugin 3.3.1, it already exposes the v2 surface.

1. Update any public docs/snippets to mention v2 fidelity support.
2. Link this release note from your home or docs changelog area.
3. If you run custom clients, add include tokens only where needed to control payload size.

Release tags

Plugin release tag: v3.3.1
MCP release tag:    mcp-v3.3.1