RCIPGive AI assistants the actions of your React app.

React capabilities for AI assistants, UI agents, and tool calling. Your application controls context, validation, policy, confirmation, and execution.

Get started

Try the interactive demo

View on GitHub

Stable product intent

Declare capabilities such as todos.create. Bind them to existing behavior without exposing the DOM or component instances.

Application-owned decisions

Validate schemas, check current availability, apply policy, and resolve confirmation in trusted host UI.

Choose your consumer

Use the headless client, packaged Assist, a command palette, or your own integration. No model service or credentials are bundled.

React Capability Interface Protocol

npm install @binaried/rcip

RCIP 2.0.3 implements the in-process protocol 1.0. Its core is framework-neutral; React bindings support React 18 and 19. Optional Assist and Explorer have separate imports.

Start with a single useful action, then share the same capability contract across human-facing application behavior and assistant integrations.

Run the standalone React starter · Understand the architecture · Read the Finance case study · Inspect the security boundary

React tool calling and browser agents

Declare the application actions an assistant or UI agent can request, bind them to current React state, and route tool calls through the validated RCIP client. An in-app agent, agentic UI, or frontend tool can consume the same application capabilities. Browser use and browser automation are supported application areas when your consumer connects the agent to RCIP's discovery and invocation client. Your consumer supplies the model/provider or browser-agent integration. Explore the architecture.

How RCIP relates to MCP and WebMCP

RCIP shares the goal of exposing useful application tools. It currently runs in-process; direct MCP and WebMCP adapters are planned and are not included. Compare the integration boundaries.