Skip to main content

​
Overview

The Builder MCP lets you build in Superblocks without leaving the AI tools you already use. Connect Superblocks to Claude (and, soon, Slack, ChatGPT, and Teams) through the Model Context Protocol, then ask in plain language to import, build, edit, or publish an app. Superblocks does the work and sends back an editor or deployed link. Many builders and business users already prototype in Claude and want to take that work to production in a governed way. The Builder MCP meets them where they are, with no separate onboarding and no new tool to learn. Whatever tool a builder starts in, the app they ship lands on Superblocks with your organization’s guardrails already applied.

​
What you can do

  • Start a new app: Ask Claude to build a new app in Superblocks and get an editor link back.
  • Import an existing app: Bring a prototype you built in Claude into Superblocks. It imports the app, replaces integrations with your governed data sources, and adds platform authentication and RBAC.
  • Edit an app: Describe a change and Clark starts building against your existing app.
  • Publish an app: Ask to deploy and get a deployed link back, after security agent scans and policy agents run.

​
How it works

​
1. Set up the MCP

An admin or builder connects the Superblocks Builder MCP in their AI tool (Claude first, then Slack). Setup instructions will be provided at launch.

​
2. Ask in natural language

Prompt the tool the same way you already do:

​
3. Plan and refine with Clark

Clark works with you conversationally through the MCP, just like in the Superblocks UI. Before building, it can ask clarifying questions about functionality, data, and design, inspect your integration metadata, and propose a plan, right in the chat. You answer in the same thread, and Clark refines its approach before it starts building. See Plan & Build modes for how this works in the editor. Where relevant, the Builder MCP replies with an editor link, a deployed link, and, depending on the platform, screenshots or a short video so you can review the result before opening Superblocks.

​
Preview your app in chat with MCP Apps

Beyond links and screenshots, we’re building toward rendering the app’s live HTML interface directly inside the conversation using MCP Apps, the MCP extension for interactive UI. Instead of switching to a browser tab, you’d see and click through the app you just built without leaving Claude. MCP Apps make this a good fit for the Builder MCP:
  • Context preservation: The app renders alongside the conversation that created it, so you can iterate (“make the table sortable”) and immediately see the result in place.
  • Sandboxed and secure: The interface runs in a host-controlled sandboxed iframe that can’t access the surrounding page, so previews stay safe to render.
  • Bidirectional: The rendered app can call back through the Builder MCP for fresh data, and your prompts can push updates into the running preview.
You’d still get the editor and deployed links; the in-chat render is an additional way to review before you open Superblocks.

​
Governed by default

Prototypes built directly in AI tools tend to hardcode credentials and reinvent auth and permissions app by app, which becomes a security risk and tech debt as they multiply. Superblocks applies governance at the platform level rather than per app: connected integrations, authentication, RBAC, and policies are managed centrally, so a change made once applies to every app. Apps that come in through the Builder MCP inherit that same model automatically.
  • Identity-aware: The MCP uses your identity, resolved through your SSO provider, and maps it to your permissions in Superblocks so builders only do what their role allows.
  • RBAC and integrations: Imported apps are rewritten to use your connected integrations and platform-managed authentication and RBAC instead of hardcoded credentials.
  • Security and policy agents: Publishing runs security agent scans and policy agents, and every app keeps native version control and one-click deploy.

​
Supported platforms

​
Builder MCP vs. Admin MCP

Superblocks offers two MCPs: the Builder MCP is for building apps, and the Admin MCP is for administering the platform.

Import an app

Bring prototypes from Claude, Replit, Lovable, v0, and more into Superblocks today

Admin MCP

Connect AI coding agents like Cursor and Claude Code to administer your Superblocks org