RationalBloks
Deploy production REST and Neo4j Graph APIs from JSON schemas in seconds.
| Endpoint | https://mcp.rationalbloks.com (streamable-http) |
|---|---|
| Registry version | 0.16.1 |
| Now | 64 tools · grade D (55) · pin ts_4e2742c8e4f816db0c29a15aa6eb878f · protocol 2025-06-18 |
| First / last listed | 2026-10-26 03:26 UTC / 2026-10-26 03:26 UTC |
| Grade over time | 2026-10-26: D (55), 64 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: list_projects get_project get_schema get_user_info list_clusters get_job_status list_project_jobs get_project_info get_version_history get_template_schemas get_schema_reference get_subscription_status get_project_usage get_project_storage_usage list_project_files get_schema_at_version preview_schema_change create_project update_schema patch_schema drop_schema_items deploy_staging deploy_production deploy_destructive redeploy_project 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 list_modules deploy_module redeploy_module update_module delete_module set_module_env freeze_module unfreeze_module scale_module set_module_resources
list_projects | List all your RationalBloks projects with their status and URLs params: none |
get_project | Get detailed information about a specific project params: 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 params: project_id*, tables, fields |
get_user_info | Get information about the authenticated user params: none |
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 deploy a project onto your own infrastructure — owned hosting is retired, so every project we operate runs on your own cluster. Registering a pool is a UI action (create a bare Ubuntu box, authorise the key we generate, then we provision it params: none |
get_job_status | Check the status of a job (a create, deploy, promotion, rollback, deletion or module operation). STATUS VALUES: pending (queued), processing (in progress), completed (success), failed. Call it until the status is completed or failed: every job ends, since a job whose server stopped is failed within about three minutes, and a deploy can take up to 15 minutes. A module job names its module_code, and params: job_id* |
list_project_jobs | List a project's jobs, newest first: every create, deploy, promotion, rollback, resource change and module operation, each with its status, error, failure_side and when it started and ended. A job's record is kept for the life of the project, so this is how to find out what an operation did when you no longer have its job_id (after an interruption, or in a later session): the first job of the job_ params: project_id*, limit, offset |
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 re params: 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. params: 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: Start from Scratch (every field type), Team Collaboration (wor params: none |
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__ (relationship-based read/write authorization with single- and multi-hop membership paths, and the rules that decide whether adopting it is safe — it replaces creator-ownership per table and fails closed on a null link), computed columns params: none |
get_subscription_status | Get your subscription tier, limits, and usage params: none |
get_project_usage | Get resource usage metrics (CPU, memory) for a project params: project_id* |
get_project_storage_usage | Get object-storage usage for a project: file count and bytes used against the plan limits. params: project_id*, environment |
list_project_files | List a project's uploaded files (metadata + public URLs), most recent first. Inspection only — files are not streamed through MCP. params: project_id*, environment, limit, offset |
get_schema_at_version | Get the schema as it was at a specific version/commit params: project_id*, version* |
preview_schema_change | Preview a schema change, saving nothing: the one way to see what a change would do before it is saved.
Pass ONE of:
• operations: the operations patch_schema or drop_schema_items would apply (relational projects)
• schema: a whole schema in place of the saved one (relational or graph projects)
ANSWER: 'applied' (for operations), 'diff' (every property saving it would change, by path), 'summary' params: project_id*, operations, schema |
create_project | Create a new RationalBloks project (a PostgreSQL REST API) from a JSON schema, on one of your resource pools.
⚠️ CRITICAL RULES - READ BEFORE CREATING SCHEMA:
1. FLAT FORMAT (REQUIRED):
✅ CORRECT: {"orders": {"total": {"type": "decimal", "precision": 10, "scale": 2}}}
❌ WRONG: {"orders": {"fields": {...}}} — never nest under 'fields'
2. EVERY field has a "type":
string (MUST have max_l params: name*, schema*, backend_type, cluster_id* |
update_schema | Replace a project's WHOLE schema (saves to database, does NOT deploy). DESTRUCTIVE: a table or field the schema leaves out is dropped by the next deploy.
For a new data model or a template. To change part of a schema use patch_schema, and drop_schema_items to drop; sending back a large schema to change one field risks changing something else on the way.
⚠️ Follow ALL rules from create_project:
• params: project_id*, schema*, expected_version |
patch_schema | Change PART of a project's schema without dropping any of it (saves to database, does NOT deploy).
Send only the change. The server applies it to the saved schema, in order and all together, and keeps
every table and field it does not touch — including their identity, so a rename stays a rename and the
column keeps its data.
OPERATIONS (each one small object, applied in the order given):
• {"op" params: project_id*, operations*, expected_version |
drop_schema_items | Drop tables or fields from a project's saved schema (saves to database, does NOT deploy). DESTRUCTIVE: the next deploy drops their data.
OPERATIONS (applied in order and all together):
• {"op": "drop_table", "table": "clocks"}
• {"op": "drop_field", "table": "parameters", "field": "is_clock"}
A drop that cannot be applied (a table or field that is not there, a schema the deploy would refuse, suc params: project_id*, operations*, expected_version |
deploy_staging | Deploy a project's saved schema 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 deploym params: project_id* |
deploy_production | Promote staging to production (requires a paid plan): production's database migrates from the schema it runs to the one staging runs, and production runs staging's build. With staging unchanged since the last promotion, it rebuilds production with no schema change. The operation is ASYNCHRONOUS: poll the returned job_id with get_job_status. A plan that drops data is refused, naming every table, fi params: project_id* |
deploy_destructive | Deploy a plan that drops data, of a relational or a graph project. DESTRUCTIVE: the tables, fields, entities or relationships the plan drops lose their data. environment 'staging' deploys the saved schema, 'production' promotes staging. Use it only after a deploy tool (deploy_staging, deploy_production, deploy_graph_staging, deploy_graph_production) refused the plan, naming its drops, and those dr params: project_id*, environment* |
redeploy_project | Rebuild and roll out a project's staging environment from the schema it runs, with NO schema change, for a relational or a graph project: the current platform release, the project's settings (email, admin users) and its environment take effect. Refused (409) when the saved schema holds changes the last deploy did not apply (deploy_staging deploys those) or when nothing was deployed yet; a save tha params: project_id* |
delete_project | Delete a project (removes GitHub repo, K8s deployments, and database). It runs as a job: poll the returned job_id with get_job_status until it is completed. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'Rationa params: 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. One operation runs on a project at a time: while params: project_id*, version*, environment |
rename_project | Rename a project (changes display name, not project_code) params: 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. The response also says whether this saved schema is the deployed one: saved_schema_deployed is true when the last deploy applied it, false when it was saved aft params: 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: Start from Scratch (hierarch params: none |
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. params: 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. params: 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. params: 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",
params: name*, schema*, cluster_id* |
update_graph_schema | Replace a graph project's WHOLE schema (saves to database, does NOT deploy). DESTRUCTIVE: an entity, relationship or field the schema leaves out is deleted by the next 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} — params: project_id*, schema*, expected_version |
deploy_graph_staging | Deploy a graph project's saved schema 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_inf params: 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. A plan that drops data is refused, naming every table, field, entity or relationship it would drop, and every field whose type change rounds or cuts its values (a decimal with a smaller scale or turned integer, a datetime turned date): deploy_destructive appl params: project_id* |
delete_graph_project | Delete a graph project (removes GitHub repo, K8s deployments, Neo4j database, and credentials). It runs as a job: poll the returned job_id with get_job_status until it is completed. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call params: 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. One operation runs on a project at a time: while another runs, the call is refused and the r params: project_id*, version*, environment |
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 Sci params: project_id*, entity_type*, entity_id*, data*, environment |
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. params: project_id*, entity_type*, entity_id*, environment |
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). params: project_id*, entity_type*, limit, offset, environment |
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. params: project_id*, entity_type*, entity_id*, data*, environment |
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). params: project_id*, entity_type*, entity_id*, environment |
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. params: project_id*, rel_type*, from_id*, to_id*, data, environment |
get_node_relationships | Get all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering. params: project_id*, entity_type*, entity_id*, direction, rel_type_filter, environment |
delete_graph_relationship | Delete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs. params: project_id*, rel_type*, rel_id*, environment |
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" params: project_id*, entity_type*, nodes*, environment |
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", params: project_id*, rel_type*, relationships*, environment |
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. params: project_id*, entity_type, filters*, limit, offset, environment |
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 wi params: project_id*, query*, entity_type, limit, offset, environment |
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: "a params: project_id*, start_entity_type*, start_entity_id*, max_depth, relationship_types, direction, limit, environment |
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. params: project_id*, environment |
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. params: project_id*, environment |
list_modules | List a project's modules and what each runs: module_id (what every module tool takes), name, type (frontblok or logicblok), repository, url, staging_status (not_deployed, deploying, deployed, failed), deployed_at, image (the image of its last successful build, named by the commit it built: <name>:<short sha>-<build time>), replicas (live pods: 0 when frozen, null while the pool is not reporting), params: project_id* |
deploy_module | Deploy a new module from a GitHub repository onto the project's resource pool: a frontblok module is a Vite frontend, a logicblok module a backend built from its Dockerfile that serves port 8000 with GET /health. Its job clones the repository (the default branch head, or git_ref), builds it and serves it at the module_url the answer names; the project's CORS origins take the module in. A private r params: project_id*, module_name*, github_repo_url*, module_type*, dockerfile_path, cpu_millicores, memory_mb, env_vars, git_ref |
redeploy_module | Rebuild a module from its repository's default branch head and roll it out, keeping its pod count. Its data and settings are untouched; the project's API (staging and production) and its backend modules restart to take the module's CORS origin. The operation is ASYNCHRONOUS: poll the returned job_id with get_job_status, whose result names the image built (its commit); list_modules shows it once do params: module_id* |
update_module | Rename a module, or point it at another GitHub repository, which its next redeploy builds. Pass module_name, github_repo_url or both. One operation runs on a module at a time, and none beside an operation on its project: the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated params: module_id*, module_name, github_repo_url |
delete_module | Remove a module: its pods stop and it leaves the project and its CORS origins. DESTRUCTIVE. One operation runs on a module at a time, and none beside an operation on its project: the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. params: module_id* |
set_module_env | Set a module's environment variables: {NAME: value} sets one, {NAME: null} removes one, and every variable not named is kept. A backend module restarts to take them; a frontend module rebuilds (they are build arguments). Values are stored encrypted and never returned: the answer and list_modules name the variables only. DESTRUCTIVE: a value replaced or removed cannot be read back. CORS_ORIGINS, DE params: module_id*, env_vars* |
freeze_module | Stop a module's pods (scale to 0), remembering how many it ran; unfreeze_module starts them again. Freezing a frozen module changes nothing. One operation runs on a module at a time, and none beside an operation on its project: the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being params: module_id* |
unfreeze_module | Start a frozen module's pods again, as many as it ran before the freeze. A running module is left as it is. One operation runs on a module at a time, and none beside an operation on its project: the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few params: module_id* |
scale_module | Run 1 or 2 pods of a module (freeze_module stops it). One operation runs on a module at a time, and none beside an operation on its project: the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. params: module_id*, replicas* |
set_module_resources | Set a module's CPU and memory and rebuild it so its pods take them. The allocation is checked against the resource pool's capacity first; a refused one is restored. The operation is ASYNCHRONOUS: poll the returned job_id with get_job_status. One operation runs on a module at a time, and none beside an operation on its project: the refusal names the running job; wait for it with get_job_status, the params: module_id*, cpu_millicores*, memory_mb* |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.