get_website_service_order_status — Website Launch MCP Tool Read-only
get_website_service_order_status
(get website service order status) is one of 3 tools on the
Website Launch
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_website_service_order_status from your client
- Claude Code Website Launch get_website_service_order_status run in your project directory
- Claude Desktop Website Launch get_website_service_order_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Website Launch get_website_service_order_status ~/.cursor/mcp.json
- VS Code Website Launch get_website_service_order_status .vscode/mcp.json
- Zed Website Launch get_website_service_order_status ~/.config/zed/settings.json
- Windsurf Website Launch get_website_service_order_status ~/.codeium/windsurf/mcp_config.json
- Cline Website Launch get_website_service_order_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Website Launch get_website_service_order_status ~/.gemini/settings.json
- Grok Website Launch get_website_service_order_status .mcp.json (in your project root)
- ChatGPT Website Launch get_website_service_order_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Website Launch get_website_service_order_status Settings → Connectors → Add custom connector
- LangChain Website Launch get_website_service_order_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http website-launch https://instant-website-builder-usa-6feac193.base44.app/functions/websiteServiceMcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.