Your app defines the operations, chooses the data, and enforces the rules. Framework-neutral core; React bindings when you need them.
npm install @binaried/rcipRCIP 2.0.5 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
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.
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.
A scheduling agent needs a scheduling operation—not every contact visible on the page. RCIP exposes the capabilities and outputs you choose, with validation, availability, application policy, and trusted confirmation around existing behavior. Your model/transport integration connects to the client; browser-native WebMCP support is not required.
In our local dispatch workflow, Browser Use took 72.9s median and RCIP took 9.4s, including readiness checks. Both passed all five runs. The RCIP route omitted selected resident/contact markers from model-bound text. See the benchmark and its limits · Understand data exposure.