verify_clone_batch — workbench MCP Prompt
verify_clone_batch
is one of 4 prompts on the
workbench
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke verify_clone_batch from your client
- Claude Code workbench Prompt/verify_clone_batch run in your project directory
- Claude Desktop workbench Prompt/verify_clone_batch ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor workbench Prompt/verify_clone_batch ~/.cursor/mcp.json
- VS Code workbench Prompt/verify_clone_batch .vscode/mcp.json
- Zed workbench Prompt/verify_clone_batch ~/.config/zed/settings.json
- Windsurf workbench Prompt/verify_clone_batch ~/.codeium/windsurf/mcp_config.json
- Cline workbench Prompt/verify_clone_batch ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI workbench Prompt/verify_clone_batch ~/.gemini/settings.json
- Grok workbench Prompt/verify_clone_batch .mcp.json (in your project root)
- ChatGPT workbench Prompt/verify_clone_batch Settings → Connectors → Advanced → Developer mode
- Claude.ai workbench Prompt/verify_clone_batch Settings → Connectors → Add custom connector
- LangChain workbench Prompt/verify_clone_batch pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.