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