plan_launch — SaaSCity MCP Prompt

plan_launch is one of 2 prompts on the SaaSCity MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke plan_launch from your client

• Claude Code SaaSCity Prompt/plan_launch run in your project directory
• Claude Desktop SaaSCity Prompt/plan_launch ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor SaaSCity Prompt/plan_launch ~/.cursor/mcp.json
• VS Code SaaSCity Prompt/plan_launch .vscode/mcp.json
• Zed SaaSCity Prompt/plan_launch ~/.config/zed/settings.json
• Windsurf SaaSCity Prompt/plan_launch ~/.codeium/windsurf/mcp_config.json
• Cline SaaSCity Prompt/plan_launch ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI SaaSCity Prompt/plan_launch ~/.gemini/settings.json
• Grok SaaSCity Prompt/plan_launch .mcp.json (in your project root)
• ChatGPT SaaSCity Prompt/plan_launch Settings → Connectors → Advanced → Developer mode
• Claude.ai SaaSCity Prompt/plan_launch Settings → Connectors → Add custom connector
• LangChain SaaSCity Prompt/plan_launch pip install langchain-mcp-adapters

Other prompts on this server

• submit_to_saascity

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.