Connections

Connect Re:Yi through two supported paths.

Use Local MCP for MCP clients or Provider Gateway for compatible API clients. Both are configured and operated locally through Re:Yi Control Center.

Re:Yi official sitePublic content, local custody.Recall Core data stays outside the online service by default.

Local

Ready

Local MCP

Use Re:Yi from trusted local MCP clients while memory custody, source files, and model keys stay on the user's machine.

API

Ready

Provider Gateway

Connect OpenAI-, Anthropic-, and Gemini-compatible clients through Recall Core's local gateway while the user keeps control of providers, model keys, and memory behavior.

One control boundary

Choose the client path. Keep control in one place.

Re:Yi Control Center owns setup, status checks, repair, updates, and clean removal for both connection paths. The official site explains them, but it does not operate a user's local Recall Core runtime.

What stays local

Memory custody and model keys remain with the user.

Local MCP and Provider Gateway follow the same local-first boundary: Re:Yi does not host user memories, source files, vectors, graphs, or model API keys.