MCP SERVER · 60+ TOOLS · POLICY AT THE PLATFORM

The governed backend for software your agents build.

Tenants, roles, field-level access and workflow undo live in the platform, not rewritten by the agent in every app. Use Supero's managed database or connect your own Postgres, Snowflake or BigQuery.

Start building free Explore demo apps →

claude mcp add --scope user --transport http supero \
  https://api.supero.dev/mcp/v1/messages \
  --header "X-API-Key: $SUPERO_API_KEY"

~/.cursor/mcp.json

{
  "mcpServers": {
    "supero": {
      "url": "https://api.supero.dev/mcp/v1/messages",
      "headers": { "X-API-Key": "ak_..." }
    }
  }
}

.vscode/mcp.json

{
  "inputs": [{
    "type": "promptString", "id": "supero-key",
    "description": "Supero API key", "password": true
  }],
  "servers": {
    "supero": {
      "type": "http",
      "url": "https://api.supero.dev/mcp/v1/messages",
      "headers": { "X-API-Key": "${input:supero-key}" }
    }
  }
}

First: create a free account, then a project key under Build via MCP. It shows the setup for your editor with your key filled in.

Then ask: “Build a support desk where agents see only their team's tickets.” The preview starts 5 to 6.5 minutes after your agent deploys.

request inspector example · replay

GET/api/v1/crud/ledger/invoice/8f2a…200 OK

authorization: Bearer •••• · tenant=acme · role=viewer

{
  "uuid": "8f2a…",
  "customer": "Northwind Clinic",
  "status": "open"
}

// amount_cents removed from the response · role=viewer

GET/api/v1/crud/ledger/invoice/77c0…403

caller tenant=acme → record tenant=globex

message: "Access denied: this invoice belongs to another tenant"

Example data. Some read checks still run in observe mode. See enforcement status

Your agent writes the app. Supero runs the backend.

01 · YOUR AGENT

Writes UI and data models

Claude Code · Cursor · VS Code
Data model files it writes: schemas.py, config.py, setup.py

02 · MCP SERVER

60+ tools

Generates a REST API per model
Checks run before deploy
REST · Python & JS SDKs

03 · SUPERO RUNTIME

policy on every request

23 tested domain services

Sign-in & accounts
Tenant isolation
Roles & field access
Workflows + undo
Payments
Integrations (40+)

04 · YOUR DATA

12 databases & warehouses

Supero managed DB
Your Postgres · Snowflake · BigQuery
Per table, keep a copy or query live

live read · live write · sync, by source

OPEN SOURCE · FIELDOPS

A trades business in 203 lines of schema.

10 of its 12 models extend a tested base service. The agent declares the data; the platform supplies approvals, signatures, payments and inventory.

Read schemas.py on GitHub Open FieldOps →

FieldOps schema models and the Supero base services they use
schema model	base service
Quote	base_approval
Appointment	base_appointment
WorkOrderSignature	base_signature
Payment	base_payment
PartHold	base_reservation
Contract	base_recurring_plan

schemas.py @ f64e0f2

22Quote = {
23    "schema_type": "object", "name": "Quote", "namespace": "fieldops",
24    "parent_type": "tenant", "extends": "approval:base_approval",
25    "description": "A priced estimate a customer approves before a job is scheduled.",
26    "attributes": [
27        {"name": "owner_username", "type": "string"},     # the customer
28        {"name": "customer_name", "type": "string"},
29        {"name": "service_name", "type": "string"},
30        {"name": "service_uuid", "type": "string"},
31        {"name": "address", "type": "string"},
32        {"name": "line_items", "type": "json"},
33        {"name": "amount", "type": "float"},
34        {"name": "notes", "type": "text"},
35        # base_approval requires: status (initial 'draft' → 'pending' on submit).
36    ],
37}

106Payment = {
107    "schema_type": "object", "name": "Payment", "namespace": "fieldops",
108    "parent_type": "tenant", "extends": "payment:base_payment",
109    "description": "A payment for a completed job, authorized then captured on sign-off.",
110    "attributes": [
111        {"name": "owner_username", "type": "string"},
112        {"name": "appointment_uuid", "type": "string"},
113        {"name": "work_order_uuid", "type": "string"},
114        {"name": "method", "type": "string"},
115        {"name": "external_id", "type": "string"},
116        {"name": "invoice_id", "type": "string"},
117        {"name": "workflow_status", "type": "string"},
118        # base_payment requires: status (initial 'pending'), amount, currency.
119    ],
120}

What your agent no longer writes.

A database with auth gets you started. The SaaS plumbing on top is where agent-written apps drift and break.

Who builds each backend capability
capability	database + auth BaaS	app builder built-in DB	Supero
Tenant isolation	your RLS policies	left to your app	platform enforced*
Roles & permissions	your RLS policies	rules you set up per app	platform enforced*
Field-level hiding in API responses	column grants / views you maintain	rules you set up per app	platform enforced*
Workflow undo on failure	left to your app	left to your app	platform, for steps that declare an undo

* Writes are checked by role on the server and hidden fields are removed from responses. Some read checks still run in observe mode.

The platform today

integrations: 40+
databases & warehouses: 12
MCP tools: 60+
domain services: 23
end-to-end test functions: 1,936
deploy targets: 4

Your cloud, your data.

Supero cloud

Preview deploys on every plan; production from Basic.

UI on your AWS, GCP or Docker

Backend stays on Supero; the front end runs in your account.

Full platform, self-hosted pilot

The platform on your servers, on request. The AI service isn't included yet.

Your data, your schema

Connect your own Postgres, Snowflake or BigQuery. Per table, keep a copy in Supero or query your source live; which modes you get depends on the source. schemas.py stays in your repo. Security & DPA

Give your agent a governed backend.

Free: 3 projects and preview deploys, no card. Paid plans from $9.99/mo.

Start building free Book a demo