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