Skip to main content

Overview

Superblocks in Claude lets you build in Superblocks without leaving Claude. Add Superblocks to Claude, then ask in plain language to import, build, edit, or publish an app. Clark does the work in Superblocks, and Claude opens your app in its built-in browser so you can click through it. Many builders and business users already prototype in Claude and want to take that work to production in a governed way. Superblocks in Claude meets them where they are, with no separate onboarding and no new tool to learn. The apps they ship land 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. Clark 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 Code Security policies run.

Set up Superblocks in Claude

An admin of your Claude organization adds the Superblocks plugin once. Each user then installs it from the plugin marketplace in Claude Desktop.

Admins: add the plugin to your organization

You need the Owner or Primary Owner role in a Claude Team or Enterprise organization.
1

Download the plugin

Download the Superblocks plugin ZIP provided by your account team. Do not unzip it.
2

Upload the plugin

In Claude, go to Organization settings > Plugins & skills, select Add > Upload a plugin, and choose the plugin ZIP.
3

Make the plugin available to install

On the Inventory tab, open the menu at the end of the Superblocks row. Select Default access, then choose Available to install. Users in your organization can now install Superblocks from the plugin marketplace.
4

Check that the built-in browser is on

In Organization settings > Cowork, make sure Built-in browser is turned on so users can open their Superblocks apps in it.

Admins: update the plugin

When your account team sends a new version of the plugin ZIP:
  1. Go to Organization settings > Plugins & skills and select the Superblocks row on the Inventory tab.
  2. Open the plugin’s menu, select Upload new version, and choose the new ZIP.
  3. In Version history, open the newly uploaded version’s menu and select Make this the current version.
  4. Confirm that the newly uploaded version is marked Current. This is the version served to members.
Uploading the ZIP alone does not make it current. Once it is marked Current, users get the new version the next time they start a session. To roll back, go to the plugin’s Version history, open an earlier version’s menu, and select Revert to this version. See Manage plugins for your organization in the Claude docs for more plugin settings.

Users: install the plugin

1

Add the plugin

In Claude Desktop, open Cowork and select + > Plugins > Manage Plugins. On the Discover tab, find Superblocks and select Add, then accept the prompts that appear. If Superblocks isn’t listed, ask your Claude organization admin to add it.
2

Use the built-in browser

In Claude Desktop, go to Settings > Cowork and set Preferred browser to Built-in browser so Claude opens your Superblocks apps there. If Built-in browser isn’t an option, ask your Claude organization admin to turn it on.
3

Configure your Superblocks instance

Start a new Cowork session and run /configure. When prompted, enter your Superblocks instance URL, such as https://app.superblocks.com for Cloud US.
4

Sign in

Complete the OAuth sign-in flow in the browser window that opens. You can now build with Superblocks in Claude.

How it works

1. Ask in natural language

Prompt Claude the same way you already do:

2. Plan and refine with Clark

Clark works with you conversationally in Cowork, 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 in Cowork. You answer in the same Cowork session, and Clark refines its approach before it starts building. See Plan & Build modes for how this works in the editor.

3. Open your app in Claude’s browser

Claude opens your app in its built-in browser, where you can click through it and verify your changes. Return to Cowork to ask for another change, such as “make the table sortable.” When you’re ready, open the app in the Superblocks editor or share its deployed link.

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 you build from Claude inherit that same model automatically.
  • Identity-aware: Claude acts as you, with your identity resolved through your SSO provider and mapped 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.
  • Code Security: Publishing runs Code Security policies, and every app keeps native version control and one-click deploy.

Superblocks in Claude vs. Admin MCP

Superblocks in Claude is for building apps. The Admin MCP is for administering the platform from AI coding agents like Cursor and Claude Code.

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