Superblocks

Official MCP Paid, self-serve RevOps Infra RESEARCHED Checked 2026-09-07 CLI: superblocks

RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: superblocks.com · entry id 06-superblocks · source 06-revops-infra.md line 428

What it does

A platform for building - and more distinctively, governing - AI-generated internal apps: lets business teams build apps (including importing prototypes from Claude, Lovable, or Replit) while giving IT/Security a control layer over integrations, permissions, and auditing.

AI features, separated from automation with an AI label on it

A "Clark AI agent" for app development plus prototype-import from AI coding tools; the more unique angle is AI-app governance (usage monitoring, permission auditing, threat detection across AI-built apps) rather than Superblocks itself being a novel generative engine - much of the "AI" framing here is about controlling other tools' AI output.

RevOps role

Adjacent to Retool - an internal-app builder, but positioned specifically as the IT/security control plane for a world where GTM/ops teams are building their own AI-assisted apps; not itself a core data-pipeline tool.

MCP server

Status bucket

Official MCP

Auth

unknown - the announcement doesn't specify the auth method; the feature is Enterprise-only, implying an admin/OAuth-gated setup, but this isn't documented in what was found.

Parsed URLs

2 found in the mcp_url field

Endpoint probe

docs page, not an endpoint

Docs URL

https://superblocks.com/blog/superblocks-mcp

Probed

2026-09-04, HTTP 200

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-09-07. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://api.superblocks.com/mcp ; https://superblocks.com/blog/superblocks-mcp

What this server exposes

Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the tools index.

Command line

Binary

superblocks

Status

official CLI, first party

Strongest evidence

npm

Harvested

2026-09-27

Install, as the source shows it:

npm install -g @superblocksteam/cli

quoted from https://www.npmjs.com/package/@superblocksteam/cli on 2026-09-27, via npm

npm install -g superblocks-cli

quoted from https://www.npmjs.com/package/superblocks-cli on 2026-09-27, via npm

npm install -g @superblocksteam/cli-ephemeral

quoted from https://www.npmjs.com/package/@superblocksteam/cli-ephemeral on 2026-09-27, via npm

Packages seen, with the version on 2026-09-27:

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

Access gate

Gate bucket

Paid, self-serve

Can a solo operator reach it

Yes, by paying, no sales call

api_gate, verbatim from the file:

paid - no free tier; cheapest self-serve entry is the Teams plan at $100/mo annual with a 14-day free trial. The MCP feature itself is Enterprise-exclusive, so a solo operator can use the base product self-serve but cannot reach the MCP capability without an enterprise plan.

API documentation

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

On GitHub

github.com/superblocksteam tied to the vendor by rule 3, account website https://www.superblocks.com has the vendor's domain, confidence strong

Public repositories

14, forks excluded, as read on 2026-09-08

Mention MCP

0 of them

Look like CLIs

0 of them

Latest push

2026-09-03

The five most recently pushed, on 2026-09-08:

Repository	Kind	Description	Stars	Pushed	Latest release
terraform-aws-superblocks	infrastructure	Superblocks Terraform Module - AWS	1	2026-09-03	v1.5.3
cloud-prem-migration-skills	other	Repository of skills and scripts for helping migrate resource between a Cloud and Cloud Prem instance.	0	2026-05-13
sync-action	infrastructure	Github Action to sync Superblocks resources	1	2026-03-12	v1.0.1
terraform-google-superblocks	infrastructure	Superblocks Terraform Module - Google	1	2026-03-04	v1.1.1
export-action	infrastructure	Github Action to pull changes for Superblocks Applications	1	2025-11-07	v1.0.15

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

Jobs it can do

No job tag on this entry.

Reason recorded by the tagging pass: no-job-fits. Internal-app building and AI-app governance. run-automation-workflow is not what it does and there is no app-builder job.

981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.

Sources

4 source URLs. Raw sources field, verbatim:

https://superblocks.com/, https://superblocks.com/pricing, https://superblocks.com/blog/superblocks-mcp, https://api.superblocks.com/mcp

Notes, verbatim from the file

Superblocks MCP is a different category of MCP than the rest of this file - it isn't "connect an AI agent to move/query GTM data," it's "give IT admins programmatic visibility and control over every AI-built app, integration, and permission in the org" (identify malicious packages, detect unusual write patterns, alert on permission changes, correlate audit logs to builders). 2026-09-07: https://api.superblocks.com/mcp returned 401 {"responseMeta":{"status":401,"message":"Authentication required."...}} while the control path https://api.superblocks.com/zzznotamcp returned 404 "no Route matched with those values" - so /mcp is a real registered route, not a blanket auth wall (https://api.superblocks.com/mcp).

Provenance

Entry id

06-superblocks

Source file

06-revops-infra.md

Source line

428

Tier

RESEARCHED

last_checked

2026-09-07

Data baked

2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.