How to Connect PostHog to Muse

Query your PostHog 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 PostHog to Sequel, then add Sequel's MCP server to Muse using the config on this page. Muse can then query your live PostHog data in plain English, with no connector code and no CSV exports. Both steps take a few minutes.

Example prompts

Everything you can ask Muse about your PostHog data.

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

What you can ask Muse
  • How many unique users triggered $pageview yesterday, by country?
  • Show me the signup → activation funnel for users created in the last 30 days.
  • What's the 7-day retention of users in the 'Power users' cohort?
  • Which 10 feature flags have the most evaluations this week?
  • Compare conversion rate by browser for the checkout funnel.

How it works

Three steps to get started

1

Connect PostHog to Sequel

In your Sequel dashboard, go to Connections and add PostHog. Sequel handles authentication and schema discovery automatically.

2

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.

3

Ask Muse about your data

Restart Muse and start asking questions. "How many unique users triggered $pageview yesterday, by country?" — and get a real answer backed by live PostHog data.

Why Muse

What Muse does with your PostHog 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 PostHog 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.

Frequently asked questions

How do I connect PostHog to Muse?

You need two things: (1) connect PostHog 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 PostHog data directly.

What PostHog data can Muse access?

Muse can access any data available through your PostHog 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 PostHog 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 PostHog and generate an API key. Sign up free at sequel.sh — no credit card required. Then create a connection to PostHog and generate an API key from Settings → API Keys.

Can I connect multiple PostHog accounts?

Yes. Sequel supports multiple connections of the same type. If you have multiple PostHog 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 do I connect PostHog to Sequel?

Create a Personal API Key in PostHog under Settings → Personal API Keys with read-only scopes: query:read, event_definitions:read, property_definitions:read, insight:read, cohort:read, project:read. Paste it into Sequel along with your host (US Cloud, EU Cloud, or self-hosted base URL) and your numeric project ID, then click Test.

Does Sequel work with PostHog Cloud and self-hosted PostHog?

Both. For PostHog Cloud, use https://us.posthog.com or https://eu.posthog.com. For self-hosted, point the host field at your own base URL (no trailing slash) — as long as the same Personal API Key endpoints exist, Sequel works identically.

What is HogQL, and why does it matter?

HogQL is PostHog's SQL dialect that runs against the raw events table. It's strictly more expressive than the insight builder — joins, window functions, conditional aggregations. Sequel writes HogQL under the hood, which is why it can answer questions a built-in insight can't.

Can Sequel write or change anything in PostHog?

No. The connector only ships read-only tools (HogQL query, list events, list properties, list insights, list cohorts) and works with read-only scopes. The agent cannot create insights, dashboards, cohorts, or feature flags.

Connect PostHog to Muse today

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