MCP servers

MCP (Model Context Protocol) servers tell the builder which tools you use, so it shapes the site around them — connect Stripe and it designs a checkout, GitHub and it adds a project showcase, and so on.

Adding servers

In the dashboard composer, click the + button → MCP servers.
Click a popular preset to add it instantly, or add your own by name with an optional Remote or Local endpoint.
Add as many as you like, then Save servers. They’re remembered for your next build.

Only non-secret metadata (name, category, and an optional endpoint) is kept in your browser to guide the design. Endpoints aren’t called by the published site — they inform how it’s built.

Popular presets

GitHub

Developer

a showcase/features section plus a “View on GitHub” CTA

Stripe

Payments

a pricing section with plan CTAs framed as checkout

Supabase

Developer

sign-up / login CTAs and data-backed feature sections

Notion

Productivity

content sections (FAQ, features, services) sourced from docs

Slack

Messaging

an integrations trust-bar or a workflow feature item

Shopify

Ecommerce

product / storefront sections with buy CTAs

HubSpot

Sales

a lead-capture contact form framed as CRM-connected

Google Sheets

Google

data-backed listing or stats sections

Linear

Productivity

roadmap / changelog-style copy in a features section

Resend

Marketing

a newsletter / contact form with email capture

Connectors vs MCP

Connectors wire a real public link into your site’s buttons (a Stripe checkout, a store). MCP servers give the builder context about your stack so it designs the right sections. You can use both together.

See all connectors