v1.2.0

What's Changed

• docs: record verified 1.1.0 publication by @pablospaniard in #139
• Complete platform-neutral renderer foundation by @pablospaniard in #140
• Add first-class SwiftUI renderer by @pablospaniard in #141
• Add remote SwiftPM package entry point by @pablospaniard in #142
• Add first-class Jetpack Compose renderer by @pablospaniard in #143
• Publish the Compose renderer to Maven Central by @pablospaniard in #144
• chore: prepare v1.2.0 release by @pablospaniard in #147

Full Changelog: v1.1.0...v1.2.0

v1.1.0

MCP Native 1.1.0 adds opt-in contract registration, native hosting, and adapter authoring across the seven coordinated packages.

• Register application-defined inline JSON contracts with closed schemas, exact negotiation, immutable models, and bounded processing.
• Host compiled native renderers through a contract controller/provider, with explicit event authorization, lifecycle ownership, and render budgets safe under React replay.
• Select maintained MCP, A2UI, and MCP Apps profiles, or install separately packaged reviewed inline adapters with their own exact bindings.
• Generate canonical schema bundles and validate adapters with bounded fixture reports.

Existing 1.0.x integrations need no code changes. Root APIs, closed result/action/error unions, default policies, peer requirements, and MCP/A2UI/MCP Apps pins are preserved. The new APIs are available through @mcp-native/host/contracts, /contracts/react-native, and /contracts/authoring. Linked custom resources, streaming updates, and additional platform renderers remain outside this release.

Earlier Milestone 11 source checkouts must replace the unpublished renderer consume prop with a fresh createRenderBudget() per render. Timeout gates remain held until actual review/delivery settlement; delivery code owns cancellation and idempotency for external effects.

See the migration guide and full changelog.

Published and verified on 2026-09-15: all seven packages are available on npm at 1.1.0, with latest pointing to that version. A clean registry installation verified all 16 public entry points, the reviewed export/declaration baseline, package manifests and contents, the CLI, and positive/negative contract fixtures. Registry signatures and provenance attestations verified successfully; all seven package attestations name the reviewed release commit ec57c6e8f980fb1f7f10aa591d29804ded138e80 and release workflow run.

v1.0.1

Documentation-only patch release of all seven coordinated packages. Runtime behavior, public APIs,
and protocol/schema pins are unchanged.

Documentation

• Align all package READMEs with consistent headers, npm badges, navigation, installation, and
  quick-start sections; add the host API summary, responsibilities, and license.
• Document every bundled CLI command, including options and examples for doctor,
  scaffold-catalog, scaffold-extension, and help.
• Document the 18-component baseline versus broader React Native and protocol support, the existing
  custom-component integration path, and a planned extended catalog with per-adapter acceptance
  criteria and an iOS/Android support matrix.
• Clarify repository-wide A2UI claims: MCP Native supports a pinned, feature-scoped profile of
  A2UI v1.0 Candidate; upstream identifies v0.9.1 as its current production release as of
  2026-09-07. Distinguish component-name coverage and stable package APIs from full protocol
  coverage, and make unsupported RPC messages and reviewed revision updates explicit.

All seven packages are released together as 1.0.1.

Full changelog: v1.0.0...v1.0.1

MCP Native v1.0.0

First stable release of all seven coordinated MCP Native packages. Adopts the 1.x compatibility
contract for the high-level connect-call-render host and independently usable runtime, MCP,
A2UI, React Native, and WebView layers.

Stable API

• Connect, discover tools, call, and render supported results through @mcp-native/host, with
  cancellation, reconnect, retry, teardown, and accessible React Native operational states.
• Render the complete pinned A2UI basic catalog through host-owned native components, bounded
  bindings and functions, and explicitly negotiated compiled host extensions.
• Host MCP Apps in isolated WebViews with validated resources, a bounded message bridge, and
  explicit application authorization; present ordinary MCP content through an inert fallback.
• Preserve concise API names, compatible aliases, and the documented migration entry points.
  Breaking API, protocol, and default-policy changes require a major-version migration plan.

Changed

• Promote all seven package versions and internal dependency ranges to 1.0.0; installation
  examples now select @1.
• Align the pre-stable A2UI schema pin to upstream
  8ff4651232ab0e02b0123730b502711170637a3a, including the function-envelope refactor in PR #2486.
  Preserve the component/function set and callable APIs; update the exported schema-revision literal
  and require hosts and servers to advertise the new exact pin together. Mismatches retain ordinary
  MCP fallback without loading the A2UI resource. See migration guidance.
• Finalize the v1 documentation and adopt the 1.x public API compatibility contract across all
  seven packages. Mark implementation, review, and readiness decisions complete while tracking
  coordinated stable publication separately.
• Consolidate pre-v1 upgrade details in the migration guide, remove stale package-preview wording,
  and describe runnable examples as application integrations. This documentation cleanup preserves
  security boundaries and existing compatibility exports.

Fixed

• Validate reconstructed A2UI function calls through the complete FunctionCall schema so the
  updated flat catalog cannot bypass common-field validation or unknown-property rejection.

Install the stable packages with npm install @mcp-native/host@1 @mcp-native/mcp@1 @modelcontextprotocol/client react.

See the migration guide for upgrade guidance.

v1.0.0-rc.1

First explicitly tagged v1 release candidate.

This release makes concise current-profile names canonical across the A2UI and React Native package APIs and documentation. Existing A2ui*, A2uiV1*, and A2UI_V1_* exports remain source-compatible aliases throughout 1.x; protocol literals and schema pins are unchanged.

The mcp-native convenience package now exposes explicit a2ui and reactNative namespaces using syntax supported by the pinned React Native Metro toolchain.

The rc dist-tag is updated by the protected release workflow. The latest dist-tag remains on 0.9.3.

v1.0.0-beta.2

Second v1 beta prerelease.

This release corrects the umbrella mcp-native CLI mapping so npm preserves and installs the mcp-native executable. Package verification now rejects bin paths npm would normalize away, and the clean-install smoke verifies the CLI from a path containing spaces across supported platforms.

The beta dist-tag is updated by the protected release workflow. The latest dist-tag remains on 0.9.3.

v1.0.0-beta.1

First 1.0.0 release candidate for MCP Native.

This beta promotes the high-level @mcp-native/host connect-call-render workflow and its React Native provider while preserving the independently usable low-level packages. It includes the reviewed A2UI v1 Candidate, MCP Apps, native rendering, WebView isolation, accessibility, policy, lifecycle, packaging, and release-hardening work described in the changelog.

Install the beta explicitly:

npm install @mcp-native/host@beta @mcp-native/mcp@beta @modelcontextprotocol/client react

The npm latest dist-tag remains on 0.9.3 until the stable 1.0.0 release.

Release candidate commit: 7cecb5260f883159754011d28e7e0b17fce5334a

v0.9.3

MCP Native 0.9.3 introduces the initial headless host orchestration package and simplifies renderer compatibility to a single React >=18.1.0 peer dependency.

Highlights

• Add @mcp-native/host with bounded result resolution, connection and tool-call orchestration, cancellation, reconnect, and fail-closed action authorization.
• Export reusable validated MCP tool and resource boundaries and forward supported abort and cache options.
• Remove React Native and Expo from package peer dependencies; native framework versions remain tested integration fixtures.
• Add the City Canvas mixed native and isolated WebView Expo Go example and updated roadmap documentation.
• Verify clean package installation and the upgrade path from the coordinated 0.9.2 release.

All seven public packages are released together at 0.9.3.

v0.9.2

MCP Native 0.9.2 adds a complete Expo Go todo app and restores React Native 0.86 as the supported minimum while preserving the frozen 1.0 candidate API.

Highlights

• Try the full package flow in Expo Go through the one-click Snack in the README.
• Build native A2UI surfaces with validated lifecycle messages, renderer-local state, official action envelopes, persistence, and accessibility.
• Use React Native 0.86 or any newer 0.x release within the declared peer range.
• Start from shorter, task-oriented documentation with clearer package choices and integration guidance.
• Rely on stronger package verification: exact licenses, exports, source maps, clean installs, and a tested 0.9.1 upgrade path.

All six public packages are released together at 0.9.2.

MCP Native v0.9.1

What's Changed

• chore: release 0.9.1 by @pablospaniard in #79

Full Changelog: v0.9.0...v0.9.1