Configuration

RC_API_KEY (Bearer)

Issued / validated by RC-API for your deployment.
Tray persists it and injects into mcp.json for the RC MCP server:
env.RC_API_KEY, and commonly MCP_CLIENT=cursor for parity with reference Electron config.
MCP uses the same key in Authorization: Bearer … when calling http://localhost:3001/tools/list-all and /tools/execute (default base URL is configured in MCP code—keep MCP and API ports aligned).

Cursor `mcp.json`

Reference shape (paths must be absolute on the user machine):

mcpServers.RC: command + args pointing at server_workflow.js inside the bundled mcp_server_dist (or dev equivalent).
Env at minimum: RC_API_KEY, MCP_CLIENT as needed.

Tray updates RC only; other servers in the file are preserved.

Constitution profiles (tray UI)

Stored in the tray app settings; when saved, tray fetches blocks from RC-API and writes:

<cursorUserConfigDir>/rules/recloud-behavior.mdc

Policies align with RC-API routes such as /rules/base, /rules/tool_policy/..., /rules/behavior_profile/..., /rules/prompt_policy/... (exact set as implemented in tray + API).

Tool activation

Tray maintains an active tools list for the operator.
Persisted path depends on build: Electron v2 historically used <projectRoot>/.recloud/active_tools.json; Tauri line may use app_data_dir/.../ReCloud/active_tools.json. Ensure the MCP bundle you ship reads the same location.

RC-API server env

Configure in RC-API repo: model keys, listen port, DB if any, upload helpers, etc.—not duplicated here.