How to Connect Cloudflare D1 to Cursor

Query your Cloudflare D1 data directly from Cursor 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 Cursor using the config on this page. Cursor 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 Cursor about your Cloudflare D1 data.

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

What you can ask Cursor
  • 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 Cursor's settings file (shown below). Swap in your API key from Settings → API Keys.

3

Ask Cursor about your data

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

Why Cursor

What Cursor does with your Cloudflare D1 data

Schema exploration in your editor

Ask Cursor to describe your database schema, find the right table for a feature, or understand relationships between tables — all without switching to another tool or reading through migrations.

Query data while you code

Need to check actual data while implementing a feature? Ask Cursor to pull examples from your connected databases. No more copy-pasting connection strings into a separate SQL client.

Catch data issues before they ship

Run queries against your staging or production database from inside the editor. Validate assumptions about data shape, volume, or edge cases while the code is still in front of you.

Configuration

Add Sequel to Cursor

Place this in .cursor/mcp.json and replace sql_your_api_key with a key from Settings → API Keys.

.cursor/mcp.json

{
  "mcpServers": {
    "sequel": {
      "url": "https://api.sequel.sh/mcp",
      "headers": {
        "Authorization": "Bearer sql_your_api_key"
      }
    }
  }
}

Install

Install Cloudflare D1 MCP in Cursor

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.

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

Add Sequel to Cursor

One click: the button above opens Cursor with Sequel pre-filled, and Cursor signs you in with your Sequel account. There is no key to paste.

Frequently asked questions

How do I connect Cloudflare D1 to Cursor?

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

What Cloudflare D1 data can Cursor access?

Cursor 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 Cursor's servers?

Query results are returned to Cursor 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. Cursor will be able to query all of them.

Does this work with Cursor Agent and Cursor Chat?

Yes. Once the MCP config is in your .cursor/mcp.json, Sequel tools are available in both Cursor Chat and Cursor Agent. The agent can call multiple tools in sequence to answer complex questions.

Should I use a project-level or global MCP config?

Use a project-level .cursor/mcp.json for team repos so all collaborators share the same MCP setup. For personal access, add the config globally at ~/.cursor/mcp.json instead.

Can Cursor modify my database through Sequel?

Sequel's query tools are read-only by default. The workbench tool can run Python code, which could write to files, but it runs in an isolated sandbox without direct database write access.

How do I share the Sequel MCP config with my team?

Commit .cursor/mcp.json to your repo. Each team member needs their own Sequel API key — replace the value of the Authorization header with their personal key from Settings → API Keys.

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 Cursor today

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