Tools catalog

Where tools live

• RC-API ships tool definitions as *.public.mdc (interface/metadata) and *.private.mdc (workflow / steps) under its settings tree.
• In the reference repo there are 75 public catalog entries; the split by execution_target changes when you edit specs (recent snapshot: ~64 remote, ~8 local, ~2 hybrid, ~1 local_async).

How Cursor sees them

• MCP exposes one tool: recloud.
• Each catalog name becomes a subcommand value.
• Discovery: MCP loads GET /tools/list-all (authorized) and exposes manifest/help resources for agents.

Activation

• Operators enable/disable tools in the tray; an active_tools JSON file is written so the MCP server can filter registration (implementation-specific path—see configuration.md).

Local execution

• Some subcommands map to Node handlers inside the MCP process (e.g. QR, chart, system metrics).
• Others run remote workflows on RC-API via POST /tools/execute.
• local_graph agents are optional definitions under ~/.recloud/agents/.

Docs discipline

This page intentionally does not duplicate a giant tool-by-tool marketing list—that drifts from code. Use /tools/list-all or the MCP recloud://tool_manifest resource as the live enumeration.