How to Connect Cloudflare D1 to Muse
Query your Cloudflare D1 data directly from Muse 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 Muse using the config on this page. Muse 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.
Everything you can ask Muse about your Cloudflare D1 data.
Ask in plain English — Sequel translates it into a Cloudflare D1 query, runs it, and Muse hands back the answer. No SQL, no dashboards, no CSV exports.
- 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
Connect Cloudflare D1 to Sequel
In your Sequel dashboard, go to Connections and add Cloudflare D1. Sequel handles authentication and schema discovery automatically.
Add Sequel to the agent
Follow the steps below to add Sequel to Muse. It signs in with your Sequel account over OAuth, so there is no key to copy.
Ask Muse about your data
Restart Muse and start asking questions. "How many rows are in each table?" — and get a real answer backed by live Cloudflare D1 data.
Why Muse
What Muse does with your Cloudflare D1 data
One message, then it's a saved skill
Muse writes the MCP client itself on its VM, lists Sequel's tools, calls them end to end, and saves the result as a skill. You do not repeat the setup: the next conversation already knows how to reach your data.
A remote server is the shortest path
Muse runs in Meta's cloud, so it can reach a hosted streamable-HTTP server the same way any other client does, and it cannot reach a database on your laptop. Sequel is hosted and connects to your cloud databases and warehouses, which is exactly the shape Muse handles best.
Credentials stay out of the chat
Sign in through Muse's secure credential flow rather than pasting anything into the conversation: secrets live in its Secure Credentials Store and are swapped in at the network boundary. Your database passwords never leave Sequel at all.
Configuration
Add Sequel to Muse
Use it in Muse chat (iOS, Android, muse.ai, WhatsApp). Muse signs in with your Sequel account over OAuth, so there is no API key to paste.
Muse chat (iOS, Android, muse.ai, WhatsApp)
Build a custom connector to Sequel. It is a remote MCP server over streamable HTTP at https://api.sequel.sh/mcp and it uses OAuth, so ask me to sign in through the secure credential flow. Connect to it with the official MCP SDK, test every tool end to end, and save it as a reusable skill so you can answer questions about my data in any conversation.
Install
Install Cloudflare D1 MCP in Muse
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 Muse
Send to Muse
Build a custom connector to Sequel. It is a remote MCP server over streamable HTTP at https://api.sequel.sh/mcp and it uses OAuth, so ask me to sign in through the secure credential flow. Connect with the official MCP SDK, test every tool end to end, and save it as a reusable skill.
- 1Paste the message above into Muse. It has no “add MCP server” screen; it builds the connector itself.
- 2Sign in to Sequel when Muse opens its secure credential flow. Never paste a key into the conversation.
- 3Muse tests each tool and saves the integration as a skill, so later chats already have it. Then ask it about your data.
Other AI agents
Connect Cloudflare D1 MCP to any agent
Claude
Use Claude to query your databases, explore schemas, and build analyses — all from one conversation.
Cursor
Query your databases and explore schemas without leaving your code editor.
ChatGPT
Connect ChatGPT to your databases and get data-backed answers in every conversation.
VS Code
Get database access inside VS Code Copilot without leaving your editor.
Windsurf
Give Windsurf's Cascade AI access to your databases — query data without leaving your editor.
Zed
Connect Zed's AI assistant to your databases for real-time data access while you code.
Gemini
Connect Google Gemini to your databases for grounded, data-backed answers.
Claude Code
Query your databases directly from the Claude Code CLI — without leaving your terminal.
Codex
Give OpenAI Codex CLI real-time database access for data-grounded coding sessions.
OpenClaw
Turn your self-hosted OpenClaw agent into a data analyst that queries every source you've connected.
Hermes
Give Nous Research's Hermes agent read access to every database and marketing tool you've connected.
Grok Bot
Tell your Grok bot to add Sequel and it can query every database and marketing tool you've connected.
Muse
Give Meta's Muse one message and it builds its own connector to every source you've put in Sequel.
dots
Add Sequel once in ChatGPT and your dot can answer data questions on its own, day and night.
Other data sources
Connect other sources to Muse
PostgreSQL
Query your PostgreSQL database in plain English. No SQL required.
MySQL
Instant insights from your MySQL database. Ask in plain English.
ClickHouse
Real-time analytics on ClickHouse at any scale, in plain English.
BigQuery
Query petabytes of BigQuery data in plain English.
Google Sheets
Query, write, and manage Google Sheets with AI.
Google Analytics 4
Ask your GA4 data anything. No SQL, no dashboards.
Google Search Console
Unlock your SEO data with natural language. No exports, no pivot tables.
MCP Server
Connect any MCP-compatible server and query it with AI in seconds.
Stripe
Ask your Stripe data anything. MRR, churn, refunds — answered in plain English.
Polar
Ask your Polar revenue, subscriptions, and usage data anything — in plain English.
Dodo Payments
Ask questions about payments, subscriptions, refunds and payouts in plain English.
PostHog
Ask your PostHog product data anything — with HogQL under the hood.
Mixpanel
Conversational analytics on your Mixpanel events, funnels, and retention.
Amplitude
Query your Amplitude taxonomy, funnels, and dashboards in plain English.
HubSpot
Your AI analyst for HubSpot contacts, deals, tickets, and pipelines.
Ahrefs
Ask your Ahrefs SEO data anything: backlinks, keywords, and traffic.
Apollo.io
Ask your Apollo.io prospects, contacts, and accounts anything, in plain English.
Instagram organic analytics — post engagement, reach, and audience insights in plain English.
Frequently asked questions
How do I connect Cloudflare D1 to Muse?
You need two things: (1) connect Cloudflare D1 to Sequel in your Sequel dashboard under Connections, and (2) add the Sequel MCP config to Muse using the setup shown above. Once both are done, Muse can query your Cloudflare D1 data directly.
What Cloudflare D1 data can Muse access?
Muse 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 Muse's servers?
Query results are returned to Muse 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. Muse will be able to query all of them.
Can Meta Muse use MCP servers?
Yes, though not through a settings menu. Muse builds a custom connector on its own VM with the official MCP SDK, connects over streamable HTTP, and saves the integration as a skill. Remote servers like Sequel are the easy case; a server on your own laptop is not reachable from Meta's cloud.
How do I add Sequel to Muse?
Send Muse one message naming Sequel, its server URL (https://api.sequel.sh/mcp) and what you want to be able to ask. It will ask whether the server is HTTP or stdio and how it authenticates, build the connector, test the tools, and save the skill. Sign in when it opens the secure credential flow.
Does Muse see my Sequel credentials?
Only if you paste them into the chat, which you should not do. Keys entered through Muse's credential prompt are held by a daemon outside the agent runtime and injected at the network edge. Better still, sign in to Sequel over OAuth: then there is no key at all, and your database passwords stay encrypted in Sequel either way.
Which data sources can Muse query through Sequel?
Any source you have connected in Sequel: PostgreSQL, MySQL, ClickHouse, BigQuery, Snowflake, Google Analytics, Search Console, Google Ads, Meta Ads, HubSpot, Stripe, and more. Muse can only reach the connections your organization has set up.
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 Muse today
Sign up free, connect your data sources, and start querying in minutes.