Supero
Build and deploy multi-tenant apps from ChatGPT, Claude or your editor. Sign in with OAuth or a key
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.Similar tools
Listed for the same task: automate CI/CD pipelinesReviews
No review yet. Used Supero? Be the first to help others choose.What it does
Supero is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 22h ago (live check)Hosted endpoints
https://api.supero.dev/mcp/v1/messagesstreamable-httphttps://mcp.supero.dev/mcpstreamable-http
Required: X-API-Key (get it from the publisher)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"supero": {
"url": "https://api.supero.dev/mcp/v1/messages",
"headers": {
"X-API-Key": "<your X-API-Key>"
}
}
}
}Replace the values in <angle brackets>.
Live check
Electra Index connected to the hosted endpoint 22h agoONLINE Supero answered an MCP connection on 16 Nov 2026 and introduced itself as supero 2.0.2 (MCP protocol 2025-03-26).
68 tools offered to AI assistants
build_get_skills· Fetch a Supero build reference. doc='skills' (default, the spec you MUST follow) | 'components' (the real pre-built SDK component/global catalog — read so you don't reinvent UI) | 'rubric' (the rich-app quality checklist — what 'stunning' mbuild_get_examples· Fetch a COMPLETE, production-quality reference app (schemas.py + config.py + setup.py + ui/app.js) to copy patterns from — the single biggest lever for app quality. archetype='index' (default) lists the available archetypes with per-file bybuild_plan· PLAN FIRST — turn a one-line app idea into an explicit BUILD CHECKLIST before you author anything, so a thin prompt doesn't silently skip what expert builders add (this is exactly why first-draft apps miss detail pages, tenant pickers, seedbuild_get_service_contract· Fetch the AUTHORITATIVE contract for a transactional/stateful platform service (cart, order, payment, booking, appointment, membership, approval, document_signature, recurring_plan, inventory, task, ticket, loyalty_points, rental, comment,build_whoami· Resolve your API key's scope: role (domain_admin/project_admin), domain, whether you can create projects, and your plan. Call this to decide the flow.build_list_projects· List projects you can build into (uuid, name, schema_namespace, live_url).build_get_project· Get one project's details: schema_namespace (use this EXACT value as the `namespace` literal on every schema dict), last published version, AND the captured `project_intent` — the brief (project_description/summary), the discovered data modbuild_create_project· Create a NEW project (domain-admin keys only; plan-gated). Mints the project's schema_namespace + an API key (returned ONCE). Use for a fresh app.build_update_project· Update a project's metadata (display_name, description, show_public, live_url).build_set_project_mode· Set a project's build mode. 'dev' (default) allows COMPLETE REPLACE (wipe data, keep credentials); 'live' protects it. Switch to dev before replacing, to live when it's in production.build_replace_project· DESTRUCTIVE (DOMAIN-admin keys only): completely replace a DEV-mode project's app — wipes its data (retains credentials, API keys, namespace, tenant). Refused if mode='live'. Requires confirm_project_name to match. If you pass files, they abuild_validate· Validate a locally-authored bundle against the live platform BEFORE publishing. AST-only (your code is never executed). Checks manifest, syntax, import-safety, config exports, schema validity, and namespace==project schema_namespace.
Show 56 more
build_publish· Package + upload your authored bundle and record a version under the project. Returns version_uuid + file_id + download_url. Runs build_validate first; force=true overrides soft errors only. Provide files as {relative_path: content}.build_stage_bundle· PUB-1a: get the out-of-band UPLOAD endpoint for a LARGE app bundle that won't fit inline (the model's max OUTPUT tokens cap `files`/`files_b64gz`, so big apps otherwise have to be truncated/minified). Upload a gzip(json {path:content}) blobbuild_get_bundle· Fetch the CURRENT (or a given) PUBLISHED bundle: the file list + a signed download_url, or ONE file's content inline via file=. For ANY change request on an existing app, START from this bundle and modify it — re-authoring from scratch silebuild_deploy· Deploy a published version. target='cloud_ephemeral' (managed Cloud Run, ~30m throwaway preview; requires platform enablement; the default when cloud deploy is enabled) or 'local' (hand the user the bundle to run with the project's own key)build_deploy_status· Poll a cloud deploy started by build_deploy or build_go_live. Pass the poll_url it returned. Reports elapsed_s since launch. 'launching' for 5-6.5 minutes is normal (Cloud Run IAM propagation): keep polling every ~30s and probe the url oncebuild_logs· Fetch recent Cloud Run logs for a project's deployed app — THE tool for diagnosing a failed/stalled cloud deploy or a crashing app (startup-probe timeouts, tracebacks, 'container failed to start on PORT'). Read-only; rate-limited per domainbuild_go_live· PERMANENT deploy: promote a published version to a PERMANENT public URL at <service>.supero.live (managed Cloud Run) — unlike build_deploy(target='cloud_ephemeral'), which is a ~30-min throwaway. If version_uuid/file_id are omitted, the latbuild_teardown· Tear down a project's live deployment — BOTH the permanent (build_go_live) app and the ephemeral preview — DELETEing the managed Cloud Run services and freeing their URLs. Idempotent: a project with nothing deployed returns stopped=true. ONbuild_go_production· Go to production: take a live app's sample data and demo logins out before real customers use it. Same six steps as the app's Settings -> Go to production: 1. Stop sample data coming back ('seed_off'; the app redeploys), 2. Preview ('plan',build_list_capabilities· List the platform's available services/integrations from the LIVE catalog (email, sms, slack, ai, stripe_checkout, google_oauth, push_notification, …) — so the intake's 'which connections/integrations?' question is accurate and you never gubuild_recommend_integrations· RECOMMEND which concrete provider integrations this app needs, and WHY — the deterministic Step-2 intelligence the web wizard uses, now over MCP. Pass the app `description` + the platform `service_ids` it will use (e.g. ['cart','order']); rbuild_configure_services· Configure a service's keys for the project so an integration works at deploy (e.g. wire SendGrid for email, a Stripe TEST key for checkout). TEST/SANDBOX keys ONLY. Keys with a clear live marker (Stripe sk_live_… / Razorpay rzp_live_…) arebuild_import_services· IMPORT platform services into a project (e.g. 'workflows', 'email', 'stripe_checkout', 'cart', 'order', 'payment') so the app can call them and its event-bound workflows can run. Uses the platform's service import with YOUR connection's crebuild_doctor· PREFLIGHT a bundle BEFORE publish/deploy — catches the silent deploy-killers build_validate does NOT: missing #supero-preloader removal (app stuck on a spinner forever), heavy startup seed (Cloud Run port-bind timeout → 'container failed tobuild_audit· SECURITY + CORRECTNESS AUDIT of a bundle BEFORE go-live (static; your code is never executed). Finds what build_validate/build_doctor do not: MONEY-01 client-chosen checkout amounts, AUTHZ-01 end-users able to write server-owned fields (paibuild_verify· ACCEPTANCE TEST of your app's running PREVIEW (after build_deploy, before build_go_live). Where build_audit reads the code, build_verify USES the deployed preview like a buyer would, with throwaway test accounts (verify-<rand>@example.com,build_smoke_test· VERIFY a DEPLOYED app actually works (not just 'running'). HTTP-checks the live URL: root loads with a title, app.js is your bundle (not a stub) and dismisses the boot splash, config.js namespace matches the project; optionally logs in andbuild_e2e_test· Run the FULL behavioural test suite against a PUBLISHED bundle in the project's OWN already-deployed app (no throwaway project is created) — auth/RBAC/multi-tenant, CRUD round-trips, workflows + event emission, services, aggregates, real-brbuild_e2e_test_status· Poll an e2e run started by build_e2e_test. While running, returns status only. When complete, returns a compact report: verdict (honest — never 'healthy' if a core suite couldn't run), per-suite pass/fail/warn/skip, findings with layer + fibuild_list_data_sources· List the external DATA SOURCE types an app can connect to — its own Postgres/MySQL/MSSQL/Oracle/MongoDB, any REST API, or a Snowflake/BigQuery/Redshift/Databricks/ClickHouse/Fabric warehouse — plus the curated public-API catalog. Read thisbuild_connect_data_source· Create a data connector to an EXTERNAL source the app owner controls (their own database, a REST API, or a warehouse). Returns a connector_id. Does NOT bind schemas yet. Flow: build_connect_data_source → build_discover_source (lists the tabbuild_discover_source· Discover a connector's schema: trigger discovery, wait, and return the source streams (names, columns, primary keys), AI-inferred Supero schemas, field mappings, and a suggested namespace. Run AFTER build_connect_data_source and BEFORE builbuild_bind_data_source· Bind source streams to the app's schemas. mode='live_read' (default: read-only BYODB / warehouse), 'live_readwrite' (BYODB read+write, DOMAIN-ADMIN only), or 'sync' (copy into SuperoDB). Modes by source: postgresql, supabase, mysql take allbuild_run_data_source· Trigger a SYNC RUN on a data connector and return the run id. MCP-created connectors are trigger:manual, so a mode='sync' binding copies NO rows until a run executes — call this after build_bind_data_source (and again whenever the source dabuild_list_bound_schemas· Classify this project's schemas: which are connector-backed vs app-authored, and each one's access mode (sync | live-ro | live-rw | warehouse). Use it so you DON'T render create/edit UI for read-only live sources (live-ro/warehouse) or regecrud_search· Search/list objects of any type in the current domain. Use schema_list first to discover available object types. System types: project, tenant, user_account, api_key, connector, audit_log, schema_registry, client_sdk, connector_execution, ccrud_get· Get a specific object by UUID from the current domain.crud_create· Create a new object in the current domain. Use schema_list to see available types and their fields.crud_update· Update an existing object in the current domain.crud_delete· Delete an object from the current domain.schema_list· List all existing schemas in the current domain.schema_get· Get full details of a specific schema by UUID. Returns the complete schema definition including all attributes and metadata.schema_validate· Validate schemas before saving. Checks for conflicts with existing schemas, circular dependencies, reserved names, and parent_type correctness. Always validate before saving!schema_save· Save/upload schemas into a project. Schemas are validated before saving and linked to the project. Returns the saved schemas with their UUIDs; skipped schemas carry the platform's reason. IMPORTANT: Pass FLAT schema objects directly — do NOschema_delete· Delete a schema from the domain. Use with caution.schema_list_project· List schemas linked to the current project.schema_update· Update an existing schema definition.project_link_schemas· Link schemas to a project. Accepts schema UUIDs or names.sdk_generate· Generate client SDKs for the domain's schemas.sdk_status· Check SDK generation request status.sdk_list· List available SDKs for the current domain.sdk_download· Get download URL for an SDK.rbac_get_my_access· Get current user's role, permissions, and scope.rbac_check_permission· Check if the current user has a specific permission.apikey_get_scope· Get the scope and permissions of the current API key.connector_run· Trigger a manual connector sync execution.connector_cancel· Cancel a running connector execution.connector_status· Get connector status and recent executions.connector_enable· Enable a connector for scheduling.connector_disable· Disable a connector.connector_discover· Trigger schema/metadata discovery for a connector.connector_discover_status· Get discovery execution status.connector_discover_results· Get discovery results.connector_test_config· Test a connector configuration.connector_test· Test an existing connector's connectivity.connector_plugins· List available connector plugins.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://api.supero.dev/mcp/v1/messages, https://mcp.supero.dev/mcp | DECLARED | SRC-001 Official MCP Registry | 15h ago |
| Website | https://docs.supero.dev/developers/mcp/connect-chatgpt-claude/ | DECLARED | SRC-001 Official MCP Registry | 15h ago |
| Version | 2.0.2 | DECLARED | SRC-001 Official MCP Registry | 15h ago |
| Repository | https://github.com/supero-platform/supero-mcp | DECLARED | SRC-001 Official MCP Registry | 15h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 15h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 15h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 15h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 15h ago |
Change history
- VERSION07 Nov 20262.0.1 → 2.0.2
- VERSION22 Oct 20262.0.0 → 2.0.1
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Supero still online?
Free alerts · no account▲ 0Do you run Supero? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Supero
How do I connect Supero?
Use the hosted endpoint https://api.supero.dev/mcp/v1/messages in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does Supero need an API key or token?
Yes. The registry entry lists a required value: X-API-Key. Get it from the publisher.
What tools does Supero offer?
When Electra Index connected on 16 Nov 2026, it listed 68 tools: build_get_skills, build_get_examples, build_plan, build_get_service_contract, build_whoami, build_list_projects, build_get_project, build_create_project and more. The full list is in "Live check" above.
Is Supero online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 22h ago.
What can I use Supero for?
Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.