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