Connectors (previously Integrations / Marketplace) is the place to browse, connect, and manage Databases, APIs, and MCP servers that Dreambase Skills and dashboards can pull from.

Browsing the Connector Marketplace

The Connectors page is a browsable catalog: a searchable, category-filterable grid of pre-built connectors, each shown as a card with the provider's logo, a one-line description, and an mcp or api badge showing how that connector is implemented under the hood. Categories include Analytics, Communication, CRM, Developer Tools, Payments, and Productivity, plus a separate Manage tab for your workspace's already-connected instances.

The catalog includes Supabase, ClickHouse, BigQuery, Stripe, Polar, RevenueCat, PostHog, GitHub, Sentry, Vercel, Linear, HubSpot, Slack, Resend, Twilio, and Ordinal. Click View details on any card to connect it; each opens the relevant Database, API, or MCP setup flow described below.

Databases

• Manage Databases lists every Supabase project connected to this workspace, with a healthy/unhealthy connection indicator per project.

• Click + Add Database to connect another Supabase project. The dialog supports Connect another org, so a single workspace can pull from multiple Supabase organizations, not just multiple projects within one org (this is the Multi-Supabase feature. See its own doc for a deeper walkthrough).

• Click into a project to see its tables/schema (what used to be described as the "Data Dictionary" now lives here, per-project, rather than as a separate top-level concept).

APIs

Register direct REST/API connections that Dreambase can call during analysis, separate from your Supabase database(s):

• Add API to open the connection dialog.

• Fields: Name, API Type (e.g. REST, GraphQL — or supabase specifically when connecting a custom schema via the API path), Endpoint URL, Auth Type (Bearer, X-Api-Key, or custom headers), Auth Token, Custom Headers, HTTP Method.

• Table columns for existing connections: Name, Schema, Context, Created, Actions.

• Optional flags: Schema (expose the API's schema for better typing) and AI Context (make the integration available to agents automatically).

• Once saved, Dreambase automatically scans the API to generate schema documentation — no manual field mapping needed. New capabilities show up across dashboards, Skills, and Slack without extra wiring.

MCP

Register Model Context Protocol servers whose tools become available to every Skill and Dashboard's Analyst Agent:

• Add MCP to register a server.

• Fields: Name, optional Description, Transport Type (Streamable HTTP recommended), Server URL, Custom Headers (JSON), optional Schema Definition, additional Client Configuration.

• Test the connection before saving.

• Existing connections list: Name, Type, Command/URL, Created, Actions.

Connecting to sources from an agent (via MCP)

Agents using the Official Dreambase MCP can check and connect sources without leaving the chat. list_connectors shows every connector the workspace can use and whether it's connected. For Supabase, GitHub, Slack, PostHog, ClickHouse, BigQuery, and Ordinal, request_connector_connection returns a link you open to authorize the connection, and get_connection_request tells the agent once it's live. Other connectors are connected here in the Dreambase app. Every connector except Supabase needs an active workspace subscription.

Once a source is connected, list_connections, get_connection, and search_connection let the agent see its tables, enabled API endpoints, or enabled MCP tools. See Datasets for how agents build datasets from them. If get_connection has to scan an MCP server for the first time, the tools it finds stay disabled until a workspace admin approves them here.