plan_site — Louis Studios MCP Tool
plan_site
(plan site) is one of 23 tools on the
Louis Studios
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_site from your client
- Claude Code Louis Studios plan_site run in your project directory
- Claude Desktop Louis Studios plan_site ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Louis Studios plan_site ~/.cursor/mcp.json
- VS Code Louis Studios plan_site .vscode/mcp.json
- Zed Louis Studios plan_site ~/.config/zed/settings.json
- Windsurf Louis Studios plan_site ~/.codeium/windsurf/mcp_config.json
- Cline Louis Studios plan_site ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Louis Studios plan_site ~/.gemini/settings.json
- Grok Louis Studios plan_site .mcp.json (in your project root)
- ChatGPT Louis Studios plan_site Settings → Connectors → Advanced → Developer mode
- Claude.ai Louis Studios plan_site Settings → Connectors → Add custom connector
- LangChain Louis Studios plan_site pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http designer https://studios.lou15.com/mcpOther tools on this server
- create_direction
- update_direction
- compose_section
- recommend_components
- tailor_component
- search_components
- get_component
- preview_component
- install_component
- account_status
- design_options
- set_direction
- adjust_direction
- fit_component
- fit_preview
- browse_rooms
- get_icons
- get_dots
- make_mark
- compose_page
- compose_block
- review_page
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.