How to Connect Cloudflare D1 to Hermes

Query your Cloudflare D1 data directly from Hermes using Sequel’s MCP server. Ask questions in plain English, with no SQL, no dashboards, and no context switching.

Short answer

Connect Cloudflare D1 to Sequel, then add Sequel's MCP server to Hermes using the config on this page. Hermes can then query your live Cloudflare D1 data in plain English, with no connector code and no CSV exports. Both steps take a few minutes.

Example prompts

Everything you can ask Hermes about your Cloudflare D1 data.

Ask in plain English — Sequel translates it into a Cloudflare D1 query, runs it, and Hermes hands back the answer. No SQL, no dashboards, no CSV exports.

What you can ask Hermes
  • How many rows are in each table?
  • Show me the 20 most recently created users.
  • What is the conversion rate from signup to first purchase, by month?
  • Which customers signed up last quarter and are still active?
  • Find duplicate email addresses in the users table.

How it works

Three steps to get started

1

Connect Cloudflare D1 to Sequel

In your Sequel dashboard, go to Connections and add Cloudflare D1. Sequel handles authentication and schema discovery automatically.

2

Add Sequel to the agent

Copy the Sequel MCP configuration into Hermes's settings file (shown below). Swap in your API key from Settings → API Keys.

3

Ask Hermes about your data

Restart Hermes and start asking questions. "How many rows are in each table?" — and get a real answer backed by live Cloudflare D1 data.

Why Hermes

What Hermes does with your Cloudflare D1 data

An agent that grows into a data analyst

Hermes runs on your own hardware and gets better the more you use it. Point it at Sequel and it gains a durable new skill: answering data questions across your databases, warehouses, and SaaS tools in plain English.

One server, every source, joined on the fly

Sequel connects to databases, warehouses, product analytics, and ad platforms. Ask Hermes to line up Stripe revenue against Google Ads spend, or GA4 sessions against your Postgres signups, and the join happens at query time with no upstream data model.

Scope the tools, keep the keys safe

Hermes supports per-server tool filtering with include and exclude lists in its YAML config, so you choose exactly which Sequel tools the agent can call. Sequel runs read-only by default, and your database credentials stay encrypted in Sequel, never in the Hermes config.

Configuration

Add Sequel to Hermes

Place this in ~/.hermes/config.yaml and replace sql_your_api_key with a key from Settings → API Keys.

~/.hermes/config.yaml

mcp_servers:
  sequel:
    url: "https://api.sequel.sh/mcp"
    headers:
      Authorization: "Bearer sql_your_api_key"

Install

Install Cloudflare D1 MCP in Hermes

Pick your app and Sequel installs itself: a one-click link where the client supports it, that client’s own few steps where it doesn’t. Every route signs in with your Sequel account over OAuth, so there is no API key to copy and nothing to keep in sync.

Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex, Grok, Muse, dots and any other MCP app

Already have an MCP client?

https://api.sequel.sh/mcp

Add it as a remote (streamable HTTP) server and sign in when prompted. Skills come with it; nothing else to install. Manual setup per client

Choose your app

  • Claude

    One click, opens in the app

  • Cursor

    One click, opens in the app

  • VS Code

    One click, opens in the app

  • ChatGPT

    Turn on developer mode, then add Sequel. About two minutes.

  • Claude Code

    Run one command, then sign in with /mcp.

  • Codex

    Run one command, then sign in.

  • Gemini CLI

    Run one command, then sign in with /mcp auth.

  • Grok

    Add Sequel as a connector and sign in.

  • Grok Bot

    Paste this to the bot. It registers Sequel and asks you to sign in.

  • Muse

    Muse writes its own connector. One message is the whole setup.

  • dots

    Add Sequel in ChatGPT; your dot picks it up with no extra step.

  • OpenCode

    Add Sequel as a remote server from the OpenCode CLI.

  • Other MCP app

    Any client that speaks remote MCP can connect with this URL.

Frequently asked questions

How do I connect Cloudflare D1 to Hermes?

You need two things: (1) connect Cloudflare D1 to Sequel in your Sequel dashboard under Connections, and (2) add the Sequel MCP config to Hermes using the setup shown above. Once both are done, Hermes can query your Cloudflare D1 data directly.

What Cloudflare D1 data can Hermes access?

Hermes can access any data available through your Cloudflare D1 connection in Sequel. Use Sequel's search tool to discover available metrics and dimensions, then execute queries to pull the data you need.

Is my Cloudflare D1 data sent to Hermes's servers?

Query results are returned to Hermes as context within your conversation. Only the data you explicitly ask about is retrieved. Sequel never stores your query results permanently — they exist only for the duration of the tool call.

Do I need a Sequel account?

Yes. You need a Sequel account to connect Cloudflare D1 and generate an API key. Sign up free at sequel.sh — no credit card required. Then create a connection to Cloudflare D1 and generate an API key from Settings → API Keys.

Can I connect multiple Cloudflare D1 accounts?

Yes. Sequel supports multiple connections of the same type. If you have multiple Cloudflare D1 accounts or properties, add each as a separate connection in Sequel. Hermes will be able to query all of them.

How do I add Sequel to Hermes?

Add a `sequel` entry under `mcp_servers` in `~/.hermes/config.yaml` with Sequel's URL and your API key as an Authorization header, then run `/reload-mcp` in Hermes (or restart it). The Sequel CLI can write the config for you with `sequel install hermes`.

Which data sources can Hermes 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. Hermes can only reach the connections your organization has set up.

Is Sequel a remote MCP server or a local command?

Remote. Sequel is hosted at https://api.sequel.sh/mcp, so in Hermes you configure it as an HTTP server with a `url` and an Authorization header, rather than a local stdio `command`.

Can I limit which Sequel tools Hermes can use?

Yes. Hermes supports per-server `tools` filtering with include and exclude lists in `config.yaml`. You can expose only the read and query tools you want a given agent to have.

How does Sequel connect to Cloudflare D1?

Through Cloudflare's D1 REST API. You sign in with Cloudflare, approve the connection, and choose which D1 database to connect. Sequel stores the resulting tokens encrypted and refreshes them automatically, so there is no API token to create, paste, or rotate by hand.

Can one connection reach more than one database?

No. You pick exactly one D1 database when you connect, and that choice is baked into the connection. Sequel has no tool that can list or query any other database. If you want to query a second database, add a second connection.

Is it read-only?

Yes, and it is enforced by Cloudflare rather than by us. Sequel requests only the D1 Read scope, so Cloudflare itself rejects any write that reaches the D1 API. The tools Sequel exposes are query and schema introspection, and nothing in the connector can create, update, or delete data.

Do I need to move my data anywhere?

No. Sequel queries D1 directly over Cloudflare's API. Nothing is copied into a warehouse and there is no sync to schedule. Query results are stored so you can export them, but your tables stay where they are.

Connect Cloudflare D1 to Hermes today

Sign up free, connect your data sources, and start querying in minutes.