OpenClaw plugins

01

The @superagnt/superagnt plugin

openclaw plugins install @superagnt/superagnt
openclaw superagnt connect

openclaw superagnt connect saves an MCP server named superagnt for https://mcp.superagnt.com/mcp, then runs OpenClaw's OAuth login for it. Approve the consent screen in the browser: it also creates a superagnt_ account if you have none. From then on your OpenClaw sessions get the workspace's tools. Run it again when the login needs renewing; if the server is already saved, it goes straight to the login.

Without the plugin, the same connection is the two openclaw mcp commands that connect runs. Keep --auth oauth: openclaw mcp login refuses a server saved without it.

openclaw mcp add superagnt --url https://mcp.superagnt.com/mcp --transport streamable-http --auth oauth
openclaw mcp login superagnt

The plugin adds the skills below on top of it. Which tools the server serves is set per workspace, by tool family, and the plugin turns nothing on: see Tools and tool families.

The bundled skills carry a superagnt- prefix, because skill names in OpenClaw are global:

The plugin also adds these commands to openclaw:

02

Data and connection plugins

Each of these registers native tools for one data source or one connection, except @superagnt/social-data, which carries all nine data sources in the table below.

Data sources

These call https://api.superagnt.com/v1/data/<source> and spend credits like any data source call: each response carries its price in meta.costCents (see What you pay). @superagnt/social-data registers over 250 tools at once, so install the per-source plugin when the agent needs one source.

The webhook tools in @superagnt/social-data are superagnt_webhooks_create_endpoint, superagnt_webhooks_list_endpoints, superagnt_webhooks_get_endpoint, superagnt_webhooks_delete_endpoint, superagnt_webhooks_list_deliveries, superagnt_webhooks_ack_delivery and superagnt_webhooks_ack_deliveries. They manage the endpoints and deliveries described on Receiving webhooks.

Connections

These call https://api.superagnt.com/v1/connections/<vendor> and run on the vendor account your workspace connected in the superagnt app, so connect the vendor first (Connections). The calls cost no superagnt_ credits; the vendor's own limits and billing apply.

Set the API key

Create an API key in the superagnt app (see Managing API keys). When the gateway loads a data or connection plugin, the plugin takes the first key it finds:

1. 01apiKey in the plugin's config in openclaw.json.
2. 02The SUPERAGNT_API_KEY environment variable of the gateway process.
3. 03apiKey in ~/.superagnt/config.json.

The environment variable covers every plugin at once. Export it in the shell that starts the gateway, or add it to ~/.openclaw/.env, which OpenClaw reads when it starts:

export SUPERAGNT_API_KEY="agnt_live_..."

To give one plugin its own key, set it in that plugin's entry, under its plugin id:

{
  "plugins": {
    "entries": {
      "social-data": {
        "enabled": true,
        "config": {
          "apiKey": "agnt_live_..."
        }
      }
    }
  }
}

The plugin reads the key once, when it loads, so restart the gateway after you change it: openclaw gateway restart.

Tools and results

After the prefix, most tool names are built from the endpoint's operation id and keep its capitalization (names that would run past 60 characters are shortened): superagnt_linkedin_Get_Company_Details calls GET /v1/data/linkedin/get-company-details. A tool takes the endpoint's parameters as named arguments:

{
  "name": "superagnt_linkedin_Get_Company_Details",
  "description": "Get Company Details",
  "parameters": {
    "type": "object",
    "properties": {
      "username": { "type": "string", "description": "username" }
    },
    "required": ["username"]
  }
}

These names belong to the plugins. Over MCP the same operations are named in lower case under data_<source>_ and connection_<vendor>_, and most are listed inside grouped tools: see Tools and tool families.

A tool returns the REST response body unchanged: { success, data, meta } when the call worked, and success: false with an error object when it did not (see Reading errors). The one exception is any 401, which comes back as { "error": "Invalid or expired API key. Get a new key at https://app.superagnt.com/dashboard" } even when a connection call failed because the vendor rejected the connected credential.

03

Update and remove

openclaw plugins update social-data
openclaw plugins uninstall social-data

A data or connection plugin's tools are fixed for its version: new endpoints reach you with an update.

04

Troubleshooting