Agents Index

Supero

Online

Multi-tenant backend your coding agent configures over MCP: auth, RBAC, data, workflows, deploy.

Visit publisherConnectJSON

What it can do: 70 tools

  • build_get_skills read-onlyReturns Supero's build guides describing schemas, services and the recommended build sequence. topic='core' (~20KB) returns the core build rules plus the topic index; other topics (build_plan names the relevant ones, e.g
  • build_get_examples read-onlyReturns a complete reference app (schemas.py, config.py, setup.py, ui/app.js) for an archetype. archetype='index' (default) lists the archetypes with file sizes: commerce-storefront, commerce-marketplace, service-booking
  • build_plan read-onlyTurns an app description into a build checklist, without an LLM. Input: description, plus optional entities, is_multi_tenant and public_facing. Returns the detected vertical with its usual pages and terms, the entities t
  • build_get_service_contract read-onlyReturns the contract of a transactional platform service (cart, order, payment, booking, appointment, membership, approval, document_signature, recurring_plan, inventory, task, ticket, loyalty_points, rental, comment, at
  • build_whoami read-onlyReturns the scope of the current credential: role (domain_admin / project_admin), domain, whether it can create projects, the project it is limited to (if any) and the plan. No inputs. Useful at the start of a session to
  • build_list_projects read-onlyLists the projects this credential can build into: uuid, name, schema_namespace and live_url. Input: optional limit. Useful for choosing a project on a domain-wide credential.
  • build_get_project read-onlyReturns one project's details for project_uuid: schema_namespace (the exact value every schema uses as its namespace), the last published version, and the captured project_intent: the brief, the discovered data model (en
  • build_create_projectCreates a new project (domain-admin credentials only; plan-gated). Inputs: name, plus optional display_name, schema_namespace, description, requirements and is_multi_tenant. Returns the project uuid, its schema_namespace
  • build_update_projectUpdates a project's metadata (display_name, description, show_public, live_url) from patch. Inputs: project_uuid, patch. Returns the updated project.
  • build_set_project_modeSets a project's build mode. 'dev' (default) allows a complete replace, which wipes app data and keeps credentials; 'live' makes a replace refuse, protecting production data. Inputs: project_uuid, mode. Returns the new m
  • build_replace_projectDestructive: completely replaces a dev-mode project's app and wipes its data (credentials, API keys, namespace and tenant are kept). Domain-admin credentials only; refused when mode='live'; confirm_project_name has to eq
  • build_validate read-onlyValidates an authored bundle against the live platform without running it (static AST checks): manifest, syntax, import safety, config exports, schema validity and namespace equal to the project's schema_namespace. Input
  • build_publishPackages and uploads an authored bundle and records a new version under the project. Runs build_validate first; force=true overrides soft errors only. Inputs: project_uuid and the files as {relative_path: content} (files
  • build_stage_bundle read-onlyReturns an out-of-band upload endpoint for a bundle too large to send inline (inline files are limited by the client model's output size). A gzip(json {path: content}) blob uploaded there with the connection's own key yi
  • build_get_bundle read-onlyReturns the current (or a given version's) published bundle: the file list and a signed download_url, or one file's content with file=. Inputs: project_uuid, optional version_uuid, file, offset, max_bytes. A file= answer
  • build_deployDeploys a published version. Inputs: project_uuid, optional version_uuid, target, app_type. target='cloud_ephemeral' (managed Cloud Run preview of about 30 minutes; requires platform enablement; the default when cloud de
  • build_deploy_status read-onlyReturns the state of a cloud deploy started by build_deploy or build_go_live. Input: the poll_url it returned (optional permanent). Reports elapsed_s since launch. 'launching' for 5-6.5 minutes is normal while Cloud Run
  • build_logs read-onlyReturns recent Cloud Run logs of a project's deployed app: startup-probe timeouts, tracebacks, 'container failed to start on PORT'. Inputs: project_uuid, optional lines, since. Read-only; rate-limited per domain. For an
  • build_go_livePromotes a published version to a permanent public URL at <service>.supero.live (managed Cloud Run), unlike the ~30-minute preview of build_deploy. Inputs: project_uuid, optional version_uuid / file_id (default: the late
  • build_teardownDestructive: stops a project's deployments, both the permanent build_go_live app and the preview, deleting the managed Cloud Run services and freeing their URLs. Input: project_uuid. Idempotent: nothing deployed returns
  • build_go_productionTakes a live app's sample data and demo logins out before real customers use it, with the same six steps as the app's Settings -> Go to production: 1. stop sample data coming back ('seed_off'; the app redeploys); 2. prev
  • build_list_capabilities read-onlyLists the services and integrations in the live platform catalog (email, sms, slack, ai, stripe_checkout, google_oauth, push_notification, ...). Returns each one's exact service_id as config.py uses it (for example 'stri
  • build_recommend_integrations read-onlyRecommends provider integrations for an app, with reasons. Inputs: the app description and the platform service_ids it uses (for example ['cart','order']), plus optional region, project_uuid and google_signin. Returns gr
  • build_configure_servicesStores a service's keys for the project so an integration works at deploy (for example SendGrid for email, a Stripe test key for checkout). Inputs: project_uuid, service_id, config. Accepts test or sandbox keys only: key
  • build_import_servicesImports platform services into a project (for example 'workflows', 'email', 'stripe_checkout', 'cart', 'order', 'payment') so the app can call them and its event-bound workflows can run, using this connection's credentia
  • build_doctor read-onlyPre-publish checks for problems build_validate does not catch: the #supero-preloader not removed (app stuck on a spinner), heavy startup seed (Cloud Run port-bind timeout), reserved field names such as status/state (drop
  • build_audit read-onlyStatic security and correctness audit of a bundle (the code is not executed). Finds MONEY-01 client-chosen checkout amounts, AUTHZ-01 end users able to write server-owned fields (paid/issued/status/amount/payment refs) o
  • build_verifyAcceptance test of the project's running preview (after build_deploy, before build_go_live), using it as a buyer would with throwaway test accounts (verify-<rand>@example.com, deleted afterwards). Checks: health (serves
  • build_smoke_testHTTP-checks a deployed app: the root loads with a title, app.js is the published bundle and dismisses the boot splash, and config.js has the project's namespace; optionally signs in and reads one entity. Inputs: project_
  • build_e2e_testStarts the full behavioural test suite against a published bundle in the project's own deployed app (no throwaway project): auth, RBAC and multi-tenancy, CRUD round-trips, workflows and events, services, aggregates and a
  • build_e2e_test_status read-onlyReturns the state of a build_e2e_test run (input: run_id). While running: status only. When complete: the verdict (not 'healthy' if a core suite could not run), per-suite pass/fail/warn/skip, findings with the responsibl
  • build_list_data_sources read-onlyLists the external data source types an app can connect to: its own Postgres, MySQL, MSSQL, Oracle or MongoDB, any REST API, or a Snowflake, BigQuery, Redshift, Databricks, ClickHouse or Fabric warehouse, plus the curate
  • build_connect_data_sourceCreates a data connector to an external source the app owner controls (a database, a REST API or a warehouse). Inputs: name, kind, and the connection fields for that kind (db_type, host, port, database, username, passwor
  • build_discover_sourceRuns discovery on a connector and returns its source streams (names, columns, primary keys), AI-inferred Supero schemas, field mappings and a suggested namespace. Inputs: connector_id, optional execution_id, timeout. Run
  • build_bind_data_sourceBinds source streams to the app's schemas. Inputs: connector_id, bindings. mode='live_read' (default: read-only own database or warehouse), 'live_readwrite' (own database read+write, domain-admin only) or 'sync' (copy in
  • build_run_data_sourceStarts a sync run on a data connector and returns the run id. Input: connector_id. Connectors created over MCP are manual-trigger, so a mode='sync' binding copies no rows until a run executes (after build_bind_data_sourc
  • build_list_bound_schemas read-onlyClassifies a project's schemas as connector-backed or app-authored, with each one's access mode (sync | live-ro | live-rw | warehouse). Input: optional project_uuid. Useful when authoring UI: read-only live sources (live
  • build_report read-onlyRead-only hand-off for a deployed project, compiled from what the server knows: what was built (from the published bundle), the app URL and expiry, console links, the demo-account table, the latest check results for this
  • build_production_status read-onlyRead-only view of a project's Go to production state; it changes nothing. Inputs: project_uuid and what: 'status' (the default: the sample data setting, the current job, blockers and the next step), 'plan' with plan_id (
  • crud_search read-onlySearches or lists objects of one type in the current domain. Inputs: object_type, optional filters / filter, sort, limit, offset, tenant. Returns matching rows. System types: project, tenant, user_account, api_key, conne

…and 30 more.

Connect it

Claude Code
claude mcp add --transport http supero https://mcp.supero.dev/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.supero.dev/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "supero": {
      "url": "https://mcp.supero.dev/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "supero": {
      "type": "http",
      "url": "https://mcp.supero.dev/mcp"
    }
  }
}

Questions

What does Supero do?

Multi-tenant backend your coding agent configures over MCP: auth, RBAC, data, workflows, deploy. It exposes 70 tools to AI assistants.

What tools does Supero provide?

70 tools, including build_get_skills, build_get_examples, build_plan, build_get_service_contract, build_whoami, build_list_projects, build_get_project, build_create_project, build_update_project, build_set_project_mode, build_replace_project, build_validate….

How do I connect Supero to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.supero.dev/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Supero require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Supero online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Supero?

@supero-platform on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Automation & Integrations