A data source is any database, warehouse, or SaaS API you connect to Sequel. Once connected, it's available to the in-app chat and to every AI tool you've authorized through the MCP server. This guide walks through adding your first one.
Cloud-hosted sources
Sequel connects to cloud-hosted data sources — managed Postgres/MySQL (RDS, Supabase, Neon, PlanetScale), warehouses like BigQuery and ClickHouse, and SaaS APIs like Stripe and Google Analytics. Make sure your source is reachable from the internet (or via the access method its guide describes).
Add a connection
Open Connections
In the Sequel dashboard, go to Connections and click New connection.
Pick a source type
Choose the source you want to connect — for example PostgreSQL, BigQuery, or Google Analytics. Each type asks for the credentials it needs.
Enter credentials
Depending on the source, this is a connection string, a host/port/user/password, a service-account key, or an OAuth sign-in. The per-integration guides under Integrations cover exactly what each source needs.
Test and save
Sequel verifies the credentials before saving. A green check means the connection is live and ready to query. If the test fails, double-check network access and credentials.
Database behind a firewall?
Sequel reaches your database from a fixed set of IP addresses. If your database sits behind a firewall, security group, or IP allowlist, add Sequel's egress IPs so the connection test can get through. The exact IPs are shown on the connection screen for database sources — copy them into your provider's networking settings (RDS security groups, Supabase/Neon network restrictions, Cloud SQL authorized networks, ClickHouse Cloud IP access list, and the like). SaaS sources that connect over OAuth or an API key don't need this.
What happens after you connect
- Schema discovery. Sequel reads your tables, columns, and relationships so agents can navigate the source without you spelling everything out.
- Available over MCP. The source immediately becomes queryable from any AI tool connected to your organization's MCP server.
- Scoped access. Connections belong to your organization. API keys and OAuth sessions only ever see the sources your org has connected.
Connecting more sources
Repeat the flow for every source you want Sequel to reach. Because Sequel can join across connections, adding a second and third source is where it gets powerful — see Chatting with your data for cross-source examples.