mark_comments_read — Player Two MCP Tool
mark_comments_read
(mark comments read) is one of 33 tools on the
Player Two
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mark_comments_read from your client
- Claude Code Player Two mark_comments_read run in your project directory
- Claude Desktop Player Two mark_comments_read ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Player Two mark_comments_read ~/.cursor/mcp.json
- VS Code Player Two mark_comments_read .vscode/mcp.json
- Zed Player Two mark_comments_read ~/.config/zed/settings.json
- Windsurf Player Two mark_comments_read ~/.codeium/windsurf/mcp_config.json
- Cline Player Two mark_comments_read ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Player Two mark_comments_read ~/.gemini/settings.json
- Grok Player Two mark_comments_read .mcp.json (in your project root)
- ChatGPT Player Two mark_comments_read Settings → Connectors → Advanced → Developer mode
- Claude.ai Player Two mark_comments_read Settings → Connectors → Add custom connector
- LangChain Player Two mark_comments_read pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://playertwo.lol/api/mcpOther tools on this server
- search_games
- list_games
- get_game_facts
- get_sdk_docs
- where_to_publish
- get_submission_guide
- check_game
- upload_media
- upload_web_build
- submit_game
- update_game
- get_game
- list_trophies
- define_trophy
- list_boards
- define_board
- list_builds
- make_build_live
- name_build
- list_products
- define_product
- get_rooms
- playtest_link
- post_update
- list_updates
- edit_update
- pin_update
- delete_update
- list_comments
- hide_comment
- lock_comments
- my_studio
This list was read from the server itself, by connecting to it and calling tools/list on 8 November 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.