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