update_schema

Active

declared in 0.10.2

Update a project's schema (saves to database, does NOT deploy). ⚠️ CRITICAL: Follow ALL rules from create_project: • FLAT format (no 'fields' nesting) • string: MUST have max_length • decimal: MUST have precision + scale • Use "datetime" NOT "timestamp" • DON'T define: id, created_at, updated_at • NEVER create users/customers/employees tables (use app_users) ⚠️ MIGRATION RULES: • New fields MUST be "required": false OR have "default" value • Cannot add required field without default to existing tables • Safe: {new_field: {type: "string", max_length: 100, required: false}} WORKFLOW: 1. Use get_schema to see current schema 2. Modify following ALL rules 3. Call update_schema (saves only) 4. Call deploy_staging to apply changes 5. Monitor with get_job_status NOTE: This only saves the schema. You MUST call deploy_staging afterwards to apply changes.

Parameters schema

{
  "type": "object",
  "required": [
    "project_id",
    "schema"
  ],
  "properties": {
    "schema": {
      "type": "object",
      "description": "New JSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property."
    },
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  }
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.50.

Parent server

RationalBloks

https://github.com/rationalbloks/rationalbloks-mcp

1/7 registries

View full server →