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