Connect your data to Muse

Give Meta's Muse one message and it builds its own connector to every source you've put in Sequel.

What Muse can do with Sequel

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.

Example prompts

Everything you can ask Muse about your data.

Ask in plain English. Sequel turns it into a query, runs it read-only, and Muse hands back the answer. No SQL, no dashboards, no CSV exports.

Connect Muse
What you can ask Muse
  • What were our top 10 customers by revenue last month?
  • How did last week's campaign do on spend, signups and revenue?
  • Which landing pages lost the most organic clicks versus last quarter?
  • Compare blended ROAS across Google Ads and Meta Ads against Stripe revenue
  • Show me week-over-week active users for the past 90 days

Setup

Add Sequel to Muse

Drop the Sequel MCP server into Muse, then ask it anything about your connected data. Sequel is read-only by default and shows each query before it runs.

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 Sequel 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.
  1. 1Paste the message above into Muse. It has no “add MCP server” screen; it builds the connector itself.
  2. 2Sign in to Sequel when Muse opens its secure credential flow. Never paste a key into the conversation.
  3. 3Muse tests each tool and saves the integration as a skill, so later chats already have it. Then ask it about your data.

Data sources

Connect any source to Muse

Frequently asked questions

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.

Can Muse change or delete my data?

Sequel is read-only by default and shows each query before it runs. Meta also does not review custom connectors, so keep Muse's approval policy on for anything that writes, and hold the connector to read-only while you are learning how it behaves.

Put your data inside Muse

Connect in minutes — then ask across all your data, not just one source.