assistant-ui React — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to React chat interfaces for user-managed MCP connections and tool presentation: Do OAuth storage, connection state and MCP tool approvals remain consistent between runtime and chat UI?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

React teams building production AI chat and agent interfaces.

What we know

Open-source React primitives for streaming AI chat, tool calls, generative UI and human approvals.

Maintenance / activity evidence

@assistant-ui/react 0.15.23 published 2026-10-02T02:21:32.295Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Host application defines permissions. Writes: Frontend approval/actions depend on app.
Authentication not yet verified.
Sensitive access: Conversation and tool-result data

The UI library itself has no service-account authority; backend integrations determine effective risk.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

12,422 shared-repository stars · 7.7M package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

GitHub stars are shared across the assistant-ui repository; npm downloads are exact to @assistant-ui/react.

All limitations / Review context

Do OAuth storage, connection state and MCP tool approvals remain consistent between runtime and chat UI?

The bounded review of the publisher's documented React chat interfaces for user-managed MCP connections and tool presentation and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

The UI library itself has no service-account authority; backend integrations determine effective risk.
Host application defines permissions.
Conversation/tool data is rendered by the host application.
Reviewed write actions: Frontend approval/actions depend on app
Sensitive access: Conversation and tool-result data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
This general SDK/UI package is MCP-relevant integration infrastructure; its separately published MCP client/manager module remains a distinct identity.
SDK only; backend model, auth and tool permissions are application-defined.

Original activity observations

@assistant-ui/react 0.15.23 published 2026-10-02T02:21:32.295Z

Technical identity

npm/@assistant-ui/react

Exact implementation source: https://www.npmjs.com/package/@assistant-ui/react ↗
Reviewed resource type: SDK
Repository identity: assistant-ui/assistant-ui
Package identity: npm:@assistant-ui/react

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

Package registry ↗
@assistant-ui/react
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
www.assistant-ui.com/docs/tools/user-managed-mcp
Source material retained for this review.
GitHub repository ↗
assistant-ui/assistant-ui
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

SDK setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
sdk dependency install · Publisher instructions
npm install @assistant-ui/react @assistant-ui/ai-sdk ai
Configure / authenticate
MCP100 setup guide
This is a React UI library. Use `npx assistant-ui@latest init` to add UI to an existing application, or `npx assistant-ui@latest create` for a new app. No standalone MCP server is provided by @assistant-ui/react.
Check connection
Suggested check
Run app build/render and verify chat UI renders; no MCP client tool listing should be expected.
Remove / uninstall / revoke
MCP100 setup guide
For the application dependency, run `npm uninstall @assistant-ui/react` in the owning Node project, remove integration imports and rebuild/redeploy. No standalone MCP registration exists for this package.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Package / application cleanup · matching installation environment · MCP100 composed guide
npm uninstall @assistant-ui/react

Official Documentation & Sources

What it does

Open-source React primitives for streaming AI chat, tool calls, generative UI and human approvals.

Capability: AI & Reasoning
Resource type: SDK
Industry: Software & Technology
Best fit: React teams building production AI chat and agent interfaces.

Representative uses

Build streaming chat UIs
Render tool calls and approval flows
Connect Vercel AI SDK, LangGraph or custom runtimes

Limitations

SDK only; backend model, auth and tool permissions are application-defined.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Host application defines permissions.
Data handling: Conversation/tool data is rendered by the host application.
Cost: free
Risk and cautions: The UI library itself has no service-account authority; backend integrations determine effective risk.

Access scope and cautions

Write actions: Frontend approval/actions depend on app
Sensitive access: Conversation and tool-result data
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Build streaming chat UIs; Render tool calls and approval flows; Connect Vercel AI SDK, LangGraph or custom runtimes.

Can it modify data or perform write operations?

Documented write actions include: Frontend approval/actions depend on app. Recorded permission boundary: Host application defines permissions.

What data-handling boundary should I consider?

Conversation/tool data is rendered by the host application. Recorded sensitive-access context: Conversation and tool-result data.

What limitations and risks should I check before use?

The UI library itself has no service-account authority; backend integrations determine effective risk. SDK only; backend model, auth and tool permissions are application-defined. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

assistant-ui is listed as First-party MCP in MCP100’s current evidence.