Core components

RC-API

HTTP service: catalog load (/tools/list-all), workflow execution (/tools/execute), health (/health), rule fragments for constitution, auth middleware for Bearer keys. Tools are defined declaratively as .mdc pairs under the API’s settings tree.

MCP server (ReCloud_app → server_workflow)

• Transport: stdio (Cursor launches the process).
• Surface: one MCP tool recloud; arguments subcommand + parameters.
• ToolDispatcher: loads descriptions from RC-API; routes by execution_target:
  • remote → HTTP POST /tools/execute (unless a local_pipeline or legacy local-handler branch applies).
  • local / hybrid / local_async → registered local handler class for that subcommand name.
  • local_graph → graph agents from ~/.recloud/agents/*.mdc when present.
• Local handler classes (reference): small fixed set including recloudControl, convertData, fileMetadata, generateQR, generateChartLocal, systemMonitor, plus meta recloud handler legacy—not separate MCP tools.

Tray app

• Electron v2 reference: rich UI, MCP spawn optional, mcp.json writer, constitution .mdc writer.
• Tauri port: same responsibilities targeted; verify parity for active_tools path and /health interpretation when claiming production-ready.

Cursor

Loads mcp.json, speaks MCP to RC, shows agent instructions from MCP resources.

Related

• architecture.md
• tools-catalog.md