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