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