Supero Apps MCP server
Commit Nov 7, 2026Lets an AI client design schemas, run CRUD operations, and deploy multi-tenant SaaS applications via 64 specialized tools.
Also known as supero-platform/supero-apps
- Stars
- 3
- Tools
- โ
- Downloads, 30 days
- โ
- Latest version
- โ
- Last commit
- Nov 7, 2026
- License
- MIT
What is Supero Apps MCP?
Supero Apps lets an AI client design schemas, run CRUD operations, and deploy multi-tenant SaaS applications via 64 specialized tools.
Summary generated from the project's README
About Supero Apps MCP server
Designing schemas, managing CRUD operations, and deploying multi-tenant SaaS applications is what developers achieve using supero-apps. This MCP server provides 64 specialized tools that allow an AI client to transform a simple sentence into a live, functional URL. It is designed for developers who want to skip the tedious work of building APIs, authentication, and admin panels by using a schema-driven approach.
Users connect their editor to the platform via an HTTP transport using an API key. The server operates by inheriting the user's existing permissions, meaning any row scoping or field-level access control policies applied to a user are identically enforced on the AI agent. This ensures the assistant is bounded by the same security constraints as a human user. The system supports various application types, including healthcare, finance, and commerce, with built-in server-side enforcement for role-based access control.
What you can do with it
- 1Deploy a new SaaS applicationAn AI assistant can take a single requirement and turn it into a live, hosted web application.
- 2Extend existing application featuresYou can ask an AI to add specific business logic, such as a waitlist system, to a healthcare application.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 15, 2026Full report โNot verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work ยท What to fix for more points
- Source repository linked and reachablesupero-platform/supero-apps is public and reachablegithub.com/supero-platform/supero-apps โPass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html โPass
- Commit or release in the last yearLast commit or release 2026-11-07github.com/supero-platform/supero-apps โPass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubSupero Apps
19 applications. Full source. Clone one onto your own domain and run it.
Every app in this repo is running live right now โ and this is the code behind it. Multi-tenant, role-based, schema-driven. No npm, no build step. MIT app source, open SDK, your data exportable over the API โ see how this works, honestly.
Live apps ยท Quickstart ยท Build with Claude ยท Platform docs ยท Ask a question
See it before you install it
lumen.supero.live is one of the 19, running the code in
apps/healthcare/lumen. The login page lists every demo account
with its role and password โ click one and you are in. No signup, nothing to install.
Sign in as the front-desk user, then sign out and back in as the patient. The patient's
record is missing clinical_notes โ and nothing in ui/app.js is doing that. The rule is
five lines in apps/healthcare/lumen/setup.py.
Or check it from a terminal in ten seconds, no signup, no clone of your own domain:
git clone https://github.com/supero-platform/supero-apps
cd supero-apps/verify && ./02-rbac-enforcement.sh
That script logs into the live insurance demo as a claims adjuster and as a
policyholder, finds one claim both can see, and compares the two responses. The
adjuster gets fraud_score and internal_notes; the policyholder gets the same
record without them. verify/ explains what it proves โ and what it
does not.
Then run it yourself, in about two minutes
New here? Start with lumen โ it is the smallest app in the repo and the one the docs
follow.
git clone https://github.com/supero-platform/supero-apps
cd supero-apps/apps/healthcare/lumen
cp .env.example .env # set SUPERO_DOMAIN, SUPERO_ADMIN_EMAIL and SUPERO_PASSWORD
./run.sh
run.sh creates a venv, installs the supero SDK, registers your domain, uploads the
schemas, seeds demo data, wires up roles โ then serves the app at http://localhost:5663.
That takes about 90 seconds on a cold machine with an empty pip cache โ roughly 10
seconds of install and 60-odd of platform setup. Call it two minutes with the time it takes
you to fill in .env.
You do not need an account, an invite, or a credit card. Domain registration is open.
The name you put in SUPERO_DOMAIN becomes yours if it's free.
Prefer containers?
docker compose upworks identically.
The apps
Each one is a complete, multi-tenant application โ public storefront and admin panel, with role-based access enforced on the server, not in the UI.
๐ฉบ Healthcare & Life Sciences
| App | What it is | Live |
|---|---|---|
| Lumen Health | Book care online, e-sign consent, clinical notes kept provider-only via field-level access | lumen.supero.live |
| BrightSmile | Dental practice โ online booking, treatment plans, provider-only clinical notes | brightsmile.supero.live |
| TrialCore | Clinical trials โ public study registry, enrollment dashboards, adverse-event workflows | trialcore.supero.live |
๐ฐ Finance & Insurance
| App | What it is | Live |
|---|---|---|
| Ledgerline | Billing โ live MRR dashboards, automated dunning, multi-step expense approvals | ledgerline.supero.live |
| Sentinel | Insurance โ two insurers on one deployment, public quote portal, claims approval sagas, insurer-only fraud scores | sentinel.supero.live |
๐๏ธ Commerce & Sales
| App | What it is | Live |
|---|---|---|
| Atelier | B2B wholesale marketplace โ discovery storefront, multi-brand cart, net-terms checkout | atelier.supero.live |
| Summit CRM | Pipeline kanban, weighted forecasting, lead conversion, win-rate analytics | summit.supero.live |
| Amplify | Social marketing โ connect channels, compose with AI, schedule, track engagement | amplify.supero.live |
๐ Multi-tenant (one deployment, many organisations)
Every app above runs a single organisation. These four run several at once, and the isolation is enforced by the server: a user signed into one tenant cannot read another tenant's rows even by calling the API directly with their own valid token. Two of them also demonstrate field-level access control on top of that, so a row you can read still arrives with fields removed.
| App | What it is | Tenants | Live |
|---|---|---|---|
| Medora | Hospital network โ appointments, encounters, prescriptions, labs, invoicing. A patient reads their own encounter with assessment and plan stripped server-side |
3 hospitals | medora.supero.live |
| Helix | Multi-site clinical trials โ participants, visits, adverse events. The treatment arm is withheld from blinded investigators by the access policy, not by the UI |
3 sites | helix.supero.live |
| Lattice | Property management โ units, leases, rent, maintenance, applications. Applicants cannot read the leasing team's screening notes | 3 managers | lattice.supero.live |
| Pulse | Multi-location gym โ classes, bookings, memberships, check-ins | 3 locations | pulse.supero.live |
Sign in on any of them and the login page lists every demo account with its tenant, role and password โ click a row to fill the form.
๐ข Operations & Services
| App | What it is | Live |
|---|---|---|
| Concierge AI | Support โ AI help center grounded in your KB, agent console with suggested replies | concierge.supero.live |
| FieldOps | Dispatch board, mobile work orders, photo capture, on-site e-signature | fieldops.supero.live |
| Relay | Per-diem healthcare staffing โ facilities post shifts, clinicians claim them, with credential verification and timesheets | relay.supero.live |
| Tavola | Restaurant โ online ordering, reservations, loyalty, live kitchen board | tavola.supero.live |
| PulseFit | Gym chain โ class booking, memberships, attendance, multi-location | pulsefit.supero.live |
๐ก Property & Media
| App | What it is | Live |
|---|---|---|
| Haven | Listings search, tour booking, offers with broker approval | haven.supero.live |
| Backlot | Film production โ slate, cast & crew, call sheets, AI script breakdown | backlot.supero.live |
Build it with your AI
Every app ships a CLAUDE.md (and .cursorrules / .windsurfrules) so your assistant
understands the codebase before it touches a line.
You can also connect your editor directly to the platform over MCP โ 64 tools that let an assistant design schemas, run CRUD, connect a database, and take an app from a sentence to a live URL:
claude mcp add --transport http supero https://api.supero.dev/mcp/v1/messages \
--header "X-API-Key: ak_your_key_here"
Then just ask:
"Add a waitlist to the clinic app โ patients join, staff promote them when a slot opens."
The interesting part is what the assistant is allowed to do. An MCP call carries your credential to the same API a browser would use โ no service account, no elevated path. So the agent inherits your permissions rather than getting its own, and the row scoping and field hiding above apply to it identically. An agent you point at a customer's data is bounded by the same policy the customer is.
The server is live and you can inspect it without a key:
curl https://api.supero.dev/mcp/v1/info
docs/mcp.md covers getting a key and the tool families. The complete reference, every parameter, is at docs.supero.dev/developers/mcp/tool-reference.
What you actually get
Two things, and it's worth being precise about which is which.
From schemas.py (95โ270 lines, median 120), automatically โ no code:
| You write | The platform generates |
|---|---|
| a data model | REST APIs, a typed SDK, validation, migrations |
access policies in setup.py |
role-based access enforced server-side |
config.py |
an admin panel, auth, and the services you switch on |
ui/app.js is the one part that's real code you own. It's the app's custom
storefront โ 400 to 1,100 lines of React depending on the app, median around 800 โ generated
as a working starting point, then yours to edit however you like. So you get the tedious 80% (APIs, auth, admin, RBAC)
for free, and a real front-end you control โ not a locked template.
Access control is declared in setup.py, and the server applies it โ not the UI. You
write row scoping (filter_field="owner_username") and field hiding
(hidden_fields=["clinical_notes", "diagnosis"]). A patient calling the API directly with
their own valid token โ curl, browser closed, front-end out of the picture:
GET /api/v1/crud/<your-domain>/appointment
gets their appointments back with clinical_notes absent from the response body.
Nothing in ui/app.js is doing that โ delete the entire front-end and the field still does
not come back. That's why lumen keeps clinical notes provider-only and sentinel hides
fraud scores from claimants without either app writing a line of access-control logic.
Two things worth being precise about, because they decide whether you can rely on this:
- It covers the entities you declare in your own schemas. Platform-managed types โ
accounts, API keys, domains, projects, tenants โ are governed by role permissions instead.
That is a different mechanism, and
hidden_fieldsdoes not extend to them. - It is a server-side response filter, not a database-level projection. The field is removed before the response is written, not withheld from the query.
Open their setup.py โ the policy block is short, and it's the thing worth checking first.
Then check it against your own deployment rather than taking this page's word for it.
Zero build. React and Tailwind load from CDN. No node_modules, no bundler, no
npm install. Edit ui/app.js, refresh the page.
Each app carries five suites. Three are static validators that check the bundle's own
consistency and need nothing running. Two โ crud_tests.py and e2e_tests.py โ make real
HTTP calls against your domain, and are the ones that assert the access-control claims.
The live pair skip with a stated reason when no app is serving, so a fresh clone stays
clean:
cd apps/healthcare/lumen && ./tests/run_tests.sh
How this works, honestly
This is open-core, and we'd rather say so plainly than have you find out.
- The app source in this repo is MIT โ genuinely yours. Fork it, sell it, rip the UI out.
- The
superoSDK is MIT and open on PyPI. - The platform these apps call (
api.supero.dev) is a hosted service. Schema resolution, the multi-tenant runtime, RBAC enforcement, and orchestration run there. That part is not open source.
So an app here is a thin, portable client that calls the platform for schema resolution, RBAC, and orchestration. That's the trade: you skip building and operating a backend, and in return the backend is a managed service.
Your data and your exit. The domain, schema, and data are yours. Every record is
reachable through the same REST API the app uses, so export is a loop over
GET /api/v1/crud/{domain}/{type}
with your API key โ nothing is trapped in a proprietary store you can't read. And for teams
that need to run inside their own network, self-managed / on-prem deployment is available
under an enterprise agreement (hello@supero.dev) โ so "what if the vendor goes away" has a
real answer. See deploy.md.
Regulated data โ read this first. These are reference applications, not certified
compliant systems. lumen and trialcore show the shape of healthcare access control;
they are not HIPAA-certified and ship with no BAA. Before putting real PHI, PII, or
regulated financial data into anything here, talk to us about compliance posture, data
residency, and a BAA โ don't assume the demo covers it. See SECURITY.md.
Pricing. There's a free tier โ enough to run everything in this repo โ then usage-based beyond it. We don't publish the numbers yet. They're visible in the dashboard once you have a domain, which costs nothing to create, and you can ask us before you get that far. We'd rather say that plainly than link you to a page that isn't there.
Anatomy of an app
apps/healthcare/lumen/
โโโ README.md โ how to run this specific app
โโโ CLAUDE.md โ context for AI assistants (also .cursorrules/.windsurfrules)
โโโ CUSTOMIZATION.md โ branding, layout, services, admin panel
โ
โโโ schemas.py โ your data model ~120 lines
โโโ setup.py โ seed data, roles, policies
โโโ config.py โ app name, services, tenants
โโโ .env.example โ copy to .env, set your domain
โ
โโโ run.sh โ bootstrap + serve
โโโ Dockerfile โ container image
โโโ docker-compose.yml โ docker compose up
โ
โโโ tests/ โ crud / integration / e2e
โโโ ui/
โโโ app.js โ your screens (the only UI file you edit)
Everything else in ui/ โ the component library, schema bindings, dev server โ is restored
from the supero wheel on every run.sh. That's why it isn't committed here: it's a build
artifact, not source.
Docs
| Guide | |
|---|---|
| Quickstart | Clone an app onto your own domain |
| Build with Claude (MCP) | Connect Claude Code / Cursor / Copilot |
| How it works | The mental model: schema โ API โ RBAC, multi-tenancy |
| API reference | Auth, CRUD, services, connectors, files, MCP |
| Schemas | The data model, inheritance, field-level access |
| Services & workflows | AI, email, payments, approval chains |
| Admin panel | What you manage without writing code |
| Deploy | Where to run it: managed URL vs your cloud vs enterprise |
| Deploy to your cloud | Cloud Run, ECS/Fargate, Fly, Render โ step by step |
FAQ
Do I need a Supero account?
No. ./run.sh registers the domain you name in .env. No signup wall.
Is my data locked in? No. It's your schema and your domain. Apps run on your machine, your cloud, or a managed URL.
What's the catch on the free tier? Usage limits. The current numbers aren't published โ they're in the dashboard once you have a domain (free to create, no card), or ask us.
Can I use these commercially? Yes โ the app source here is MIT. Build on it, sell it, fork it.
Where's the platform source?
The supero SDK is MIT and open. The hosted platform
(generation, multi-tenant runtime, orchestration) is a managed service.
Getting help
Ask in Discussions. Use Q&A when something does not work the way you expected, and Show and tell for an app you built. Answers stay public, so the next person with the same question finds them. Anything about your own account goes to support@supero.dev, and security reports go to security@supero.dev, never to a public thread.
Contributing
Issues and PRs welcome โ app improvements, new verticals, doc fixes. See CONTRIBUTING.md.
Built something with Supero? Open a PR and add it to the gallery.
Want to build a new app from scratch? supero-mcp has a step-by-step guide to building one from your AI assistant over MCP, 26 project briefs to pick from, and community apps you can improve. The free plan covers three projects.
Contributors
Thank you to the people who have improved these apps:
- @bhavesh1309 added the first app screenshots, for Lumen Health (#28) and FieldOps (#32).
- @kkinsen0314-alt fixed TrialCore's enrolment email, which had no recipient, and added a test for it (#29).
- @Cid-oe made Tavola's order confirmation email-only by removing its SMS step, which closed #20 (#33).
Want your name here? The open issues say what needs doing, and several are marked good first issue.
supero.dev ยท Live apps ยท Discussions ยท Issues
App source in this repo is MIT licensed.
Supero Apps MCP questions
How can I use an AI assistant to build these apps?
You can connect your editor directly to the platform over MCP using 64 tools that allow an assistant to design schemas, run CRUD, and take an app from a sentence to a live URL.
Does the AI assistant have elevated permissions?
No, the MCP call carries your own credentials, meaning the agent inherits your specific permissions and is bounded by the same row scoping and field hiding policies as you.