get_launch_directory — SaaSCity MCP Tool Read-only
get_launch_directory
(get launch directory) 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 get_launch_directory from your client
- Claude Code SaaSCity get_launch_directory run in your project directory
- Claude Desktop SaaSCity get_launch_directory ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SaaSCity get_launch_directory ~/.cursor/mcp.json
- VS Code SaaSCity get_launch_directory .vscode/mcp.json
- Zed SaaSCity get_launch_directory ~/.config/zed/settings.json
- Windsurf SaaSCity get_launch_directory ~/.codeium/windsurf/mcp_config.json
- Cline SaaSCity get_launch_directory ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SaaSCity get_launch_directory ~/.gemini/settings.json
- Grok SaaSCity get_launch_directory .mcp.json (in your project root)
- ChatGPT SaaSCity get_launch_directory Settings → Connectors → Advanced → Developer mode
- Claude.ai SaaSCity get_launch_directory Settings → Connectors → Add custom connector
- LangChain SaaSCity get_launch_directory 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.