> ## Documentation Index
> Fetch the complete documentation index at: https://docs.saga-a2ui.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Installing saga a2ui

> The seven packages published for this release, their registry integrity values and the install recipes for the Lit and React stacks.

> Documents saga a2ui **0.11.0-rc.1** (prerelease). This is the SDK guide [`docs/public-install.md`](https://github.com/MachineWisdomAI/saga-a2ui/blob/fb4126cc5a9ac2e7f9cd916c377d24b237d00bb8/docs/public-install.md) at source revision [`fb4126c`](https://github.com/MachineWisdomAI/saga-a2ui/tree/fb4126cc5a9ac2e7f9cd916c377d24b237d00bb8). It is published as a snapshot: later source changes do not alter it. Licensed under [Apache-2.0](https://github.com/MachineWisdomAI/saga-a2ui/blob/fb4126cc5a9ac2e7f9cd916c377d24b237d00bb8/LICENSE).

The public release set contains seven packages:

| Package | Use |
| - | - |
| `@saga-a2ui/core` | Application actions and A2UI protocol processing. |
| `@saga-a2ui/mcp` | MCP server operations, view connections and request lifetimes. |
| `@saga-a2ui/components` | Optional FaithfulCard content, link and image policies. |
| `@saga-a2ui/lit` | Lit renderer integration and optional FaithfulCard rendering. |
| `@saga-a2ui/react` | React A2UI integration, action controls and optional FaithfulCard rendering. |
| `@saga-a2ui/lit-mcp-stack` | Lit rendering joined to MCP Apps delivery. |
| `@saga-a2ui/react-mcp-stack` | React rendering joined to MCP Apps delivery. |

Use Node **22.12.0 or newer** and a TypeScript-aware bundler. The packages export TypeScript source. An application normally installs one stack and its framework peers, and imports from that stack only.

## Choose an exact published version

Check the registry before selecting a version:

```sh theme={null}
npm view @saga-a2ui/lit-mcp-stack dist-tags --json
npm view @saga-a2ui/react-mcp-stack dist-tags --json
```

The current RC is `0.9.0-rc.1` for all seven packages, verified on 29 October 2026. The recipes below pin those versions. The [release receipt](https://github.com/MachineWisdomAI/saga-a2ui/pull/343) records the source revision, registry integrity and anonymous installation checks. `next` selects these versions; `latest` was not changed by this release.

A stack pins its SDK siblings, so its patch version can differ from theirs. For another release, confirm the stack version and its framework peers in npm before replacing the pins. Source manifests and candidate builds can be ahead of the registry.

## Install one stack plus framework peers

At your application's root, preserve existing overrides and add:

```json theme={null}
{
  "overrides": {
    "@a2ui/markdown-it": "0.2.1"
  }
}
```

For Lit:

```sh theme={null}
npm install --save-exact --strict-peer-deps @saga-a2ui/lit-mcp-stack@0.9.0-rc.1 lit@3.3.3
```

For React:

```sh theme={null}
npm install --save-exact --strict-peer-deps @saga-a2ui/react-mcp-stack@0.9.0-rc.1 react@19.3.1 react-dom@19.3.1
```

Commit the application lockfile. Each stack declares its SAGA siblings as regular dependencies with exact pins, so the application does not declare those packages separately. Use the stack root for an application-owned catalog and `/faithful-card` for a card application; `/server` is composed separately and stays out of browser bundles. A stack's server entry requires the full application's framework peers.

For pnpm, put the equivalent Markdown override in the consumer workspace root. See [React consumer dependencies](https://docs.saga-a2ui.dev/docs/releases/0.11.0-rc.1/guides/react-consumers.md) for the separate A2UI Zod 3 and MCP Zod 4 contexts. Do not add direct upstream A2UI packages to a stack application.

## Lower-level integrations

Applications that intentionally compose lower-level SDK APIs may install the packages they import, using the versions recorded in the release receipt. The original four-package `0.1.0-rc.1` release remains historical; it predates the stacks. See [package layout](https://github.com/MachineWisdomAI/saga-a2ui/blob/fb4126cc5a9ac2e7f9cd916c377d24b237d00bb8/packages/README.md) for ownership and entry points.

## Run a demo or use a starter

[Getting started](https://docs.saga-a2ui.dev/docs/releases/0.11.0-rc.1/guides/getting-started.md) creates a Lit starter or the React starter on Hono, or attaches SAGA to an existing backend, and its two tracks build an application ([React](https://docs.saga-a2ui.dev/docs/releases/0.11.0-rc.1/guides/build-tic-tac-toe-with-react.md), [Lit](https://docs.saga-a2ui.dev/docs/releases/0.11.0-rc.1/guides/build-notes-with-lit.md), which also runs the synthetic demo). The React tutorial installs published npm packages in the reader’s own app directory. The source CLI and contributor workflows build matched candidate tarballs from a checkout to test unpublished changes. Candidates have versions such as `0.0.0-candidate.g<12 hex>` and are distinct from public npm releases; see [candidate installation, updates and rollback](https://github.com/MachineWisdomAI/saga-a2ui/blob/fb4126cc5a9ac2e7f9cd916c377d24b237d00bb8/docs/candidate-update-and-rollback.md). The source CLI, root workspace and example applications are not npm packages.

Continue with [the Lit track](https://docs.saga-a2ui.dev/docs/releases/0.11.0-rc.1/guides/build-notes-with-lit.md#compose-a-view-with-a-stack) or the [React track](https://docs.saga-a2ui.dev/docs/releases/0.11.0-rc.1/guides/build-tic-tac-toe-with-react.md) to connect a view, then the [action guide](https://docs.saga-a2ui.dev/docs/releases/0.11.0-rc.1/guides/actions.md) to trace a complete interaction. [Host compatibility](https://docs.saga-a2ui.dev/docs/releases/0.11.0-rc.1/guides/host-compatibility.md) records the flows observed in ChatGPT, Claude and Alexa+. Installing a package does not deploy an application or establish acceptance in an assistant host.

## Maintainer publication

[Release preparation](https://github.com/MachineWisdomAI/saga-a2ui/blob/fb4126cc5a9ac2e7f9cd916c377d24b237d00bb8/docs/release-packages.md) describes the seven-package set, exact tarball qualification and publication verification. Source metadata and passing CI prepare a release; successful publication followed by an anonymous exact-version install establishes registry availability. Keep current release receipts here instead of copying mutable registry status into agent instructions and development guides.

For repeat releases, npm [trusted publishing](https://docs.npmjs.com/trusted-publishers/) needs a matching package repository URL, a supported Node/npm combination and `id-token: write` confined to its publishing job. The existing validation workflow does not publish. Verify scope ownership and approved versions and tags before publishing with [public npm access](https://docs.npmjs.com/creating-and-publishing-an-organization-scoped-package/).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.