check_launch_readiness — SaaSCity MCP Tool Read-only
check_launch_readiness
(check launch readiness) is one of 13 tools on the
SaaSCity
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_launch_readiness from your client
- Claude Code SaaSCity check_launch_readiness run in your project directory
- Claude Desktop SaaSCity check_launch_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SaaSCity check_launch_readiness ~/.cursor/mcp.json
- VS Code SaaSCity check_launch_readiness .vscode/mcp.json
- Zed SaaSCity check_launch_readiness ~/.config/zed/settings.json
- Windsurf SaaSCity check_launch_readiness ~/.codeium/windsurf/mcp_config.json
- Cline SaaSCity check_launch_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SaaSCity check_launch_readiness ~/.gemini/settings.json
- Grok SaaSCity check_launch_readiness .mcp.json (in your project root)
- ChatGPT SaaSCity check_launch_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai SaaSCity check_launch_readiness Settings → Connectors → Add custom connector
- LangChain SaaSCity check_launch_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http saascity https://saascity.io/api/mcpOther 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.