Open the Watchline dashboard, choose OpenClaw, then copy the generated setup commands. Watchline prepares pull delivery automatically for first-run setup, so you do not need to manage channels by hand.

Watchline's hosted MCP server provides watch-management tools, and the plugin runs a background puller that starts OpenClaw runs for matched events in the main session by default.

Prerequisites

You need a Watchline account and a working OpenClaw workspace. The dashboard generates the exact values for apiKey and channelId.

Install the plugin

The plugin gives OpenClaw a pull delivery service. Use the commands from the OpenClaw tab in the dashboard whenever possible.

openclaw plugins install @watchline/openclaw-plugin

openclaw plugins install @watchline/openclaw-plugin

openclaw config patch --stdin <<'JSON5'
{
  plugins: {
    entries: {
      watchline: {
        enabled: true,
        config: {
          apiKey: "wl_...",
          channelId: "ch_...",
          apiBaseUrl: "https://api.watch.qordinate.ai",
          userId: "me",
          pollIntervalSeconds: 15
        }
      }
    }
  }
}
JSON5
openclaw watchline install-mcp

openclaw config patch --stdin <<'JSON5'{  plugins: {    entries: {      watchline: {        enabled: true,        config: {          apiKey: "wl_...",          channelId: "ch_...",          apiBaseUrl: "https://api.watch.qordinate.ai",          userId: "me",          pollIntervalSeconds: 15        }      }    }  }}JSON5openclaw watchline install-mcp

openclaw gateway restart

openclaw gateway restart

openclaw watchline install-mcp reads the plugin config and configures the hosted Watchline MCP server for start_watch, continue_watch, list_watches, pause_watch, resume_watch, and delete_watch.

Matched events start a targeted OpenClaw run in the main session by default. Set sessionKey only if you want to route deliveries to a different explicit OpenClaw session.

The generated MCP server uses a static URL, https://api.watch.qordinate.ai/v1/mcp, and sends the API key, channel ID, and user ID through headers. That keeps the setup compatible with OpenClaw's MCP config while still letting other MCP clients use the URL-param form.

Register a watch from OpenClaw

Ask OpenClaw to use Watchline to watch an app source for a specific event. OpenClaw should call start_watch from the hosted MCP server; if Watchline needs an app connected, it returns the connect URL in the tool response.

Troubleshooting

If OpenClaw cannot see the tools, run openclaw mcp show, restart the gateway, and confirm openclaw watchline install-mcp completed.

If no events arrive, refresh the Watchline dashboard and confirm it shows an API key and channel ID in the OpenClaw setup. If the setup panel keeps saying it is preparing, sign out and back in, then contact Watchline support if it still does not clear.