update_graph_schema

Active

declared in 0.10.2

Update a graph project's schema (saves to database, does NOT deploy). ⚠️ Follow ALL rules from create_graph_project: • Must have "nodes" key with at least one entity • Each entity needs "description" and "schema" with field definitions • Each field is {"type": "...", "required": true/false} — required defaults to false • Relationships need "from", "to", and "cardinality" • Field types: string, integer, float, boolean, date, json • Relationship types should be UPPER_SNAKE_CASE • Entity names should be PascalCase WORKFLOW: 1. Use get_graph_schema to see current schema 2. Modify following all rules 3. Call update_graph_schema (saves only) 4. Call deploy_graph_staging to apply changes 5. Monitor with get_job_status NOTE: This only saves the schema. You MUST call deploy_graph_staging afterwards to deploy.

Parameters schema

{
  "type": "object",
  "required": [
    "project_id",
    "schema"
  ],
  "properties": {
    "schema": {
      "type": "object",
      "description": "New graph schema with 'nodes' and optionally 'relationships' keys."
    },
    "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.70.

Parent server

RationalBloks

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

1/7 registries

View full server →