RationalBloks

Official44 toolsLive

by rationalbloks · Python

Deploy production REST APIs from JSON schemas in seconds. Manage projects, schemas, and deployments.

RationalBloks MCP is a server that lets AI agents deploy production REST APIs directly from JSON schemas. It manages projects, schemas, and deployments, reducing the need to write backend code or configure infrastructure.

🛠️ Key Features

Deploy production APIs from JSON schemas
Manage projects, schemas, and deployments
Graph data support and tooling included
Production-ready with minimal setup

🚀 Use Cases

Deploying APIs for AI agent workflows
Rapid prototyping of REST endpoints from schema definitions
Centralized management of multiple schemas and deployments

⚡ Developer Benefits

No backend implementation required
Quick start with existing JSON schemas
Python 3.10+ compatibility; PyPI package available

⚠️ Limitations

Proprietary license (as indicated by readme)
Focused on JSON-schema-driven API deployment; may not cover all backend patterns
Requires environment capable of running Python applications

Captured live from the server via tools/list.

list_projects

List all your RationalBloks projects with their status and URLs

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

get_project

Get detailed information about a specific project

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

get_schema

Get the JSON schema definition of a project in FLAT format. Returns the schema structure where each table name maps directly to field definitions. This is the same format required for create_project and update_schema. USE CASES: Review current schema before making updates, copy schema as template for new projects, verify schema structure after deployment, learn the correct schema format by example. The returned schema will be in FLAT format: {table_name: {field_name: {type, properties}}}

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

get_user_info

Get information about the authenticated user

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

get_job_status

Check the status of a deployment job. STATUS VALUES: pending (job queued), running (deployment in progress), completed (success), failed (deployment failed). TIMELINE: Typical deployment takes 2-5 minutes. If status is 'running' for >10 minutes, check get_project_info for detailed pod status. If status is 'failed', use get_project_info to see deployment errors and check schema format (must be FLAT, no 'fields' nesting).

Parameters1

job_id

string

required

Job ID returned from deployment operations

Raw schema

{
  "type": "object",
  "properties": {
    "job_id": {
      "type": "string",
      "description": "Job ID returned from deployment operations"
    }
  },
  "required": [
    "job_id"
  ]
}

get_project_info

Get detailed project info including deployment status and resource usage. DEPLOYMENT STATUS: Running (healthy), Pending (starting), CrashLoopBackOff (init container failed - usually schema format error), ImagePullBackOff (image build failed). TROUBLESHOOTING: If status is CrashLoopBackOff, the schema is likely in wrong format (nested 'fields' key or missing 'type' properties). Use get_schema to review current schema. If replicas show 0/2, the init container (migration runner) is failing. This is almost always a schema format issue.

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

get_version_history

Get the deployment and version history (git commits) for a project. Shows all schema changes with commit SHA, timestamp, and message. USE CASES: Review what changed between deployments, find the last working version before issues started, get commit SHA for rollback_project.

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

get_template_schemas

Get pre-built template schemas for common use cases. ⭐ USE THIS FIRST when creating a new project! Templates show the CORRECT schema format with: proper FLAT structure (no 'fields' nesting), every field has a 'type' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: E-commerce (products, orders, customers), Team collaboration (projects, tasks, users), General purpose templates. You can use these templates directly with create_project or modify them for your needs. TIP: Study these templates to understand the correct schema format before creating custom schemas.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

get_subscription_status

Get your subscription tier, limits, and usage

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

get_project_usage

Get resource usage metrics (CPU, memory) for a project

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

get_schema_at_version

Get the schema as it was at a specific version/commit

Parameters2

project_id	string	required	Project ID (UUID)
version	string	required	Commit SHA of the version

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "version": {
      "type": "string",
      "description": "Commit SHA of the version"
    }
  },
  "required": [
    "project_id",
    "version"
  ]
}

create_project

Create a new RationalBloks project from a JSON schema. ⚠️ CRITICAL RULES - READ BEFORE CREATING SCHEMA: 1. FLAT FORMAT (REQUIRED): ✅ CORRECT: {users: {email: {type: "string", max_length: 255}}} ❌ WRONG: {users: {fields: {email: {type: "string"}}}} DO NOT nest under 'fields' key! 2. FIELD TYPE REQUIREMENTS: • string: MUST have "max_length" (e.g., max_length: 255) • decimal: MUST have "precision" and "scale" (e.g., precision: 10, scale: 2) • datetime: Use "datetime" NOT "timestamp" • ALL fields: MUST have "type" property 3. AUTOMATIC FIELDS (DON'T define): • id (uuid, primary key) • created_at (datetime) • updated_at (datetime) 4. USER AUTHENTICATION: ❌ NEVER create "users", "customers", "employees" tables with email/password ✅ USE built-in app_users table Example: { "employee_profiles": { "user_id": {type: "uuid", foreign_key: "app_users.id", required: true}, "department": {type: "string", max_length: 100} } } 5. AUTHORIZATION: Add user_id → app_users.id to enable "only see your own data" Example: { "orders": { "user_id": {type: "uuid", foreign_key: "app_users.id"}, "total": {type: "decimal", precision: 10, scale: 2} } } 6. FIELD OPTIONS: • required: true/false • unique: true/false • default: any value • enum: ["val1", "val2"] • foreign_key: "table.id" AVAILABLE TYPES: string, text, integer, decimal, boolean, uuid, date, datetime, json, uuid_array, integer_array, text_array, float_array Array types store PostgreSQL native arrays with automatic GIN indexing: • uuid_array: UUID[] — for sets of references (e.g., tensor coordinates) • integer_array: BIGINT[] — for dimension indices, integer sets • text_array: TEXT[] — for tags, categories, label sets • float_array: DOUBLE PRECISION[] — for weight vectors, scores GIN-indexed operators: @> (contains), <@ (contained_by), && (overlaps) BACKEND ENGINE: • python (default): FastAPI backend — mature, full-featured • rust: Axum backend — faster cold starts, lower memory, high performance WORKFLOW: 1. Use get_template_schemas FIRST to see valid examples 2. Create schema following ALL rules above 3. Call this tool (optionally choose backend_type: "python" or "rust") 4. Monitor with get_job_status (2-5 min deployment) After creation, use get_job_status with returned job_id to monitor deployment.

Parameters4

name	string	required	Project name
schema	object	required	JSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property. Use get_template_schemas to see valid examples.
description	string	optional	Optional project description
backend_type	string	optional	Backend engine: 'python' (FastAPI, default) or 'rust' (Axum, faster). Default: python

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Project name"
    },
    "schema": {
      "type": "object",
      "description": "JSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property. Use get_template_schemas to see valid examples."
    },
    "description": {
      "type": "string",
      "description": "Optional project description"
    },
    "backend_type": {
      "type": "string",
      "enum": [
        "python",
        "rust"
      ],
      "description": "Backend engine: 'python' (FastAPI, default) or 'rust' (Axum, faster). Default: python"
    }
  },
  "required": [
    "name",
    "schema"
  ]
}

update_schema

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.

Parameters2

project_id	string	required	Project ID (UUID)
schema	object	required	New JSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property.

Raw schema

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

deploy_staging

Deploy a project to the staging environment. This triggers: (1) Schema validation, (2) Docker image build, (3) GitHub commit, (4) Kubernetes deployment, (5) Database migrations. The operation is ASYNCHRONOUS - it returns immediately with a job_id. Use get_job_status with the job_id to monitor progress. Deployment typically takes 2-5 minutes depending on schema complexity. If deployment fails, check: (1) Schema format is FLAT (no 'fields' nesting), (2) Every field has a 'type' property, (3) Foreign keys reference existing tables, (4) No PostgreSQL reserved words in table/field names. Use get_project_info to see if the deployment succeeded.

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

deploy_production

Promote staging to production (requires paid plan)

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

delete_project

Delete a project (removes GitHub repo, K8s deployments, and database)

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

rollback_project

Rollback a project to a previous version. ⚠️ WARNING: This reverts schema AND code to the specified commit. Database data is NOT rolled back. Use get_version_history to find the commit SHA of the version you want to rollback to. After rollback, use get_job_status to monitor the redeployment. Rollback is useful when a schema change breaks deployment.

Parameters3

project_id	string	required	Project ID (UUID)
version	string	required	Commit SHA or version to rollback to
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "version": {
      "type": "string",
      "description": "Commit SHA or version to rollback to"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "version"
  ]
}

rename_project

Rename a project (changes display name, not project_code)

Parameters2

project_id	string	required	Project ID (UUID)
name	string	required	New display name for the project

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "name": {
      "type": "string",
      "description": "New display name for the project"
    }
  },
  "required": [
    "project_id",
    "name"
  ]
}

get_graph_schema

Get the graph schema definition of a project. Returns the hierarchical schema with nodes (entities) and relationships. Graph schemas define entity hierarchies and typed relationships — a different format than relational flat-table schemas.

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

get_graph_template_schemas

Get pre-built graph template schemas for common use cases. ⭐ USE THIS FIRST when creating a new graph project! Templates show the CORRECT graph schema format with: proper node definitions (description, flat_labels, schema with flat field definitions), relationship configurations (from, to, cardinality, data_schema), and hierarchical entity nesting. Available templates: Social Network (users, posts, follows), Knowledge Graph (topics, articles, authors), Product Catalog (products, categories, suppliers). You can use these templates directly with create_graph_project or modify them for your needs. TIP: Study these templates to understand the correct graph schema format before creating custom schemas.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

get_graph_version_history

Get the deployment and version history for a graph project. Shows all schema changes with commit SHAs, timestamps, version numbers, and messages. Use this to find a specific version for rollback operations.

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

get_graph_schema_at_version

Get the graph schema as it existed at a specific version/commit. Use get_graph_version_history to find commit SHAs. Useful for comparing schemas across versions or auditing changes.

Parameters2

project_id	string	required	Project ID (UUID)
version	string	required	Commit SHA of the version to retrieve

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "version": {
      "type": "string",
      "description": "Commit SHA of the version to retrieve"
    }
  },
  "required": [
    "project_id",
    "version"
  ]
}

get_graph_project_info

Get detailed graph project information including Kubernetes deployment status, Neo4j database health, pod status, and resource usage. Use this after deployment to verify the graph project is running correctly.

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

create_graph_project

Create a new Neo4j graph database project from a hierarchical JSON schema. ⚠️ GRAPH SCHEMA FORMAT — READ BEFORE CREATING: Graph schemas define nodes (entities) and relationships, NOT flat database tables. Each field is a dict with "type" and optional "required": true (defaults to false). SCHEMA STRUCTURE: { "nodes": { "EntityName": { "description": "What this entity represents", "flat_labels": ["AdditionalLabel"], "schema": { "field_name": {"type": "string", "required": true}, "other_field": {"type": "integer"} } } }, "relationships": { "RELATIONSHIP_TYPE": { "from": "EntityName", "to": "OtherEntity", "cardinality": "MANY_TO_MANY", "data_schema": { "field_name": {"type": "date"} } } } } FIELD TYPES: string, integer, float, boolean, date, json CARDINALITY OPTIONS: ONE_TO_ONE, ONE_TO_MANY, MANY_TO_ONE, MANY_TO_MANY HIERARCHICAL NODES: Nest entities inside parent entities to create type hierarchies. Child entities inherit parent labels automatically. Example: { "nodes": { "Animal": { "description": "Base animal entity", "flat_labels": ["LivingThing"], "schema": { "name": {"type": "string", "required": true}, "habitat": {"type": "string"} }, "Dog": { "description": "A dog (inherits Animal labels)", "flat_labels": ["Pet"], "schema": { "breed": {"type": "string", "required": true}, "trained": {"type": "boolean"} } } } }, "relationships": { "OWNS": { "from": "Person", "to": "Animal", "cardinality": "ONE_TO_MANY" } } } RULES: 1. "nodes" key is REQUIRED — must contain at least one entity 2. Each entity needs "description" and "schema" with field definitions 3. Each field is {"type": "...", "required": true/false} — required defaults to false 4. Relationship "from"/"to" must reference defined node names 5. Relationship types should be UPPER_SNAKE_CASE 6. Entity names should be PascalCase 7. Automatic fields (id, created_at, updated_at) are NOT needed 8. Use get_graph_template_schemas FIRST to see valid examples WORKFLOW: 1. Use get_graph_template_schemas to see valid examples 2. Create schema following the rules above 3. Call this tool 4. Monitor with get_job_status (2-5 min deployment) After creation, use get_job_status with returned job_id to monitor deployment.

Parameters3

name	string	required	Project name
schema	object	required	Graph schema with 'nodes' and optionally 'relationships' keys. Use get_graph_template_schemas to see valid examples.
description	string	optional	Optional project description

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Project name"
    },
    "schema": {
      "type": "object",
      "description": "Graph schema with 'nodes' and optionally 'relationships' keys. Use get_graph_template_schemas to see valid examples."
    },
    "description": {
      "type": "string",
      "description": "Optional project description"
    }
  },
  "required": [
    "name",
    "schema"
  ]
}

update_graph_schema

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.

Parameters2

project_id	string	required	Project ID (UUID)
schema	object	required	New graph schema with 'nodes' and optionally 'relationships' keys.

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "schema": {
      "type": "object",
      "description": "New graph schema with 'nodes' and optionally 'relationships' keys."
    }
  },
  "required": [
    "project_id",
    "schema"
  ]
}

deploy_graph_staging

Deploy a graph project to the staging environment. This triggers: (1) Schema validation, (2) Neo4j entity code generation, (3) Docker image build, (4) GitHub commit, (5) Kubernetes deployment with Neo4j instance. The operation is ASYNCHRONOUS — returns immediately with a job_id. Use get_job_status to monitor progress. Deployment typically takes 2-5 minutes. Use get_graph_project_info to verify deployment succeeded.

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

deploy_graph_production

Promote graph staging to production. Creates a separate production Neo4j instance with its own credentials and database. Requires paid plan.

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

delete_graph_project

Delete a graph project (removes GitHub repo, K8s deployments, Neo4j database, and credentials)

Parameters1

project_id

string

required

Project ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    }
  },
  "required": [
    "project_id"
  ]
}

rollback_graph_project

Rollback a graph project to a previous version. ⚠️ WARNING: This reverts schema AND code to the specified commit. Neo4j data is NOT rolled back. Use get_graph_version_history to find the commit SHA of the version you want to rollback to. After rollback, the graph API will be redeployed with the old schema.

Parameters3

project_id	string	required	Project ID (UUID)
version	string	required	Commit SHA to rollback to
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "version": {
      "type": "string",
      "description": "Commit SHA to rollback to"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "version"
  ]
}

create_graph_node

Create a single node in a deployed graph project. REQUIRES: Project must be deployed (use deploy_graph_staging first). The entity_type must match an entity key from the project schema. Use get_graph_data_schema to see available entity types and their fields. Example: entity_type: "person" entity_id: "alan-turing-001" data: {"name": "Alan Turing", "birth_year": 1912, "field": "Computer Science"} The entity_id is your unique identifier — use meaningful IDs for knowledge graphs.

Parameters5

project_id	string	required	Project ID (UUID)
entity_type	string	required	Entity key (e.g., 'person', 'concept')
entity_id	string	required	Unique identifier for the node
data	object	required	Node properties matching the entity schema
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "entity_id": {
      "type": "string",
      "description": "Unique identifier for the node"
    },
    "data": {
      "type": "object",
      "description": "Node properties matching the entity schema"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id",
    "data"
  ]
}

get_graph_node

Get a specific node by its entity_id from a deployed graph project. Returns all node properties including created_at and updated_at timestamps.

Parameters4

project_id	string	required	Project ID (UUID)
entity_type	string	required	Entity key (e.g., 'person', 'concept')
entity_id	string	required	The node's entity_id
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "entity_id": {
      "type": "string",
      "description": "The node's entity_id"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id"
  ]
}

list_graph_nodes

List nodes of a specific entity type from a deployed graph project. Supports pagination with limit/offset. Returns nodes ordered by creation date (newest first).

Parameters5

project_id	string	required	Project ID (UUID)
entity_type	string	required	Entity key (e.g., 'person', 'concept')
limit	integer	optional	Max results (default: 100, max: 1000)
offset	integer	optional	Pagination offset (default: 0)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "limit": {
      "type": "integer",
      "description": "Max results (default: 100, max: 1000)"
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset (default: 0)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type"
  ]
}

update_graph_node

Update properties of an existing node in a deployed graph project. Only send the fields you want to change — unspecified fields remain unchanged.

Parameters5

project_id	string	required	Project ID (UUID)
entity_type	string	required	Entity key (e.g., 'person', 'concept')
entity_id	string	required	The node's entity_id
data	object	required	Properties to update (partial update)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "entity_id": {
      "type": "string",
      "description": "The node's entity_id"
    },
    "data": {
      "type": "object",
      "description": "Properties to update (partial update)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id",
    "data"
  ]
}

delete_graph_node

Delete a node and all its relationships from a deployed graph project. ⚠️ This also removes all relationships connected to this node (DETACH DELETE).

Parameters4

project_id	string	required	Project ID (UUID)
entity_type	string	required	Entity key (e.g., 'person', 'concept')
entity_id	string	required	The node's entity_id
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key (e.g., 'person', 'concept')"
    },
    "entity_id": {
      "type": "string",
      "description": "The node's entity_id"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id"
  ]
}

create_graph_relationship

Create a relationship between two nodes in a deployed graph project. The rel_type must match a relationship key from the project schema. Use get_graph_data_schema to see available relationship types. Example: rel_type: "authored" from_id: "alan-turing-001" to_id: "on-computable-numbers-001" data: {"year": 1936} The from_id and to_id must be entity_ids of existing nodes.

Parameters6

project_id	string	required	Project ID (UUID)
rel_type	string	required	Relationship key (e.g., 'authored', 'related_to')
from_id	string	required	Source node entity_id
to_id	string	required	Target node entity_id
data	object	optional	Relationship properties (optional)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "rel_type": {
      "type": "string",
      "description": "Relationship key (e.g., 'authored', 'related_to')"
    },
    "from_id": {
      "type": "string",
      "description": "Source node entity_id"
    },
    "to_id": {
      "type": "string",
      "description": "Target node entity_id"
    },
    "data": {
      "type": "object",
      "description": "Relationship properties (optional)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "rel_type",
    "from_id",
    "to_id"
  ]
}

get_node_relationships

Get all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering.

Parameters6

project_id	string	required	Project ID (UUID)
entity_type	string	required	Entity key of the node
entity_id	string	required	The node's entity_id
direction	string	optional	Filter: incoming, outgoing, or both (default: both)
rel_type_filter	string	optional	Filter by relationship type (UPPER_SNAKE_CASE)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key of the node"
    },
    "entity_id": {
      "type": "string",
      "description": "The node's entity_id"
    },
    "direction": {
      "type": "string",
      "description": "Filter: incoming, outgoing, or both (default: both)"
    },
    "rel_type_filter": {
      "type": "string",
      "description": "Filter by relationship type (UPPER_SNAKE_CASE)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "entity_id"
  ]
}

delete_graph_relationship

Delete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs.

Parameters4

project_id	string	required	Project ID (UUID)
rel_type	string	required	Relationship key
rel_id	integer	required	Internal relationship ID (from get_node_relationships)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "rel_type": {
      "type": "string",
      "description": "Relationship key"
    },
    "rel_id": {
      "type": "integer",
      "description": "Internal relationship ID (from get_node_relationships)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "rel_type",
    "rel_id"
  ]
}

bulk_create_graph_nodes

Create multiple nodes at once (up to 500 per call). Uses Neo4j UNWIND for high performance. Essential for knowledge graph population — create hundreds of entities from a single book chapter or article. Each node needs: entity_id (unique string) and data (properties dict). Example: entity_type: "concept" nodes: [ {"entity_id": "quantum-mechanics-001", "data": {"name": "Quantum Mechanics", "field": "Physics"}}, {"entity_id": "wave-function-001", "data": {"name": "Wave Function", "field": "Physics"}}, {"entity_id": "superposition-001", "data": {"name": "Superposition", "field": "Physics"}} ]

Parameters4

project_id	string	required	Project ID (UUID)
entity_type	string	required	Entity key for all nodes
nodes	array	required	List of nodes. Each: {entity_id: string, data: {properties}}
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key for all nodes"
    },
    "nodes": {
      "type": "array",
      "description": "List of nodes. Each: {entity_id: string, data: {properties}}",
      "items": {
        "type": "object",
        "properties": {
          "entity_id": {
            "type": "string"
          },
          "data": {
            "type": "object"
          }
        },
        "required": [
          "entity_id",
          "data"
        ]
      }
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "entity_type",
    "nodes"
  ]
}

bulk_create_graph_relationships

Create multiple relationships at once (up to 500 per call). Uses Neo4j UNWIND for high performance. Essential for connecting knowledge — link hundreds of concepts, people, and events in one operation. Each relationship needs: from_id, to_id, and optional data (properties). Example: rel_type: "related_to" relationships: [ {"from_id": "quantum-mechanics-001", "to_id": "wave-function-001", "data": {"strength": "strong"}}, {"from_id": "quantum-mechanics-001", "to_id": "superposition-001", "data": {"strength": "strong"}} ]

Parameters4

project_id	string	required	Project ID (UUID)
rel_type	string	required	Relationship key for all relationships
relationships	array	required	List of relationships. Each: {from_id, to_id, data?}
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "rel_type": {
      "type": "string",
      "description": "Relationship key for all relationships"
    },
    "relationships": {
      "type": "array",
      "description": "List of relationships. Each: {from_id, to_id, data?}",
      "items": {
        "type": "object",
        "properties": {
          "from_id": {
            "type": "string"
          },
          "to_id": {
            "type": "string"
          },
          "data": {
            "type": "object"
          }
        },
        "required": [
          "from_id",
          "to_id"
        ]
      }
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "rel_type",
    "relationships"
  ]
}

search_graph_nodes

Search for nodes by property values in a deployed graph project. Supports exact match and contains search (prefix value with ~ for contains). Examples: Exact: filters: {"name": "Alan Turing"} Contains: filters: {"name": "~turing"} (case-insensitive) Combined: entity_type: "person", filters: {"field": "~physics"} Without entity_type, searches ALL node types.

Parameters6

project_id	string	required	Project ID (UUID)
entity_type	string	optional	Entity key to filter by (optional — omit to search all types)
filters	object	required	Property filters. Prefix value with ~ for contains search.
limit	integer	optional	Max results (default: 100, max: 1000)
offset	integer	optional	Pagination offset (default: 0)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key to filter by (optional — omit to search all types)"
    },
    "filters": {
      "type": "object",
      "description": "Property filters. Prefix value with ~ for contains search."
    },
    "limit": {
      "type": "integer",
      "description": "Max results (default: 100, max: 1000)"
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset (default: 0)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "filters"
  ]
}

fulltext_search_graph

Search across ALL string properties of ALL nodes in a deployed graph using free-text queries. Unlike search_graph_nodes (which filters by specific property), this searches every text field at once. Perfect for finding knowledge when you don't know which property contains the answer. Example: query "quantum" searches name, description, summary, notes, and all other string fields. Returns nodes with _match_fields showing which properties matched. Optionally filter by entity_type to narrow results.

Parameters6

project_id	string	required	Project ID (UUID)
query	string	required	Search text (case-insensitive, min 2 chars)
entity_type	string	optional	Entity key to filter by (optional — omit to search all types)
limit	integer	optional	Max results (default: 50, max: 500)
offset	integer	optional	Pagination offset (default: 0)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "query": {
      "type": "string",
      "description": "Search text (case-insensitive, min 2 chars)"
    },
    "entity_type": {
      "type": "string",
      "description": "Entity key to filter by (optional — omit to search all types)"
    },
    "limit": {
      "type": "integer",
      "description": "Max results (default: 50, max: 500)"
    },
    "offset": {
      "type": "integer",
      "description": "Pagination offset (default: 0)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "query"
  ]
}

traverse_graph

Walk the graph from a starting node, discovering connected knowledge. Returns all nodes reachable within max_depth hops, with their distance from the start. Essential for exploring knowledge graphs — find related concepts, trace connections, discover clusters. Example: Start from "Alan Turing", traverse outgoing relationships up to 3 hops deep: start_entity_type: "person" start_entity_id: "alan-turing-001" max_depth: 3 direction: "outgoing" Supports filtering by relationship types and direction.

Parameters8

project_id	string	required	Project ID (UUID)
start_entity_type	string	required	Entity key of the starting node
start_entity_id	string	required	Entity ID of the starting node
max_depth	integer	optional	Maximum traversal depth (default: 3, max: 10)
relationship_types	array	optional	Filter by relationship types (UPPER_SNAKE_CASE). Omit for all types.
direction	string	optional	Direction: outgoing, incoming, or both (default: both)
limit	integer	optional	Max results (default: 100, max: 1000)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "start_entity_type": {
      "type": "string",
      "description": "Entity key of the starting node"
    },
    "start_entity_id": {
      "type": "string",
      "description": "Entity ID of the starting node"
    },
    "max_depth": {
      "type": "integer",
      "description": "Maximum traversal depth (default: 3, max: 10)"
    },
    "relationship_types": {
      "type": "array",
      "description": "Filter by relationship types (UPPER_SNAKE_CASE). Omit for all types.",
      "items": {
        "type": "string"
      }
    },
    "direction": {
      "type": "string",
      "description": "Direction: outgoing, incoming, or both (default: both)"
    },
    "limit": {
      "type": "integer",
      "description": "Max results (default: 100, max: 1000)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id",
    "start_entity_type",
    "start_entity_id"
  ]
}

get_graph_statistics

Get statistics about a deployed graph: total node count, total relationship count, counts per entity type, counts per relationship type. Essential for understanding the current state of a knowledge graph before adding more data.

Parameters2

project_id	string	required	Project ID (UUID)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id"
  ]
}

get_graph_data_schema

Get the runtime schema of a DEPLOYED graph project — shows the actual entity types and relationship types available for data operations. Returns: Available entity keys (for create_graph_node, list_graph_nodes, etc.) and relationship keys (for create_graph_relationship, etc.). ⭐ USE THIS FIRST before creating nodes/relationships to know what entity_type and rel_type values are valid.

Parameters2

project_id	string	required	Project ID (UUID)
environment	string	optional	Environment: staging or production (default: staging)

Raw schema

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "description": "Project ID (UUID)"
    },
    "environment": {
      "type": "string",
      "description": "Environment: staging or production (default: staging)"
    }
  },
  "required": [
    "project_id"
  ]
}

README.md6 KBView on GitHub

RationalBloks MCP Server

Deploy production APIs in minutes. 47 tools for projects, schemas, deployments, object storage, and graph data.

What Is This?

RationalBloks MCP lets AI agents (Claude, Cursor, etc.) deploy production APIs from a JSON schema. No backend code to write. No infrastructure to manage.

code

"Create a task management API with tasks, projects, and users"
→ 2 minutes later: Production API running on Kubernetes

Installation

bash

pip install rationalbloks-mcp

Quick Start

1. Get Your API Key

Visit rationalbloks.com/settings and create an API key.

2. Configure Your AI Agent

VS Code / Cursor - Add to settings.json:

json

{
  "mcp.servers": {
    "rationalbloks": {
      "command": "rationalbloks-mcp",
      "env": {
        "RATIONALBLOKS_API_KEY": "rb_sk_your_key_here"
      }
    }
  }
}

Claude Desktop - Add to claude_desktop_config.json:

json

{
  "mcpServers": {
    "rationalbloks": {
      "command": "rationalbloks-mcp",
      "env": {
        "RATIONALBLOKS_API_KEY": "rb_sk_your_key_here"
      }
    }
  }
}

47 Tools

Relational Read Operations (14 tools)

Tool	Description
`list_projects`	List all your projects
`get_project`	Get project details
`get_schema`	Get current JSON schema
`get_user_info`	Get authenticated user info
`get_job_status`	Check deployment job status
`get_project_info`	Detailed project info with K8s status
`get_version_history`	Git commit history
`get_template_schemas`	Pre-built schema templates
`get_subscription_status`	Plan and usage limits
`get_project_usage`	CPU/memory metrics
`get_project_storage_usage`	Object-storage file count and bytes used vs limits
`list_project_files`	List uploaded files (metadata + public URLs)
`get_schema_at_version`	Schema at specific commit
`list_clusters`	List your BYOC resource pools (client-owned clusters)

Relational Write Operations (7 tools)

Tool	Description
`create_project`	Create new project from schema
`update_schema`	Update project schema
`deploy_staging`	Deploy to staging environment
`deploy_production`	Deploy to production
`delete_project`	Delete project permanently
`rollback_project`	Rollback to previous version
`rename_project`	Rename project

Graph Schema Operations (11 tools)

Tool	Description
`get_graph_schema`	Get graph project schema
`get_graph_template_schemas`	Pre-built graph schema templates
`get_graph_version_history`	Graph schema version history
`get_graph_schema_at_version`	Schema at specific version
`get_graph_project_info`	Graph project info with K8s/Neo4j status
`create_graph_project`	Create Neo4j graph project
`update_graph_schema`	Update graph schema
`deploy_graph_staging`	Deploy graph to staging
`deploy_graph_production`	Deploy graph to production
`delete_graph_project`	Delete graph project
`rollback_graph_project`	Rollback graph to previous version

Graph Data Operations (15 tools)

Tool	Description
`create_graph_node`	Create a single node
`get_graph_node`	Get node by ID
`list_graph_nodes`	List nodes by entity type
`update_graph_node`	Update node properties
`delete_graph_node`	Delete a node
`create_graph_relationship`	Create a relationship
`get_node_relationships`	Get node's relationships
`delete_graph_relationship`	Delete a relationship
`bulk_create_graph_nodes`	Bulk create nodes
`bulk_create_graph_relationships`	Bulk create relationships
`search_graph_nodes`	Search nodes by property filters
`fulltext_search_graph`	Full-text search across all fields
`traverse_graph`	Traverse graph from a node
`get_graph_statistics`	Get graph statistics (counts)
`get_graph_data_schema`	Get deployed data schema

Schema Format

Schemas must be in FLAT format:

json

{
  "tasks": {
    "title": {"type": "string", "max_length": 200, "required": true},
    "status": {"type": "string", "max_length": 50, "enum": ["pending", "done"]},
    "due_date": {"type": "date", "required": false}
  },
  "projects": {
    "name": {"type": "string", "max_length": 100, "required": true}
  }
}

Field Types

Type	Required Properties
`string`	`max_length`
`text`	None
`integer`	None
`decimal`	`precision`, `scale`
`boolean`	None
`uuid`	None
`date`	None
`datetime`	None
`json`	None

Auto-Generated Fields

These are automatic - don't define them:

id (UUID primary key)
created_at (datetime)
updated_at (datetime)

User Authentication

Use the built-in app_users table:

json

{
  "employee_profiles": {
    "user_id": {"type": "uuid", "foreign_key": "app_users.id", "required": true},
    "department": {"type": "string", "max_length": 100}
  }
}

Frontend

For frontend development, use our NPM packages:

bash

npm install @rationalbloks/frontblok-auth @rationalbloks/frontblok-crud

These provide:

frontblok-auth: Authentication, login, tokens, user context
frontblok-crud: Generic CRUD via getApi().getAll(), getApi().create(), etc.

Environment Variables

Variable	Description	Default
`RATIONALBLOKS_API_KEY`	Your API key (required)	-
`RATIONALBLOKS_TIMEOUT`	Request timeout (seconds)	`30`
`RATIONALBLOKS_LOG_LEVEL`	Log level	`INFO`

Support

Documentation: rationalbloks.com/docs
Email: support@rationalbloks.com

License

Install

Tools (44)

list_projectsget_projectget_schemaget_user_infoget_job_statusget_project_infoget_version_historyget_template_schemas

Configuration

Environment variables

RATIONALBLOKS_API_KEYrequiredsecret

Your RationalBloks API key (get it from rationalbloks.com/settings)

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "rationalbloks-mcp": {
      "command": "uvx",
      "args": [
        "rationalbloks-mcp"
      ],
      "env": {
        "RATIONALBLOKS_API_KEY": "<YOUR_RATIONALBLOKS_API_KEY>"
      }
    }
  }
}

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

list_projects

get_project

get_schema

get_user_info

get_job_status

get_project_info

get_version_history

get_template_schemas

get_subscription_status

get_project_usage

get_schema_at_version

create_project

update_schema

deploy_staging

deploy_production

delete_project

rollback_project

rename_project

get_graph_schema

get_graph_template_schemas

get_graph_version_history

get_graph_schema_at_version

get_graph_project_info

create_graph_project

update_graph_schema

deploy_graph_staging

deploy_graph_production

delete_graph_project

rollback_graph_project

create_graph_node

get_graph_node

list_graph_nodes

update_graph_node

delete_graph_node

create_graph_relationship

get_node_relationships

delete_graph_relationship

bulk_create_graph_nodes

bulk_create_graph_relationships

search_graph_nodes

fulltext_search_graph

traverse_graph

get_graph_statistics

get_graph_data_schema

RationalBloks MCP Server

What Is This?

Installation

Quick Start

1. Get Your API Key

2. Configure Your AI Agent

47 Tools

Relational Read Operations (14 tools)

Relational Write Operations (7 tools)

Graph Schema Operations (11 tools)

Graph Data Operations (15 tools)

Schema Format

Field Types

Auto-Generated Fields

User Authentication

Frontend

Environment Variables

Support

License

Install

Configuration

Related servers