# WalkMyPlan [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/yaniv-fink/walkmyplan-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/walkmyplan-2

## Description
Describe a house or upload a DWG/vector-PDF plan and get a walkable, editable 3D model.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "walkmyplan": {
    "url": "https://www.walkmyplan.com"
  }
}
```

## Documentation & README

<!-- mcp-name: com.walkmyplan/walkmyplan -->

# WalkMyPlan — Floor Plans to 3D, MCP Server

**Describe a home and walk through it.** Connect WalkMyPlan to Claude, ChatGPT, Cursor or any
MCP client and design a house in conversation: tell it the rooms, sizes and shape and one call
builds the complete layout — any footprint (L-shape, U-shape, courtyard), walls, doors, windows,
named rooms, furniture, stairs, pools and parking — then returns a live link that opens in 2D and 3D
in the browser. Already have a drawing? Upload a **DWG** or **vector PDF** and get the same
editable, measured model.

> **WalkMyPlan** is a Model Context Protocol (MCP) server. **45 tools.** Remote **Streamable
> HTTP** with **OAuth 2.1** (Dynamic Client Registration + PKCE) — keyless, no API key to paste.

- 🌐 **Website:** https://www.walkmyplan.com
- 📚 **Install & docs:** https://www.walkmyplan.com/docs
- 🔌 **Endpoint:** `https://mcp.walkmyplan.com/mcp`

---

## Connect

WalkMyPlan is a **remote** MCP server — no install, no local process. Point your client at the
endpoint; OAuth runs automatically on first connect and creates the account.

### Claude / generic MCP client (JSON)
```json
{
  "mcpServers": {
    "walkmyplan": {
      "url": "https://mcp.walkmyplan.com/mcp"
    }
  }
}
```

### Cursor
Add the `url` above in Cursor's **Settings → Tools & MCP**, or install from the listing on
`cursor.directory`.

<!--
MAINTAINER NOTE (cursor.directory): the GitHub auto-scanner reads mcp.json but STRIPS the
`mcpServers` wrapper, leaving only `{ "type": "http", "url": ... }` in the listing's Component
"Content". That drops the server name, so Cursor's install dialog shows "server" instead of
"walkmyplan". After any re-scan, re-paste the FULL wrapper into the listing Content and keep the
key a lowercase slug (`walkmyplan`, not "WalkMyPlan" — it's a config identifier):
  { "mcpServers": { "walkmyplan": { "url": "https://mcp.walkmyplan.com/mcp" } } }
The connected display name comes from the server's own serverInfo, not this key.
-->

Full per-client instructions: **https://www.walkmyplan.com/docs**

---

## Three ways to start

1. **Describe it in chat** — rooms, sizes, layout and shape in words; the model designs the
   layout and `build_house` executes it in one call.
2. **Sketch it yourself** — `create_upload_link` returns a private page where you draw the plan
   with a pencil (or start from a template) and press Build 3D. No sign-in.
3. **Start from a file** — the same private link accepts **DWG** (best results) and **vector PDF**
   drawings.

Rooms are numbered and a compass marks directions, so follow-ups like *"make room 3 wider"* or
*"move the door on the north wall"* land exactly.

---

## What you can do (45 tools)

| Area | Example tools |
|---|---|
| **Create** | `build_house`, `create_new_plan`, `create_upload_link`, `create_plan_from_url` |
| **Understand** | `get_plan_structure`, `ask_plan_question`, `get_plan_status`, `get_plan_link`, `list_my_plans`, `download_plan_pdf` |
| **Furnish** | `furnish_room`, `place_furniture_in_room`, `add_fixture_at_point`, `move_or_rotate_fixture`, `resize_fixture`, `remove_fixture`, `clear_room_furniture` |
| **Structure** | `add_wall`, `move_wall`, `remove_wall`, `set_wall_height`, `set_ceiling_height`, `add_door_or_window`, `move_door_or_window`, `resize_door_or_window`, `flip_door_hinge`, `remove_door_or_window`, `add_stairs`, `move_or_resize_stairs` |
| **Annotate** | `name_room`, `write_text_on_floor`, `add_marker`, `remove_marker_or_text` |
| **Outdoors** | `add_pool`, `move_or_resize_pool`, `add_parking`, `move_or_resize_parking` |
| **History & sharing** | `undo_last_edit`, `list_revisions`, `restore_revision`, `rename_plan`, `get_sharing`, `set_sharing`, `delete_plan`, `report_plan_problem` |

Read operations are read-only; every edit is journaled and undoable.

---

## How it works / data ownership

WalkMyPlan does **not** wrap or resell a third-party API. Plans are created by the user, stored
in the user's own account, and stay private unless the user shares them. Uploaded drawings are
converted deterministically to geometry — they are **never used to train AI models**. Edits are
for visualization and planning; WalkMyPlan does not check structural safety or building codes.

## Support

- Docs: https://www.walkmyplan.com/docs
- Email: support@walkmyplan.com
- Issues: use this repository's issue tracker.

## License

MIT — see [LICENSE](https://github.com/yaniv-fink/walkmyplan-mcp/blob/HEAD/LICENSE). (This repository hosts the MCP server's public metadata and
documentation; the server itself runs at `mcp.walkmyplan.com`.)