Supero
by supero.dev in Developer tools
Build multi-tenant apps over MCP. Schemas, CRUD, deploys — access control enforced server-side.
https://api.supero.dev/mcp/v1/messages
Last 30 days
- Uptime
- 100%
- Response time
- 255 ms typical, 255 ms slowest 5%
- Last check
- 2 h ago
- Next check
- in 4 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"supero": {
"type": "http",
"url": "https://api.supero.dev/mcp/v1/messages"
}
}
}64 tools
- crud_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, connector_plugin. Domain types vary per d
- crud_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 to the domain. Schemas are validated before saving. Returns list of successfully saved schemas with their UUIDs. IMPORTANT: Pass FLAT schema objects directly — do NOT wrap in schema_content. The tool handles schema_type detection and wrapping automatically.
- schema_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.
- 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' means) | 'landing' (compact landing-page
- build_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 byte sizes; pick the one closest to your a
- build_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, seed data). Deterministic, no LLM: it detect
- build_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, attachment, feedback, notification, prod
- 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 model (entities/central_entity/relationship
- build_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).
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 2 h ago | Passed | 200 | 255 ms |