Dreambase now supports the full MCP authorization spec across every integration in our Plugin Marketplace. Here is what that means technically and what you can build with it.
The Auth Stack
Dreambase implements the full MCP authorization standard across every marketplace integration. Connections use OAuth 2.1 with PKCE, meaning the authorization handshake is handled automatically between Dreambase and the remote MCP server without you ever managing credentials manually. Dynamic client registration lets new integrations configure themselves programmatically, so connecting a new source is a single browser-based OAuth flow.
All remote MCP connections in Dreambase use Streamable HTTP transport, which replaced SSE as the standard for remote MCP servers. Each connection is scoped to exactly the permissions you grant, auditable, and revocable, no API keys stored anywhere in your stack.
What Each Integration Exposes
ClickHouse runs a remote MCP server with three core tools: run_select_query for
executing SQL against your ClickHouse cluster, list_databases to enumerate databases, and
list_tables to enumerate tables within a database. Dreambase agents use these to run
analytical queries across billions of rows and join results directly with Supabase data at
query time.
PostHog exposes a rich MCP toolset including hogql-schema to introspect available
tables and columns, query-generate-hogql-from-question to generate HogQL from natural
language, query-run to execute trend, funnel, paths, or HogQL queries, and insight-query
to run saved insights. Dreambase agents use these alongside Supabase joins to answer product
questions that span behavioral events and structured database records.
Linear hosts its MCP server at https://mcp.linear.app/mcp using Streamable HTTP with
OAuth 2.1 and dynamic client registration. Clients that do not yet support remote MCP can use
the mcp-remote module for backwards compatibility. Exposed tools cover finding, creating, and
updating issues, projects, and comments — pulling Linear project state directly into Dreambase
dashboards alongside product and revenue metrics.
GitHub exposes repository activity, commit history, PR data, and contributor analytics
that Dreambase agents surface alongside Linear velocity metrics and Sentry error rates.
How Dreambase Uses This
When you connect a source in the Dreambase Plugin Marketplace, the OAuth flow handles
authorization and the connection is stored centrally. From that point, you define a Skill that
bundles the connected sources with your business logic, KPI definitions, and visualization
rules. The Dreambase agent then has typed, authorized access to every source in the Skill and
can join across them at query time.
A practical example: a Revenue and Product Health Skill might pull run_select_query results
from ClickHouse for event volume, query-run from PostHog for funnel completion rates, and
join both against Supabase subscription records — all resolved into a single cached dataset
in Supabase Storage via DuckDB transforms at the edge.
Existing Marketplace Integrations
The same OAuth flow covers Stripe, Polar, HubSpot, Sentry, Vercel, and Resend. Any REST API
with an OpenAPI spec can be connected by pasting the OpenAPI URL directly. Skills via CLI,
API, and MCP are coming soon so external agents can consume Dreambase intelligence directly.
Reach out if you want early access.
Top comments (0)