How to Connect Cloudflare D1 to VS Code

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

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

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

3

Ask VS Code about your data

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

Why VS Code

What VS Code does with your Cloudflare D1 data

Database access in Copilot Chat

Once configured, GitHub Copilot Chat can call Sequel tools to answer questions about your data. Ask about your schema, query examples, or check metrics — right in the Chat panel.

Team-wide setup with one commit

Commit .vscode/mcp.json to your repo and every developer on the team gets Sequel MCP configured automatically. Each team member provides their own API key.

Schema-aware code generation

Copilot can pull your actual database schema through Sequel and use it to generate more accurate SQL queries, migration files, and ORM models — based on what's really in your database.

Configuration

Add Sequel to VS Code

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

.vscode/mcp.json

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

Install

Install Cloudflare D1 MCP in VS Code

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 VS Code

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

Frequently asked questions

How do I connect Cloudflare D1 to VS Code?

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

What Cloudflare D1 data can VS Code access?

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

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

Does this work with GitHub Copilot in VS Code?

Yes. VS Code's MCP support is available in GitHub Copilot Chat (VS Code 1.99+). Create .vscode/mcp.json in your project root with the config above, and Sequel tools will appear in Copilot Chat.

Do I need the GitHub Copilot subscription?

VS Code MCP requires GitHub Copilot Chat (Individual, Business, or Enterprise plan). The MCP configuration itself is free; you only need a Sequel API key and a Copilot subscription.

Can I configure this globally instead of per-project?

Yes. Add the server configuration to your VS Code user settings.json under the `mcp.servers` key for global access across all projects.

Is the .vscode/mcp.json file safe to commit?

The config file is safe to commit — but never commit your actual API key in it. Use an environment variable reference or instruct team members to replace the placeholder with their own key.

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 VS Code today

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