Three Fields. Your Cloudflare D1 Database, Live in MyD1.

MyD1 was built for exactly one database: Cloudflare D1. The connection flow reflects that — it asks only for what it needs, nothing more.

What the setup actually looks like

Open MyD1, click New Connection, and you see three fields:

That's it. Click Connect and you're in.

Creating your API token (2 minutes)

If you don't have a Cloudflare API token yet, here's the fastest path:

1. Go to dash.cloudflare.com/profile/api-tokens
2. Click Create Token → scroll to Custom token → Get started
3. In the permissions row, search for d1 — pick D1 from the dropdown
4. Choose Edit (read + write) or Read
5. Continue to summary → Create Token — copy it immediately (shown once)

What you get once connected

MyD1 fetches your schema immediately. From there:

• Browse any table in a sortable, filterable grid — click any cell to edit inline
• Run SQL in the editor with syntax highlighting, query history, and multi-statement support
• Export rows as CSV, TSV, or SQL — useful for backups or sending data to a teammate
• Right-click a table for ALTER TABLE shortcuts: add column, rename, drop, and more

Your credentials stay local

Your API token is stored in your macOS Keychain — never sent anywhere except directly to api.cloudflare.com. MyD1 has no backend server of its own. The connection you configure goes straight to Cloudflare.

The security banner in the connection form shows which Cloudflare account your token is scoped to, so you can confirm before connecting — especially handy if you manage multiple accounts.

Already have a D1 database?

Then you're 60 seconds away from browsing it visually. If you're still setting up your first Cloudflare D1 database, our visual getting-started guide walks you through creating one — no terminal required.