Modulor vs WalkMyPlan
A side-by-side look at the Modulor and WalkMyPlan MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WalkMyPlanArchitecture & DesignTurn floor-plan files (DWG/DXF/PDF/IFC) into walkable 3D models; view, edit and share by chat.37FairAuth: not declaredVerdict: choose Modulor for architecture & design work as a local process; choose WalkMyPlan for architecture & design. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Modulor when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
WChoose WalkMyPlan when
- You need dedicated capabilities in the Architecture & Design domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W WalkMyPlan | |
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 37/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Modulor | View WalkMyPlan |
Tools & capabilities
Modulor tools
No tool names declared yet. Check the project README from the listing page.
WalkMyPlan tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Modulor
{
"mcpServers": {
"modulor": {
"command": "uvx",
"args": [
"modulor"
]
}
}
}
WalkMyPlan
No confirmed install command for WalkMyPlan yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Modulor is categorized under Architecture & Design and uses a local stdio subprocess. WalkMyPlan belongs to Architecture & Design and uses an install path we have not confirmed yet. Pick Modulor for architecture & design work and WalkMyPlan for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. WalkMyPlan has no confirmed install command yet — follow its own setup instructions.
Modulor has no declared pricing — check the project's own site. WalkMyPlan has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add modulor and walkmyplan as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Modulor has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. WalkMyPlan has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.