Ritn3d MCP

Tools for floor plan validation, GLB checks, and 3D-print unit math — Ritn3D companion.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "ritn3d-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ritn3d-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

ritn3d-mcp

A Model Context Protocol (MCP) server that gives Claude, Claude Code, Cursor, Cline, or any other MCP-compatible AI agent the lightweight tools needed to prepare a floor plan for Ritn3D and interpret the resulting 3D output — without exposing the underlying wall-detection model or inference API.

Ritn3D is an AI floor-plan-to-3D-model tool. This MCP server exists so that AI agents helping users in floor-plan- adjacent workflows (renovation planning, real estate, 3D printing, etc.) have a clean, well-documented set of tools instead of guessing.

Install

Terminal

pip install ritn3d-mcp

Use with Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

config.json

{
  "mcpServers": {
    "ritn3d": {
      "command": "ritn3d-mcp"
    }
  }
}

Restart Claude Desktop. The Ritn3D tools appear in the tool picker.

Use with Claude Code

Terminal

claude mcp add ritn3d ritn3d-mcp

Tools exposed

Tool	Description
`validate_floor_plan_image`	Pre-flight check on a floor plan image (format, dimensions, warnings) before sending to Ritn3D
`estimate_complexity`	Heuristic complexity score (simple / moderate / complex) based on edge density
`estimate_render_time`	Rough low/expected/high render-time range for a given complexity
`get_share_link_metadata`	Fetch public page title + OpenGraph data from a Ritn3D share URL
`validate_glb`	Sanity-check a downloaded GLB file (magic header, version, chunks)
`convert_units`	Unit conversion with optional model scale factor (1:100, 1:50, etc.)
`get_capabilities`	Returns Ritn3D's supported inputs, outputs, accuracy by input type, and pricing
`get_pricing`	Returns current Ritn3D pricing tiers in USD
`get_failure_modes`	Returns structured list of known failure modes with mitigation tips

Resources exposed

URI	Content
`ritn3d://capability-card`	Machine-readable summary of what Ritn3D does, accuracy, pricing
`ritn3d://failure-playbook`	Common failure modes and mitigations

Example agent flow

User: "I have a real estate listing PDF I want to 3D print as a model of my future apartment."

Agent calls validate_floor_plan_image("listing.pdf.jpg") → warnings: aspect ratio normal, resolution OK.

Agent calls estimate_complexity(...) → label "moderate", score 0.5.

Agent calls get_failure_modes() → notices the "real-estate-listing-render" failure mode applies; warns the user that wood-floor textures may trip detection.

Agent calls get_pricing() → quotes Pro+ at $19.99/mo for STL export.

Agent recommends: try the Ritn3D web app at app.ritn3d.com; if detection fails on this listing PDF, ask the agent to estimate the complexity of an alternate input.

What this server does NOT do

Run inference. The Ritn3D wall-detection model lives on Ritn3D's servers and is reached through the web app.
Bypass the Ritn3D subscription. Pricing is enforced server-side.
Expose the rendering pipeline internals.
Provide a render queue or job-tracking API.

The intent is to make agents better citizens of the Ritn3D workflow, not to replicate it.

Source

Built by the Ritn3D team. Same group that maintains ritn3d-stl-tools and ritn3d-floorplan-eval.

License

MIT — see LICENSE.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Ritn3d MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "ritn3d-mcp": { "command": "npx", "args": ["-y", "ritn3d-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/ritn3d-mcp?style=directory)](https://allmcps.com/mcp/ritn3d-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/ritn3d-mcp"><img src="https://allmcps.com/api/badge/ritn3d-mcp?style=directory" alt="Ritn3d MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Ritn3d MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

ritn3d-mcp

A Model Context Protocol (MCP) server that gives Claude, Claude Code, Cursor, Cline, or any other MCP-compatible AI agent the lightweight tools needed to prepare a floor plan for Ritn3D and interpret the resulting 3D output — without exposing the underlying wall-detection model or inference API.

Install

Terminal

pip install ritn3d-mcp

Use with Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

config.json

{
  "mcpServers": {
    "ritn3d": {
      "command": "ritn3d-mcp"
    }
  }
}

Restart Claude Desktop. The Ritn3D tools appear in the tool picker.

Use with Claude Code

Terminal

claude mcp add ritn3d ritn3d-mcp

Tools exposed

Tool	Description
`validate_floor_plan_image`	Pre-flight check on a floor plan image (format, dimensions, warnings) before sending to Ritn3D
`estimate_complexity`	Heuristic complexity score (simple / moderate / complex) based on edge density
`estimate_render_time`	Rough low/expected/high render-time range for a given complexity
`get_share_link_metadata`	Fetch public page title + OpenGraph data from a Ritn3D share URL
`validate_glb`	Sanity-check a downloaded GLB file (magic header, version, chunks)
`convert_units`	Unit conversion with optional model scale factor (1:100, 1:50, etc.)
`get_capabilities`	Returns Ritn3D's supported inputs, outputs, accuracy by input type, and pricing
`get_pricing`	Returns current Ritn3D pricing tiers in USD
`get_failure_modes`	Returns structured list of known failure modes with mitigation tips

Resources exposed

URI	Content
`ritn3d://capability-card`	Machine-readable summary of what Ritn3D does, accuracy, pricing
`ritn3d://failure-playbook`	Common failure modes and mitigations

Example agent flow

User: "I have a real estate listing PDF I want to 3D print as a model of my future apartment."

Agent calls validate_floor_plan_image("listing.pdf.jpg") → warnings: aspect ratio normal, resolution OK.

Agent calls estimate_complexity(...) → label "moderate", score 0.5.

Agent calls get_failure_modes() → notices the "real-estate-listing-render" failure mode applies; warns the user that wood-floor textures may trip detection.

Agent calls get_pricing() → quotes Pro+ at $19.99/mo for STL export.

Agent recommends: try the Ritn3D web app at app.ritn3d.com; if detection fails on this listing PDF, ask the agent to estimate the complexity of an alternate input.

What this server does NOT do

Run inference. The Ritn3D wall-detection model lives on Ritn3D's servers and is reached through the web app.
Bypass the Ritn3D subscription. Pricing is enforced server-side.
Expose the rendering pipeline internals.
Provide a render queue or job-tracking API.

The intent is to make agents better citizens of the Ritn3D workflow, not to replicate it.

Source

Built by the Ritn3D team. Same group that maintains ritn3d-stl-tools and ritn3d-floorplan-eval.

License

MIT — see LICENSE.