Respira Add-on SDK

Write your own WordPress plugin that adds MCP tools, safety controls, builder integrations, or any other surface to Respira. Used by every first-party add-on (Forms, SEO, Newsletter, WooCommerce) and open to partner / third-party developers.

WordPress + Respira (core)
       └── Respira Add-on SDK (this package)
              ├── @respira-press/forms-addon       (free · top 5 form plugins)
              ├── @respira-press/seo-addon         (paid · bundled with Studio · IndexNow + multi-plugin)
              ├── @respira-press/woocommerce-addon (paid · already shipping)
              └── your-addon-here                  (third-party, MIT/GPL/proprietary)

Why an SDK

Respira's core surface is page-builder-aware editing across 12 builders. Everything else — form-entry analytics, SEO automation, newsletter sync, e-commerce flows — is orthogonal to that surface and shouldn't bloat the core plugin. Add-ons let those surfaces ship as separate, opt-in packages, each with their own:

• Versioning (no need to ship-and-forget with every core release)
• Licensing (free, paid, or bundled with a Respira plan)
• MCP tool catalogue (each add-on registers tools that show up in agent autocomplete)
• Telemetry (audit-log scope per add-on)
• Update channel (respira.press downloads, license-gated zip)

The SDK gives you the primitives. The Woo add-on is the live reference implementation.

Spec

The full v1 spec lives in SPEC-v1.md. It locks in:

• Add-on manifest format (respira-addon.json)
• Lifecycle hooks (boot, register_tools, deactivate, uninstall)
• Tool registration shape (ToolDescriptor + handler signature + scope declaration)
• License & entitlement contract (free / paid / bundled-with-plan / lifetime)
• Version pinning (SDK semver + core compatibility range)
• Error taxonomy hooks (so add-on errors flow into core's structured-error system)
• Install / update / uninstall flow + safety
• Security model (capability checks, sandbox boundaries)
• Distribution model (zip + checksum + license-gated download endpoint)

Quick start

1. Read the spec.
2. Copy examples/hello-addon/ as your starting point.
3. Edit respira-addon.json with your add-on's slug, name, version, license tier.
4. Implement register_tools() to declare your MCP tools.
5. Test against a Respira install (any v7.1.0+ build).
6. For partner submission, open a PR or issue against this repo with your add-on's manifest URL.

Roadmap

• Phase 1 (now) — v1 spec + hello-addon example + Woo addon migration to SDK shape.
• Phase 2 — Forms add-on (WPForms + CF7 + Gravity + Forminator + Fluent), free, ships as the first net-new SDK consumer.
• Phase 3 — SEO add-on with IndexNow + Yoast / RankMath / AIOSEO / SEOPress / The SEO Framework. Paid; bundled with Respira Studio plan.
• Phase 4 — Newsletter add-on (Stefano Satollo plugin integration).
• Phase 5 — Open the partner submission flow publicly.

License

GPL-2.0-or-later — same as Respira core.