Claude Code Policy: Write Managed Settings Fast
Read More
Enterprise Connectors
RationalBloks logo. RationalBloks MCP server connector.

RationalBloks MCP Server

Deploy production REST APIs from JSON schemas in seconds. Manage projects, schemas, and deployments.

ToolsTools
44
Last updatedLast Updated
Jun 14, 2026
CategoryCategory
All
Enterprise-grade security
SSO & authentication ready
Full governance & audit logs

What is the RationalBloks MCP Server?

The RationalBloks MCP server gives AI agents structured, permission-aware access to RationalBloks through the Model Context Protocol. With 44 pre-built actions, agents can read, create, and update RationalBloks data on behalf of authorized users.

Willow ships the RationalBloks MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how RationalBloks is being used by every AI agent in your stack.

Tools

Tool

list_projects

List all your RationalBloks projects with their status and URLs
Tool

get_project

Get detailed information about a specific project
Tool

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. The returned schema will be in FLAT format: {table_name: {field_name: {type, properties}}}
Tool

get_user_info

Get information about the authenticated user
Tool

get_job_status

Check the status of a deployment job. STATUS VALUES: pending (job queued), running (deployment in progress), completed (success), failed (deployment failed). TIMELINE: Typical deployment takes 2-5 minutes. If status is 'running' for >10 minutes, check get_project_info for detailed pod status. If status is 'failed', use get_project_info to see deployment errors and check schema format (must be FLAT, no 'fields' nesting).
Tool

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 review current schema. If replicas show 0/2, the init container (migration runner) is failing. This is almost always a schema format issue.
Tool

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.
Tool

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: E-commerce (products, orders, customers), Team collaboration (projects, tasks, users), General purpose templates. You can use these templates directly with create_project or modify them for your needs. TIP: Study these templates to understand the correct schema format before creating custom schemas.
Tool

get_subscription_status

Get your subscription tier, limits, and usage
Tool

get_project_usage

Get resource usage metrics (CPU, memory) for a project
...
1–10 of 44 tools
Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your RationalBloks MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-rationalbloks": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/rationalbloks"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-rationalbloks": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/rationalbloks"
    }
  }
}

Claude Code

CLI
claude mcp add willow-rationalbloks --transport http https://<org>.mcp-s.com/mcp/mcp/rationalbloks

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/rationalbloks",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for RationalBloks

Willow adds the layer RationalBloks and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

RationalBloks MCP Server FAQ

What is the RationalBloks MCP server?

The RationalBloks MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write RationalBloks data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's RationalBloks MCP server different from the official one?

The official RationalBloks MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the RationalBloks MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the RationalBloks MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in RationalBloks, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which RationalBloks actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow RationalBloks MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved RationalBloks MCP locally, you'll see it.

What does the RationalBloks MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the RationalBloks MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.

RationalBloks MCP Server | Willow