# Rationalbloks MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.rationalbloks%2Frationalbloks-mcp
Registry id: `mcp-registry/io.github.rationalbloks/rationalbloks-mcp`
Status: live (checked 2026-10-26T19:48:57.846Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4877
- Outages (90 days): 5

## Install

```json
{
  "mcpServers": {
    "rationalbloks-mcp-server": {
      "type": "http",
      "url": "https://mcp.rationalbloks.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http rationalbloks-mcp-server https://mcp.rationalbloks.com/mcp
```

## Tools (64)

- `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 entiti
- `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 concep
- `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 
- `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) 
- `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_sche
- `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
- `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).
- `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 u
- `delete_graph_relationship`: Delete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs.
- `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 operati
- `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
- `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. en
- `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 d
- `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
- `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 it
- `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 stagin
- `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 depl
- `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 
- `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 
- `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), th
- `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 enti
- `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.
- `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 
- `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_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_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_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_job_status`: Check the status of a job (a create, deploy, promotion, rollback, deletion or module operation). STATUS VALUES: pending (queued), processing (in progress), comp
- `get_node_relationships`: Get all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering.
- `get_project`: Get detailed information about a specific project
- `get_project_info`: Get detailed project info including deployment status and resource usage. DEPLOYMENT STATUS: Running (healthy), Pending (starting), CrashLoopBackOff (init conta
- `get_project_storage_usage`: Get object-storage usage for a project: file count and bytes used against the plan limits.
- `get_project_usage`: Get resource usage metrics (CPU, memory) for a 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_schema_at_version`: Get the schema as it was at a specific version/commit
- `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_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_user_info`: Get information about the authenticated user
- `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
- `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
- `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)
- `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
- `list_project_files`: List a project's uploaded files (metadata + public URLs), most recent first. Inspection only — files are not streamed through MCP.
- `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 
- `list_projects`: List all your RationalBloks projects with their status and URLs
- `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 sche
- `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
- `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 (stagi
- `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 r
- `rename_project`: Rename a project (changes display name, not project_code)
- `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
- `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
- `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 t
- `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: f
- `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 
- `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 resto
- `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. Ess
- `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 b
- `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.
- `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 t
- `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 mo
- `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 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.