The logic is simple. If building became programmable, distribution should be too. That's why Torchly now ships an MCP server alongside the dashboard: an agent in Claude, Cursor, or any MCP client can now search communities by audience, estimate reach against a target cost per action, launch a campaign, and read back per-community attribution – without you touching a growth dashboard at all. Distribution becomes a callable function, as it's arguably the most critical aspect involved in building a product.

A terminal session calling Torchly's MCP server: search_communities returns 34 communities and 61,200 members; estimate_reach returns 18 matched rooms at an estimated 480 to 620 installs for £4.10 to £5.40 each; launch_campaign goes live awaiting admin approval, 14 of 18 so far; then get_attribution returns per-community taps, installs and redemptions.

How it works is simple. You write the brief – or your agent does – and Torchly handles the rest - attribution, matching, approvals, and more. All from one window.