Name: RationalBloks
Author: rationalbloks

Tools observed via MCP handshake

list_projects — List all your RationalBloks projects with their status and URLs
get_project — Get detailed information about a specific project
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 s
get_user_info — Get information about the authenticated user
list_clusters — List your registered BYOC resource pools (client-owned Kubernetes clusters). Each returned cluster has an 'id' you MUST pass as create_project's cluster_id to d
get_job_status — Check the status of a deployment job. STATUS VALUES: pending (job queued), running (deployment in progress), completed (success), failed (deployment failed). TI
get_project_info — Get detailed project info including deployment status and resource usage. DEPLOYMENT STATUS: Running (healthy), Pending (starting), CrashLoopBackOff (init conta
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 cha
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 st
get_schema_reference — Get the reference for ADVANCED schema features the templates do not show — read this before adding authorization or derived fields to a schema. Covers: __policy
get_subscription_status — Get your subscription tier, limits, and usage
get_project_usage — Get resource usage metrics (CPU, memory) for a project
get_project_storage_usage — Get object-storage usage for a project: file count and bytes used against the plan limits.
list_project_files — List a project's uploaded files (metadata + public URLs), most recent first. Inspection only — files are not streamed through MCP.
get_schema_at_version — Get the schema as it was at a specific version/commit
create_project — Create a new RationalBloks project from a JSON schema. ⚠️ CRITICAL RULES - READ BEFORE CREATING SCHEMA: 1. FLAT FORMAT (REQUIRED): ✅ CORRECT: {users: {emai
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
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) Dat
deploy_production — Promote staging to production (requires paid plan)
delete_project — Delete a project (removes GitHub repo, K8s deployments, and database)
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_hi
rename_project — Rename a project (changes display name, not project_code)
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 a
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 wi
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 fi
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
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
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
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
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 co
deploy_graph_production — Promote graph staging to production. Creates a separate production Neo4j instance with its own credentials and database. Requires paid plan.
delete_graph_project — Delete a graph project (removes GitHub repo, K8s deployments, Neo4j database, and credentials)
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_v
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 ke
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.
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)
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.
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).
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_sch
get_node_relationships — Get all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering.
delete_graph_relationship — Delete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs.
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 entit
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 conce
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: Exac
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), t
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. Es
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 understan
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 ent

RationalBloks

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from