Connect your data to OpenClaw

Turn your self-hosted OpenClaw agent into a data analyst that queries every source you've connected.

What OpenClaw can do with Sequel

One agent, every data source

OpenClaw hosts the MCP servers your agents share. Add Sequel once and every agent on the gateway can query Postgres, BigQuery, ClickHouse, Google Analytics, Stripe, and more — joined across sources in a single answer.

Scope exactly what the agent can touch

OpenClaw decides which MCP tools an agent sees through tool profiles and per-server tool filters. Expose Sequel's read tools to your marketing agent and keep the surface tight — access is a config line, not a credential hand-off.

Self-hosted, with credentials that never leave Sequel

OpenClaw runs on your infrastructure and talks to Sequel over an authenticated HTTPS MCP endpoint. Your database passwords and OAuth tokens stay encrypted in Sequel; OpenClaw only ever holds a scoped Sequel API key.

Example prompts

Everything you can ask OpenClaw about your data.

Ask in plain English. Sequel turns it into a query, runs it read-only, and OpenClaw hands back the answer. No SQL, no dashboards, no CSV exports.

Connect OpenClaw
What you can ask OpenClaw
  • Which landing pages lost the most organic traffic over the last 30 days?
  • Compare blended CAC across Google Ads and Meta Ads this quarter
  • What's our MRR trend for the last 6 months, by plan?
  • Join GA4 sessions with our Postgres signups and show conversion by channel
  • Which marketing campaigns drove the most revenue in Stripe last month?

Setup

Add Sequel to OpenClaw

Drop the Sequel MCP server into OpenClaw, then ask it anything about your connected data. Sequel is read-only by default and shows each query before it runs.

~/.openclaw/openclaw.json

{
  "mcp": {
    "servers": {
      "sequel": {
        "url": "https://api.sequel.sh/mcp",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer sql_your_api_key"
        }
      }
    }
  }
}

Sequel CLI

Install Sequel MCP to OpenClaw

The Sequel CLI installs Sequel into OpenClaw in one step — it signs you in, provisions a scoped API key, and writes the right config to the right place. No keys to copy by hand.

Prefer npm? npm install -g @sequelsh/cli@latest works too.

  1. 1

    Install the Sequel CLI

    One line installs the latest CLI with whatever package manager you have.

    curl -fsSL https://sequel.sh/install | sh
  2. 2

    Sign in

    Authenticate in your browser and pick an organization.

    sequel login
  3. 3

    Install into OpenClaw

    One command installs Sequel into OpenClaw and writes its MCP config.

    sequel install openclaw

Frequently asked questions

How do I add Sequel to OpenClaw?

Add the snippet above to your OpenClaw config (`~/.openclaw/openclaw.json`) under `mcp.servers`, or run `openclaw mcp set sequel '{"url":"https://api.sequel.sh/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer sql_your_api_key"}}'`, then reload the gateway. The Sequel CLI can do it for you with `sequel install openclaw`.

Which data sources can OpenClaw query through Sequel?

Any source you've connected in Sequel: PostgreSQL, MySQL, ClickHouse, BigQuery, Snowflake, Google Analytics, Search Console, Google Ads, Meta Ads, HubSpot, Stripe, and more. OpenClaw can only reach the connections your organization has set up.

Does Sequel use a remote (HTTP) MCP server?

Yes. Sequel is a hosted MCP server at https://api.sequel.sh/mcp. In OpenClaw that's a remote server — use `transport: streamable-http` and pass your key in the `Authorization` header, rather than a local stdio command.

Can I limit which agents or tools use Sequel?

Yes. OpenClaw controls which agents see MCP tools through tool profiles, and you can narrow Sequel to specific tools with per-server tool filters (`toolFilter` include/exclude) — so a dedicated marketing analyst agent gets exactly the access it needs and nothing more.

Is my database data sent anywhere it shouldn't be?

Query results flow to whichever model your OpenClaw agent runs, as context for the answer. Sequel never stores results permanently — they exist only for the duration of the tool call — and your raw credentials stay encrypted inside Sequel.

Put your data inside OpenClaw

Connect in minutes — then ask across all your data, not just one source.