Connecting your agent to the platform

The connection is a one-time setup, and none of it requires being a developer. You are wiring three things together: your platform workspace, your agent, and the site code your agent will work on. Here is the shape of it, in order.

Step 1: the workspace

Create your free account and set up your first client, even a test client named after your own agency site. Every client in the platform has their sites, forms, reports, and requests in one place. This workspace is what your agent will be able to see.

Step 2: the site code

Client sites live on the boilerplate: a modern, fast site codebase, pre-instrumented with analytics, search console wiring, forms, and event tracking. You get it from the resources library. Your agent works on copies of this codebase, one per client site. The boilerplate matters more than it sounds: because every site shares the same proven structure, your agent never improvises architecture, and its work stays predictable across every client you ever take.

Step 3: the MCP connection

In your platform settings you will find the MCP connection details. You add them to your agent's configuration (for Claude Code, one entry in a config file; the resources library has copy-paste setup guides per agent). From that moment, your agent can list your clients, read requests, and update their status. Test it immediately: ask your agent "what open requests do I have?" and watch it answer from your real workspace.

Step 4: the listen daemon

Install the daemon so requests trigger work without you in the loop. When a client submits a request through their portal, the daemon notifies your agent, the agent picks it up, does the work, and posts the result back for your review. You can run without it (checking the queue manually a few times a day is fine at the start), but the daemon is what makes the machine feel like a machine.

The first test, end to end

• Create a request on your test client: "change the phone number in the footer."
• Let the agent pick it up and make the change on a branch (next lesson explains branches).
• Open the preview link, check the footer, approve it.
• Now do it again with something real. That loop, repeated, is your delivery business.

If you get stuck, the setup guides in the resources library cover the common agents and the common failure points. And if you would rather have the whole thing configured for you, agent connection and skills setup is part of the Starter Package. Optional, as always.