launch_on_time_record — SpaceNexus space data MCP Tool
launch_on_time_record
(launch on time record) is one of 14 tools on the
SpaceNexus space data
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call launch_on_time_record from your client
- Claude Code SpaceNexus space data launch_on_time_record run in your project directory
- Claude Desktop SpaceNexus space data launch_on_time_record ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SpaceNexus space data launch_on_time_record ~/.cursor/mcp.json
- VS Code SpaceNexus space data launch_on_time_record .vscode/mcp.json
- Zed SpaceNexus space data launch_on_time_record ~/.config/zed/settings.json
- Windsurf SpaceNexus space data launch_on_time_record ~/.codeium/windsurf/mcp_config.json
- Cline SpaceNexus space data launch_on_time_record ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SpaceNexus space data launch_on_time_record ~/.gemini/settings.json
- Grok SpaceNexus space data launch_on_time_record .mcp.json (in your project root)
- ChatGPT SpaceNexus space data launch_on_time_record Settings → Connectors → Advanced → Developer mode
- Claude.ai SpaceNexus space data launch_on_time_record Settings → Connectors → Add custom connector
- LangChain SpaceNexus space data launch_on_time_record pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http spacenexus https://spacenexus.us/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 30 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.