MCP server

RationalBloks Official

com.rationalbloks/mcp

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

Deploy production REST and Neo4j Graph APIs from JSON schemas in seconds.

Source

At a glance

Type

MCP server

Publisher

rationalbloks.com (verified by the MCP Registry)

Status

Working at last check

Tools

64

Token cost

About 17,006 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

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

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.rationalbloks]
url = "https://mcp.rationalbloks.com/"

Gemini CLI

{"mcpServers":{"rationalbloks":{"httpUrl":"https://mcp.rationalbloks.com/"}}}

Cursor

{"mcpServers":{"rationalbloks":{"url":"https://mcp.rationalbloks.com/"}}}

VS Code

{"servers":{"rationalbloks":{"type":"http","url":"https://mcp.rationalbloks.com/"}}}

Antigravity

agy mcp add rationalbloks https://mcp.rationalbloks.com/

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"rationalbloks","server_url":"https://mcp.rationalbloks.com/","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"rationalbloks","server_url":"https://mcp.rationalbloks.com/"}

Tools

• bulk_create_graph_nodes ~369 tokens
  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:
• bulk_create_graph_relationships ~356 tokens
  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: "r
• create_graph_node ~310 tokens
  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" ent
• create_graph_project ~794 tokens
  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 S
• create_graph_relationship ~294 tokens
  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"
• create_project ~756 tokens
  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": {"f
• delete_graph_node Deletes data · ~176 tokens
  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 Deletes data · ~192 tokens
  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 j
• delete_graph_relationship Deletes data · ~166 tokens
  Delete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs.
• delete_module Deletes data · ~165 tokens
  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
• delete_project Deletes data · ~183 tokens
  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_
• deploy_destructive ~333 tokens
  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_product
• deploy_graph_production ~272 tokens
  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
• deploy_graph_staging ~354 tokens
  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 g
• deploy_module ~504 tokens
  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 serv
• deploy_production ~328 tokens
  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: pol
• deploy_staging ~454 tokens
  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
• drop_schema_items Deletes data · ~398 tokens
  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 dr
• freeze_module ~179 tokens
  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
• fulltext_search_graph ~332 tokens
  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
• get_graph_data_schema ~195 tokens
  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 befo
• get_graph_node ~174 tokens
  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 ~114 tokens
  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.
• get_graph_schema ~204 tokens
  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 depl
• get_graph_schema_at_version ~134 tokens
  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.
• get_graph_statistics ~148 tokens
  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.
• get_graph_template_schemas ~260 tokens
  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, cardinali
• get_graph_version_history ~114 tokens
  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.
• get_job_status ~306 tokens
  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
• get_node_relationships ~227 tokens
  Get all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering.
• get_project ~65 tokens
  Get detailed information about a specific project
• get_project_info ~296 tokens
  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 schem
• get_project_storage_usage ~111 tokens
  Get object-storage usage for a project: file count and bytes used against the plan limits.
• get_project_usage ~68 tokens
  Get resource usage metrics (CPU, memory) for a project
• get_schema ~440 tokens
  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 fo
• get_schema_at_version ~92 tokens
  Get the schema as it was at a specific version/commit
• get_schema_reference ~287 tokens
  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 i
• get_subscription_status ~46 tokens
  Get your subscription tier, limits, and usage
• get_template_schemas ~246 tokens
  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 n
• get_user_info ~43 tokens
  Get information about the authenticated user
• get_version_history ~132 tokens
  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.
• list_clusters ~179 tokens
  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
• list_graph_nodes ~201 tokens
  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 ~193 tokens
  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>:<s
• list_project_files ~166 tokens
  List a project's uploaded files (metadata + public URLs), most recent first. Inspection only — files are not streamed through MCP.
• list_project_jobs ~247 tokens
  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
• list_projects ~48 tokens
  List all your RationalBloks projects with their status and URLs
• patch_schema ~735 tokens
  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
• preview_schema_change ~354 tokens
  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) ANS
• redeploy_module ~255 tokens
  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
• redeploy_project ~321 tokens
  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 l
• rename_project ~92 tokens
  Rename a project (changes display name, not project_code)
• rollback_graph_project ~280 tokens
  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
• rollback_project ~294 tokens
  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. Rollbac
• scale_module ~178 tokens
  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 'RationalBl
• search_graph_nodes ~302 tokens
  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:
• set_module_env ~340 tokens
  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 nam
• set_module_resources ~262 tokens
  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
• traverse_graph ~413 tokens
  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", tr
• unfreeze_module ~170 tokens
  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
• update_graph_node ~200 tokens
  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 ~412 tokens
  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 "descri
• update_module ~225 tokens
  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 a
• update_schema ~522 tokens
  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 ch

Browse

• GitHub tools
• Email
• GitHub and code hosting
• Databases
• Docker and Kubernetes

Related MCP servers

• Witness
  Production proofs for breaking JSON Schema/MCP changes; UNKNOWN/NO_WITNESS_FOUND not compatible.
• Graph Paper
  Check a plot document and get a link that opens it in Graph Paper. No account, no key.
• Marsgeo
  Generate SEO structured data: JSON-LD schema, robots.txt, sitemaps, hreflang, Open Graph, meta.
• Rankparse
  SEO MCP server — backlinks, domain authority, tech stack, and 18+ tools via Common Crawl.
• XGR MCP Gateway
  Public Streamable HTTP MCP gateway for XGRChain, XDaLa sessions, Explorer data and XGR standards.
• Arch Tools
  63 production tools for AI agents — one API key, pay per call in USDC (x402) or Stripe credits.
• Tclp
  MCP server for The Chancery Lane Project's climate-aligned contract clause knowledge graph.
• Smart Data Extractor
  smart-data-extractor MCP server on Cloudflare Workers · REST + MCP JSON-RPC · free tier

Badge for your README

[![AptLynx](https://aptlynx.net/badge/com.rationalbloks/mcp.svg)](https://aptlynx.net/servers/com.rationalbloks/mcp)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents