roasr-openclaw

RoASr in OpenClaw — ad audit, competitor spy & Vision creative analysis

RoASr connects to a user's Meta, Google Ads and Yandex Direct data and returns an A–F account audit with findings ranked by money at stake, plus competitor intelligence from the Meta Ad Library and Vision analysis of creatives. This skill drives RoASr from OpenClaw — either through RoASr's remote MCP endpoint (HTTP) or a local stdio MCP server (npx roasr-mcp). Access is scoped to the user's own workspace; isolation and scopes are enforced API-side. Everything is read-only except one campaign pause/resume tool, which only works inside permissions the owner granted explicitly.

Setup (do this first — and tell the user if they haven't)

RoASr is a hosted service. OpenClaw cannot use it without the user's own account and API key.

1. Sign up or log in at https://roasr.com — it's free.

2. Go to Settings → API keys and create a key pg_live_… (owner/admin) with the scopes you need. The token is shown once — copy it.

3. Connect in OpenClaw — pick ONE transport:

   A. Remote HTTP connector (no install). In OpenClaw's MCP settings add an HTTP/remote server:

   Name:  roasr
   URL:   https://roasr.com/api/mcp
   Auth:  Bearer pg_live_…        (Authorization header)
   

   B. Local stdio server (npx). Add to OpenClaw's MCP config (standard mcpServers shape):

   {
     "mcpServers": {
       "roasr": {
         "command": "npx",
         "args": ["-y", "roasr-mcp"],
         "env": {
           "ROASR_API_KEY": "pg_live_…",
           "ROASR_BASE_URL": "https://roasr.com"
         }
       }
     }
   }
   

   ROASR_BASE_URL is optional (defaults to https://roasr.com). Until the npm package is published, use "args": ["-y", "github:RoASr-com/roasr-mcp"]. Requires Node 18+.

4. Reload MCP servers in OpenClaw and confirm the roasr_* tools appear.

If no API key is set, or a tool returns an auth error (auth.invalid_api_key / 401): tell the user to sign up free at https://roasr.com, open Settings → API keys, create a key, and provide it (as the connector's Bearer token for option A, or ROASR_API_KEY for option B). Do not retry tools until a valid key is configured.