{"id":"com.rationalbloks/mcp","slug":"com-rationalbloks-mcp","title":"RationalBloks","description":"Deploy production REST and Neo4j Graph APIs from JSON schemas in seconds.","version":"0.16.2","publisher":{"kind":"domain","id":"rationalbloks.com","label":"rationalbloks.com","url":"https://rationalbloks.com"},"website":"","repository":"https://github.com/rationalbloks/rationalbloks-mcp","remotes":[{"type":"streamable-http","url":"https://mcp.rationalbloks.com/"}],"packages":[{"registryType":"pypi","identifier":"rationalbloks-mcp","version":"0.16.2","transport":{"type":"stdio"},"environmentVariables":[{"description":"Your RationalBloks API key (get it from rationalbloks.com/settings)","isRequired":true,"format":"string","isSecret":true,"name":"RATIONALBLOKS_API_KEY"}]}],"published":"2026-11-10","updated":"2026-11-10","status":"online","auth":"","latency_ms":1227,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_projects","title":"List Projects","description":"List all your RationalBloks projects with their status and URLs","read_only":true},{"name":"get_project","title":"Get Project Details","description":"Get detailed information about a specific project","read_only":true},{"name":"get_schema","title":"Get Project Schema","description":"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","read_only":true},{"name":"get_user_info","title":"Get User Info","description":"Get information about the authenticated user","read_only":true},{"name":"list_clusters","title":"List Resource Pools","description":"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 ","read_only":true},{"name":"get_job_status","title":"Get Job Status","description":"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","read_only":true},{"name":"list_project_jobs","title":"List Project Jobs","description":"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_","read_only":true},{"name":"get_project_info","title":"Get Project Info","description":"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","read_only":true},{"name":"get_version_history","title":"Get Version History","description":"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.","read_only":true},{"name":"get_template_schemas","title":"Get Template Schemas","description":"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","read_only":true},{"name":"get_schema_reference","title":"Get Schema Features Reference","description":"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 ","read_only":true},{"name":"get_subscription_status","title":"Get Subscription Status","description":"Get your subscription tier, limits, and usage","read_only":true},{"name":"get_project_usage","title":"Get Project Usage","description":"Get resource usage metrics (CPU, memory) for a project","read_only":true},{"name":"get_project_storage_usage","title":"Get Project Storage Usage","description":"Get object-storage usage for a project: file count and bytes used against the plan limits.","read_only":true},{"name":"list_project_files","title":"List Project Files","description":"List a project's uploaded files (metadata + public URLs), most recent first. Inspection only — files are not streamed through MCP.","read_only":true},{"name":"get_schema_at_version","title":"Get Schema at Version","description":"Get the schema as it was at a specific version/commit","read_only":true},{"name":"preview_schema_change","title":"Preview Schema Change","description":"Preview a schema change, saving nothing: the one way to see what a change would do before it is saved.\n\nPass ONE of:\n• operations: the operations patch_schema or drop_schema_items would apply (relational projects)\n• schema: a whole schema in place of the saved one (relational or graph projects)\n\nANSWER: 'applied' (for operations), 'diff' (every property saving it would change, by path), 'summary' ","read_only":true},{"name":"create_project","title":"Create Project","description":"Create a new RationalBloks project (a PostgreSQL REST API) from a JSON schema, on one of your resource pools.\n\n⚠️ CRITICAL RULES - READ BEFORE CREATING SCHEMA:\n\n1. FLAT FORMAT (REQUIRED):\n   ✅ CORRECT: {\"orders\": {\"total\": {\"type\": \"decimal\", \"precision\": 10, \"scale\": 2}}}\n   ❌ WRONG: {\"orders\": {\"fields\": {...}}} — never nest under 'fields'\n\n2. EVERY field has a \"type\":\n   string (MUST have max_l","read_only":false},{"name":"update_schema","title":"Update Schema","description":"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.\n\nFor 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.\n\n⚠️ Follow ALL rules from create_project:\n•","read_only":false},{"name":"patch_schema","title":"Patch Schema","description":"Change PART of a project's schema without dropping any of it (saves to database, does NOT deploy).\n\nSend only the change. The server applies it to the saved schema, in order and all together, and keeps\nevery table and field it does not touch — including their identity, so a rename stays a rename and the\ncolumn keeps its data.\n\nOPERATIONS (each one small object, applied in the order given):\n• {\"op\"","read_only":false},{"name":"drop_schema_items","title":"Drop Tables or Fields","description":"Drop tables or fields from a project's saved schema (saves to database, does NOT deploy). DESTRUCTIVE: the next deploy drops their data.\n\nOPERATIONS (applied in order and all together):\n• {\"op\": \"drop_table\", \"table\": \"clocks\"}\n• {\"op\": \"drop_field\", \"table\": \"parameters\", \"field\": \"is_clock\"}\n\nA drop that cannot be applied (a table or field that is not there, a schema the deploy would refuse, suc","read_only":false},{"name":"deploy_staging","title":"Deploy to Staging","description":"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","read_only":false},{"name":"deploy_production","title":"Deploy to Production","description":"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","read_only":false},{"name":"deploy_destructive","title":"Deploy a Plan That Drops Data","description":"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","read_only":false},{"name":"redeploy_project","title":"Redeploy Project","description":"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","read_only":false},{"name":"delete_project","title":"Delete Project","description":"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","read_only":false},{"name":"rollback_project","title":"Rollback Project","description":"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","read_only":false},{"name":"rename_project","title":"Rename Project","description":"Rename a project (changes display name, not project_code)","read_only":false},{"name":"get_graph_schema","title":"Get Graph Schema","description":"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","read_only":true},{"name":"get_graph_template_schemas","title":"Get Graph Template Schemas","description":"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","read_only":true},{"name":"get_graph_version_history","title":"Get Graph Version History","description":"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.","read_only":true},{"name":"get_graph_schema_at_version","title":"Get Graph Schema at Version","description":"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.","read_only":true},{"name":"get_graph_project_info","title":"Get Graph Project Info","description":"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.","read_only":true},{"name":"create_graph_project","title":"Create Graph Project","description":"Create a new Neo4j graph database project from a hierarchical JSON schema.\n\n⚠️ GRAPH SCHEMA FORMAT — READ BEFORE CREATING:\n\nGraph schemas define nodes (entities) and relationships, NOT flat database tables.\nEach field is a dict with \"type\" and optional \"required\": true (defaults to false).\n\nSCHEMA STRUCTURE:\n{\n  \"nodes\": {\n    \"EntityName\": {\n      \"description\": \"What this entity represents\",\n   ","read_only":false},{"name":"update_graph_schema","title":"Update Graph Schema","description":"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.\n\n⚠️ Follow ALL rules from create_graph_project:\n• Must have \"nodes\" key with at least one entity\n• Each entity needs \"description\" and \"schema\" with field definitions\n• Each field is {\"type\": \"...\", \"required\": true/false} —","read_only":false},{"name":"deploy_graph_staging","title":"Deploy Graph to Staging","description":"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","read_only":false},{"name":"deploy_graph_production","title":"Deploy Graph to Production","description":"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","read_only":false},{"name":"delete_graph_project","title":"Delete Graph Project","description":"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","read_only":false},{"name":"rollback_graph_project","title":"Rollback Graph Project","description":"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","read_only":false},{"name":"create_graph_node","title":"Create Graph Node","description":"Create a single node in a deployed graph project.\n\nREQUIRES: Project must be deployed (use deploy_graph_staging first).\n\nThe entity_type must match an entity key from the project schema.\nUse get_graph_data_schema to see available entity types and their fields.\n\nExample:\n  entity_type: \"person\"\n  entity_id: \"alan-turing-001\"\n  data: {\"name\": \"Alan Turing\", \"birth_year\": 1912, \"field\": \"Computer Sci","read_only":false},{"name":"get_graph_node","title":"Get Graph Node","description":"Get a specific node by its entity_id from a deployed graph project. Returns all node properties including created_at and updated_at timestamps.","read_only":true},{"name":"list_graph_nodes","title":"List Graph Nodes","description":"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).","read_only":true},{"name":"update_graph_node","title":"Update Graph Node","description":"Update properties of an existing node in a deployed graph project. Only send the fields you want to change — unspecified fields remain unchanged.","read_only":false},{"name":"delete_graph_node","title":"Delete Graph Node","description":"Delete a node and all its relationships from a deployed graph project. ⚠️ This also removes all relationships connected to this node (DETACH DELETE).","read_only":false},{"name":"create_graph_relationship","title":"Create Graph Relationship","description":"Create a relationship between two nodes in a deployed graph project.\n\nThe rel_type must match a relationship key from the project schema.\nUse get_graph_data_schema to see available relationship types.\n\nExample:\n  rel_type: \"authored\"\n  from_id: \"alan-turing-001\"\n  to_id: \"on-computable-numbers-001\"\n  data: {\"year\": 1936}\n\nThe from_id and to_id must be entity_ids of existing nodes.","read_only":false},{"name":"get_node_relationships","title":"Get Node Relationships","description":"Get all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering.","read_only":true},{"name":"delete_graph_relationship","title":"Delete Graph Relationship","description":"Delete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs.","read_only":false},{"name":"bulk_create_graph_nodes","title":"Bulk Create Graph Nodes","description":"Create multiple nodes at once (up to 500 per call). Uses Neo4j UNWIND for high performance.\n\nEssential for knowledge graph population — create hundreds of entities from a single book chapter or article.\n\nEach node needs: entity_id (unique string) and data (properties dict).\n\nExample:\n  entity_type: \"concept\"\n  nodes: [\n    {\"entity_id\": \"quantum-mechanics-001\", \"data\": {\"name\": \"Quantum Mechanics\"","read_only":false},{"name":"bulk_create_graph_relationships","title":"Bulk Create Graph Relationships","description":"Create multiple relationships at once (up to 500 per call). Uses Neo4j UNWIND for high performance.\n\nEssential for connecting knowledge — link hundreds of concepts, people, and events in one operation.\n\nEach relationship needs: from_id, to_id, and optional data (properties).\n\nExample:\n  rel_type: \"related_to\"\n  relationships: [\n    {\"from_id\": \"quantum-mechanics-001\", \"to_id\": \"wave-function-001\",","read_only":false},{"name":"search_graph_nodes","title":"Search Graph Nodes","description":"Search for nodes by property values in a deployed graph project.\n\nSupports exact match and contains search (prefix value with ~ for contains).\n\nExamples:\n  Exact: filters: {\"name\": \"Alan Turing\"}\n  Contains: filters: {\"name\": \"~turing\"} (case-insensitive)\n  Combined: entity_type: \"person\", filters: {\"field\": \"~physics\"}\n\nWithout entity_type, searches ALL node types.","read_only":true},{"name":"fulltext_search_graph","title":"Full-Text Search Graph","description":"Search across ALL string properties of ALL nodes in a deployed graph using free-text queries.\n\nUnlike search_graph_nodes (which filters by specific property), this searches every text field at once.\nPerfect for finding knowledge when you don't know which property contains the answer.\n\nExample: query \"quantum\" searches name, description, summary, notes, and all other string fields.\nReturns nodes wi","read_only":true},{"name":"traverse_graph","title":"Traverse Graph","description":"Walk the graph from a starting node, discovering connected knowledge.\n\nReturns all nodes reachable within max_depth hops, with their distance from the start.\nEssential for exploring knowledge graphs — find related concepts, trace connections, discover clusters.\n\nExample: Start from \"Alan Turing\", traverse outgoing relationships up to 3 hops deep:\n  start_entity_type: \"person\"\n  start_entity_id: \"a","read_only":true},{"name":"get_graph_statistics","title":"Get Graph Statistics","description":"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.","read_only":true},{"name":"get_graph_data_schema","title":"Get Graph Data Schema","description":"Get the runtime schema of a DEPLOYED graph project — shows the actual entity types and relationship types available for data operations.\n\nReturns: Available entity keys (for create_graph_node, list_graph_nodes, etc.) and relationship keys (for create_graph_relationship, etc.).\n\n⭐ USE THIS FIRST before creating nodes/relationships to know what entity_type and rel_type values are valid.","read_only":true},{"name":"list_modules","title":"List Modules","description":"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), ","read_only":true},{"name":"deploy_module","title":"Deploy Module","description":"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","read_only":false},{"name":"redeploy_module","title":"Redeploy Module","description":"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","read_only":false},{"name":"update_module","title":"Update Module","description":"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","read_only":false},{"name":"delete_module","title":"Delete Module","description":"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.","read_only":false},{"name":"set_module_env","title":"Set Module Environment","description":"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","read_only":false},{"name":"freeze_module","title":"Freeze Module","description":"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 ","read_only":false},{"name":"unfreeze_module","title":"Unfreeze Module","description":"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 ","read_only":false},{"name":"scale_module","title":"Scale Module","description":"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.","read_only":false},{"name":"set_module_resources","title":"Set Module Resources","description":"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","read_only":false}],"server_info":{"icons":[{"mimeType":"image/svg+xml","src":"https://rationalbloks.com/favicon.svg"},{"mimeType":"image/png","sizes":["1200x250"],"src":"https://rationalbloks.com/rationalbloks_logo.png"}],"name":"rationalbloks-backend","version":"0.16.2","websiteUrl":"https://rationalbloks.com"},"category":"project","tags":["cloud","ecommerce","hr"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-13","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/com-rationalbloks-mcp/"}