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