
Ritn3d Mcp
io.github.printplan3dPublished by GitHub account printplan3dv0.1.2Updated Oct 24, 2026
Tools for floor plan validation, GLB checks, and 3D-print unit math — Ritn3D companion.
Overview
A local Ritn3D companion server that lets an assistant pre-check floor plan images, sanity-check GLB files, convert units, and look up Ritn3D capabilities, fail
- What you can do
- Validate floor plan images and estimate their complexity and render time before sending them to Ritn3D. Check downloaded GLB files for header, version and chunk sanity. Convert units with an optional model scale factor. Look up Ritn3D capabilities, pricing tiers and known failure modes, and read share-link metadata from public Ritn3D pages. Read capability-card and failure-playbook resources.
- When to use it
- Useful when helping with floor-plan-to-3D workflows such as renovation planning, real estate listings or 3D printing, where an assistant should pre-check inputs, explain Ritn3D limits and pricing, or verify a downloaded model before the user goes to the Ritn3D web app.
- Requirements
- Runs as a local process installed from PyPI with pip and started with the ritn3d-mcp command; configured in an MCP client such as Claude Desktop or Claude Code. No authentication, environment variables or headers are declared. Fetching share-link metadata needs network access to public Ritn3D pages.
Installation
In SourceWeft
- Open Ritn3d Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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
Use with Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Restart Claude Desktop. The Ritn3D tools appear in the tool picker.
Use with Claude Code
Tools exposed
Resources exposed
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.
Source: README.md at commit 13c4ef5
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts